npx, and an install inside a folder
works only while that folder exists. To update later, or for the details, see
Updating the CLI.
Most days you run none of these. The daemon syncs on its own. The ones you
touch are auth once per machine, init once per project, and mcp when you
set up an agent.
Commands
Driving it from a coding agent
Every command takes--json and prints exactly one object, and every command
that would ask a question takes a flag answering it instead: --agents/--yes
for which coding agents to sync from, -y for a confirmation. Without a
terminal and without those flags, a command fails immediately and names the
flag rather than waiting for a keypress.
That is what lets you hand setup, and everything after it, to the agent you
already have open — see setting up with an agent.
Driving it from a coding agent
Every command takes--json and prints exactly one object, and every command
that would ask something takes a flag that answers it instead: --agents or
--yes for which coding agents to sync from, -y for a confirmation. Without
a terminal and without those flags, a command fails immediately and names the
flag, rather than waiting for a keypress that cannot come.
That is what lets you hand setup — and everything after it — to the agent you
already have open. See setting up with an agent.
Global options
Commands that act on a project must be run inside a directory that has been
inited, because that is how the CLI knows which project you mean.