CLI reference

Everything you can do from the dashboard you can also do with the chronos command. The CLI is a thin client of the chronosd daemon — start the daemon first, then run commands from inside your repository: session commands operate on the workspace of the current directory. chronos --help and chronos session --help are always authoritative.

Daemon and workspace

chronos ping                 # check that the daemon is alive
chronos .                    # connect the current repository (shorthand for `chronos open .`)
chronos open <path>          # open/register the workspace at <path> (default: .)
chronos clone <url> [path]   # git clone a remote and register it (default: ~/Chronos/<repo>)
chronos workspace list       # list registered workspaces

clone accepts https://, ssh://, and scp-like git@host:org/repo.git URLs, and authenticates through your machine’s git config (SSH agent / credential helper) — see Cloning a repository.

Sessions

chronos session new "<instruction>"        # create an isolated session and start an agent
chronos session list                       # list sessions and their status
chronos session send <id> "<instruction>"  # queue another instruction onto the sequence
chronos session attach <id>                # follow the live agent stream
chronos session rm <id>                    # close the session (worktree + branch cleanup)

session new takes an optional first prompt and these flags:

Flag	Meaning
`--from <branch>`	Branch to cut the session from. Defaults to the workspace base branch.
`--agent <name>`	Agent adapter for this session (e.g. `claude-code`, `codex`).
`--plan`	Plan mode: the agent only produces a plan, it makes no edits.

session send also accepts --plan. Starting a prompt with /plan is equivalent to passing --plan — the token is stripped before the prompt reaches the agent. See Prompting and plan mode.

Review

chronos session files   <id>           # all files in the session worktree
chronos session changes <id>           # what changed per file (status, +/− lines)
chronos session diff    <id>           # the full diff against the base branch
chronos session check   <id>           # run the verification hooks; red blocks merge

check runs the committed verification hooks (test/verify/qa/pentest) from workspace settings and prints each result plus the overall status. Failed checks include their captured output.

Scripts and terminal

chronos session run  <id> <name>       # run a named, vetted script
chronos session term <id> "<command>"  # run a command in the sandboxed, audited terminal

run accepts one of the named script slots: setup, run, archive, test, verify, qa, pentest. There is no free-text script execution.

Flag (`term`)	Meaning
`--approve`	Approve a destructive command at the approval gate and run it.

If a terminal command trips the gate, Chronos prints the operation and reason and asks you to re-run with --approve.

Pull request, approve, merge

chronos session pr      <id>           # push the branch and open a pull request
chronos session approve <id>           # certify the work (requires pr.approve)
chronos session merge   <id>           # merge if policy allows

Flag (`pr`)	Default	Meaning
`--title <title>`	`Chronos session`	Pull request title.
`--body <body>`	empty	Pull request body.
`--draft`	off	Open the pull request as a draft.

merge only proceeds when policy allows — checks green, required approvals in place, and the actor has pr.merge. Otherwise it lists exactly which blockers remain. See Pull requests, approvals and merge.

Governed context and tools

chronos session mcp     <id>           # load the governed MCPs (verify catalog, start broker)
chronos session context <id>           # load the governed context into the managed layer
chronos session capabilities <id>      # resolve the governed capability packs
chronos session set-capability <id> <pack>   # enable an overridable pack

Flag	Command	Meaning
`--approve`	`capabilities`	Approve the network install of an adapter pack at the gate.
`--off`	`set-capability`	Disable the pack for this session (default is enable).

mcp verifies the signed catalog and lists each tool’s loopback URL — the agent only ever sees the local broker, never a credential. capabilities lists each pack with its state, kind and where it runs. Only packs your organization marks overridable can be toggled; for example, to turn the Tempo optimizer off for one session:

chronos session set-capability <id> tempo --off

Cross-session memory

chronos memory propose <team> "<content>"  # propose a lesson to keep (goes through approval)
chronos memory approve <id>                # approve a proposed entry
chronos memory list <team>                 # list a team's memory

Flag (`list`)	Default	Meaning
`--status <status>`	`approved`	Filter by status: `proposed`, `approved` or `rejected`.

Writes are explicit and reviewed — nothing is remembered silently, and memory never crosses team boundaries.

chronos login                          # device flow: shows a code to enter on the panel
chronos logout                         # sign out and delete the stored credential

Flag (`login`)	Meaning
`--panel <url>`	Panel base URL. Defaults to the stored or env-configured panel.
`--status`	Print the current login status instead of starting a login.

login prints a verification URL and a user code, then waits until someone approves the device on the panel’s activation page. The credential is stored in the OS keychain and restored when the daemon restarts.

Insights

chronos insights                       # adoption and productivity metrics

Prints workspace, session, prompt, agent-run, pull-request, merge and approval counts for this daemon.