DevCore CLI overview

Use the DevCore CLI to script DevAgent from a terminal, manage worktrees, control agent terminals, automate the built-in browser, and install agent skills.

The DevCore CLI is the devcore command-line interface for scripting a running DevAgent editor from any shell. Use it to create and inspect worktrees, drive agent terminals, open files and diffs, automate the built-in browser, run scheduled automations, share HTML/Markdown artifacts, and control DevAgent-native tools from scripts or AI agents.

It ships with the desktop app; register it under Settings → General → DevCore CLI.

Agents can install the matching DevCore CLI skill with:

npx skills add https://github.com/Clouditera/devagent-skills --skill orca-cli
# headless / no Settings UI:
devcore skills install --skill orca-cli

See Skills registry & MCP for every installable DevAgent skill, including devcore skills install / devcore skills update.

Install & verify

command -v devcore
devcore status --json

Worktree commands

devcore worktree ps --json
devcore worktree create --repo id:<repoId> --name my-task --issue 123 --json
devcore worktree current --json
devcore worktree set --worktree active --comment "reproduced bug" --json
devcore worktree rm --worktree id:<id> --force --json

For selectors, setup flags, parent/child worktrees, and the broader command map, see DevCore CLI reference.

Terminal commands

devcore terminal list --json
devcore terminal read --json
devcore terminal send --text "continue" --enter --json
devcore terminal wait --for tui-idle --timeout-ms 30000 --json
devcore terminal create --worktree path:/projects/app --command "npm test" --json
devcore terminal split --direction vertical --command "npm run dev" --json

For tracked multi-agent work, use Orchestration instead of plain terminal prompts.

File commands

Open files and diffs in the active DevAgent worktree from a shell:

devcore file open src/App.tsx
devcore file diff src/App.tsx --staged
devcore file open-changed --mode both

Use --worktree <selector> when the shell's current directory is not inside the target worktree.

Browser profiles

Browser profiles isolate tab session state, so a script or agent can test with different cookies, local storage, and logged-in identities. The CLI exposes profile commands under devcore tab profile; start with devcore tab profile list --json, then use create, set, clone, or use-default as needed.

Scheduled automations

Use devcore automations to create, inspect, run, and remove scheduled DevAgent tasks from a shell. Start with Scheduled automations when you want a recurring prompt to run against a repo or an existing worktree.

Artifacts

Share HTML or Markdown as public view links through the signed-in DevAgent account (devcore artifacts share|update|list|delete). Publishing is opt-in under Settings → Artifacts. Command details: CLI reference → Artifacts.

Browser automation

The CLI also drives the built-in browser with a snapshot-interact-re-snapshot loop:

devcore goto --url https://example.com --json
devcore snapshot --json     # returns refs like @e1, @e3
devcore click --element @e3 --json
devcore fill --element @e1 --value "[email protected]" --json
devcore screenshot --json

For responsive browser checks, switch the active tab to a named device profile:

devcore set device --name "iPhone 12" --json
devcore screenshot --json

Mobile emulator

The CLI can also drive an iOS Simulator through DevAgent's mobile emulator bridge. It is scoped to the active worktree, so agents and scripts can attach a simulator from devcore emulator list, tap normalized coordinates, type text, send gestures, rotate the device, and shut it down without leaving DevAgent.

devcore emulator list --json
devcore emulator attach "<device-name-or-udid>" --json
devcore emulator tap 0.5 0.7 --json
devcore emulator type "hello" --json
devcore emulator gesture '[{"type":"begin","x":0.5,"y":0.8},{"type":"move","x":0.5,"y":0.4},{"type":"end","x":0.5,"y":0.2}]' --json
devcore emulator rotate landscape_left --json
devcore emulator kill --json

Use --worktree <selector>, --device <udid-or-name>, or --emulator <id> when a script needs an explicit target.

For the full command surface including tabs, waits, cookies, and frames, see DevCore CLI reference, then install the DevCore CLI skill (see Skills registry) and point your agent at it.