WhoseDev CLI
The WhoseDev CLI ships with the editor install. The binary name is whosedev. Use it to open projects from a shell, manage extensions, and run a local agent host for headless or automated agent sessions.
Install
Section titled “Install”The CLI is included when you install WhoseDev from whosedev.com/downloads. On Linux, apt and yum packages also install the whosedev command.
Verify it is available:
whosedev --versionOpen the editor
Section titled “Open the editor”Pass files or folders to open them in WhoseDev:
whosedev .whosedev path/to/file.tsStandard editor flags from the underlying VS Code CLI apply (diff mode, wait, reuse window, and others). Run whosedev --help for the full list on your build.
Agent host
Section titled “Agent host”The agent host runs WhoseDev’s agent loop locally so other tools can connect over WebSocket. This is useful for automation, CI-adjacent workflows, and integrations that drive the same agent as the IDE.
Start a host
Section titled “Start a host”whosedev agent hostCommon options:
| Flag | Purpose |
|---|---|
--host |
Bind address (default localhost; use 0.0.0.0 to expose on all interfaces) |
--port |
Port to bind (default 0 = OS-assigned; written to the agent host lockfile) |
--connection-token |
Require this token on WebSocket connections |
--replace |
Stop any existing agent host on this machine and start a fresh one |
--tunnel |
Expose the host through a dev tunnel |
Running whosedev agent with no subcommand starts the host with default host arguments.
Manage sessions
Section titled “Manage sessions”| Command | Purpose |
|---|---|
whosedev agent ps |
List active sessions on a running host (--json for machine-readable output, --all for idle/archived sessions) |
whosedev agent stop |
Cancel the active turn of a session |
whosedev agent kill |
Forcefully stop the agent host process tree |
whosedev agent logs |
Stream live session events |
Use --address ws://127.0.0.1:PORT?tkn=TOKEN to target a specific host. When omitted, the CLI discovers a locally running agent host automatically.
Other subcommands
Section titled “Other subcommands”| Command | Purpose |
|---|---|
whosedev tunnel |
Remote access tunnel (VS Code tunnel subsystem) |
whosedev serve-web |
Run a local web workbench |
whosedev ext |
Install, list, and manage extensions from the terminal |
Run whosedev <command> --help for command-specific flags.
Authentication
Section titled “Authentication”CLI-driven managed cloud requests use the same account as the editor. Sign in through the editor (WhoseDev: Sign In) before relying on cloud models from automated workflows. See Sign in.