Show local bridge status.
Install the local runtime using Agent plugins. The npm CLI is a thin client and does not bundle the bridge, editor, or rendering dependencies. The examples assume @editframe/cli is already installed in your project and use explicit paths; replace them with your project and installed bridge paths. A verified component installation can use --component /absolute/installed/component instead of --bridge.
bash
npx editframe status --project /absolute/project --bridge /absolute/editframe-bridgePrints the selected project runtime status as JSON. Use this to inspect the runtime before connecting an agent.
Flags
The table includes shared parser options; use the connection and command-specific flags shown above.
15 of 15
| Flag | Default | Description |
|---|---|---|
-h, --help | — | Show usage |
--version | — | Show the CLI version |
--project <value> | — | Absolute local project directory |
--bridge <value> | — | Installed bridge executable |
--component <value> | — | Installed signed component directory |
--registry <value> | — | Local bridge registry directory |
--editor <value> | — | Verified editor asset directory |
--editor-version <value> | — | Verified editor version |
--compiler-pack <value> | — | Verified compiler pack file |
--compiler-pack-sha256 <value> | — | Expected compiler pack SHA-256 |
--endpoint <value> | — | Hosted runtime API endpoint |
--project-id <value> | — | Hosted project identifier |
--composition <value> | — | Composition identifier |
--input <value> | — | JSON request file with an explicit operation identity and revision |
--job <value> | — | Job identifier |