Inspect and debug Honcho workspaces via the `honcho` CLI. Use when investigating peer representations, memory state, session context, or dialectic quality — any task that requires introspection of a Honcho deployment, including verifying that a recall/record memory loop is actually working.

Honcho CLI honcho wraps the Honcho Python SDK with agent friendly defaults: JSON output, structured errors, input validation. Use it to inspect workspace state, debug peer memory, and diagnose the dialectic. Output & config TTY : human readable tables (default when interactive) Piped / json : JSON — collection commands emit arrays, single resource commands emit objects Exit codes : 0 success · 1 client error (bad input, not found) · 2 server error · 3 auth error Config : ~/.honcho/config.json (shared with other Honcho tools). The CLI owns apiKey and environmentUrl at the top level; run honcho init to confirm or set them. Per command scope (workspace / peer / session) is via w / p / s flags or HONCHO env vars. Command groups honcho config — CLI configuration honcho start / stop / status — local Docker stack (does not change environmentUrl ). First start pins the Honcho image digest and writes config.toml into the profile. Pass setup basic or setup advanced for an interactive config wizard (TTY only; writes .env overrides). honcho status lists every profile; pass profile for one. honcho workspace — inspect, delete, search, chat honcho peer — inspect, card, chat, search honcho session — inspect, view (transcript), context, summaries honcho message — list and get honcho conclusion — list, search, create, delete Rules Always pass json when processing output programmatically. Run honcho peer inspect before honcho peer chat to understand context. Use honcho session context to see exactly what an agent receives. Never run honcho workspace delete without honcho workspace inspect first. Compare peer card with conclusions to understand memory state. honcho start does not rewrite environmentUrl . Use HONCHO BASE URL=http://127.0.0.1:8000 to talk to local stack. Inspection tour When orienting to a Honcho deployment, walk outside in: 1. Understand the workspace 2. Find the peer 3. Check peer's memory 4. Debug a session 5. Search across workspace Debugging playbook Peer not learning? Session context looks wrong? Dialectic giving bad answers?

honcho-cli