CLI commands
| Command | Effect |
|---|---|
staso setup --target claude-code | Configure Claude Code hooks. |
staso setup --target codex | Configure Codex hooks. |
staso status | Report local hook configuration. Accepts --target. |
staso sync | Add missing hook events and repair the Python path. Accepts --target. |
staso update | Upgrade with the current interpreter's pip, then sync hooks. |
staso uninstall | Remove Staso hooks and clean up their state. Accepts --target. |
staso version or staso --version | Print installed version and latest-version hint. |
Run staso <command> --help to see all flags in your installed release.
Setup options
staso setup --target codex --workspace my-workspace --environment production --scope project--target accepts claude-code and codex; the default is Claude Code. --scope global writes user settings, and --scope project writes settings in the current project. Setup also accepts --api-key, --profile, --base-url, --agent-name, --no-guard, --auto-sync, and paired --capture-* / --no-capture-* flags for each content category.
The interactive flow can collect a key without placing it in a shell command. Setup stores the key in Staso's user-only credential storage and writes a reference to agent settings. Check the settings before running your agent. Setup validates access and hook installation but does not manufacture a trace.
Profiles
Profiles select a workspace, environment, and key for configured hooks:
staso profile set production --workspace my-workspace --environment production
staso profile use production
staso profile listprofile set prompts for a key unless you supply --api-key or import one with --from-credentials. The active profile applies to configured CLI agents. Use staso profile <command> --help for its flags.
Update and repair
See Update Staso for the pip upgrade path and package-manager alternatives. staso sync repairs already configured hooks; it does not install Staso into a new coding agent. If no hooks exist, run staso setup --target <agent>.