| name | continia-env-setup |
| description | Find or start a running BC developer environment and configure launch.json. Use when (1) you need a running environment for deploy, test, or dependency operations, (2) a session was just started and no environment is configured, (3) a command fails because the environment is stopped, or (4) the user asks to set up or connect to an environment. |
Environment Setup
Ensure a running BC environment is available and configured for development.
The CLI is located at .tools/continia.exe.
Process
- List running environments:
continia env list --status running --json
- If running env found -- pick the one with most recent
lastActivityUtc, skip to step 5
- If none running -- list stopped:
continia env list --status stopped --json, then start one: continia env start <envId>
- Poll every 10s until status is
Running: continia env get <envId> --json (typically 1-3 min; if >5 min, check continia env logs <envId>)
- Configure launch.json for all workspace apps:
continia launch add <envId> .
- Report the environment ID, description, and URL
Command Reference
continia env list [--status running|stopped] [--json]
continia env get <id> [--json]
continia env start <id>
continia env stop <id>
continia env delete <id>
continia env create --name <name> --profile <profileId> [--json]
continia env logs <id>
continia env users <id> [--json]
continia env sessions <id> [--json]
continia env profiles versions [--json]
continia env profiles list --bc-version <version> [--json]
continia launch add <id> <workspacePath>
Creating a New Environment
If no environments exist, create one:
- List available BC versions:
continia env profiles versions --json
- Pick a version, list profiles:
continia env profiles list --bc-version <version> --json
- Create:
continia env create --name "My Env" --profile <profileId> --json
- The environment starts in "Draft" status. Start it:
continia env start <envId>
- Poll until Running (see step 4 in Process above)
Error Handling
- No environments exist -- create one (see "Creating a New Environment" above)
- Stuck in "Creating" -- check
continia env logs <envId>
- API token error -- token is auto-read from VS Code setting
environment-explorer.api-token; verify it's set
