Honcho Cli
Inspect Honcho peer memory, sessions, queues, and dialectic quality from the terminal when debugging an agent workspace deployment.
Install
npx skills add https://github.com/plastic-labs/honcho --skill honcho-cliWhat is this skill?
- JSON-first CLI output with `--json` for programmatic agent consumption and structured errors
- Command groups: config, workspace, peer, session, message, conclusion with scoped `-w` / `-p` / `-s` flags
- Exit code contract: 0 success, 1 client, 2 server, 3 auth—for reliable automation gates
- Allowed-tools integration: Bash honcho and jq with Read/Grep for deep workspace debugging
- Shared config at `~/.honcho/config.json` with `honcho init` for apiKey and environmentUrl
Adoption & trust: 1 installs on skills.sh; 5k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Microsoft Foundrymicrosoft/azure-skills
Azure Aimicrosoft/azure-skills
Azure Hosted Copilot Sdkmicrosoft/azure-skills
Lark Eventlarksuite/cli
Running Claude Code Via Litellm Copilotxixu-me/skills
Setup Matt Pocock Skillsmattpocock/skills
Journey fit
Primary fit
Operate is canonical because the skill supports live introspection and diagnosis of a running Honcho deployment—not initial product build or launch copy. Monitoring matches workspace, peer, session, message, and conclusion inspection plus queue and dialectic health checks.
Common Questions / FAQ
Is Honcho Cli safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Honcho Cli
# 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 workspace` — inspect, delete, search - `honcho peer` — inspect, card, chat, search - `honcho session` — inspect, messages, 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. - Check queue status when derivation seems stalled. - Compare peer card with conclusions to understand memory state. ## Inspection tour When orienting to a Honcho deployment, walk outside-in: ### 1. Understand the workspace ```bash honcho workspace inspect --json ``` ### 2. Find the peer ```bash honcho peer list --json honcho peer inspect <peer_id> --json ``` ### 3. Check peer's memory ```bash honcho peer card <peer_id> --json honcho conclusion list --observer <peer_id> --json honcho conclusion search "topic" --observer <peer_id> --json ``` ### 4. Debug a session ```bash honcho session inspect <session_id> --json honcho message list <session_id> --last 20 --json honcho session context <session_id> --json honcho session summaries <session_id> --json ``` ### 5. Search across workspace ```bash honcho workspace search "query" --json honcho peer search <peer_id> "query" --json ``` ## Debugging playbook ### Peer not learning? ```bash # Is observation enabled? honcho peer inspect <peer_id> --json | jq '.configuration' # Is the deriver queue processing messages? honcho workspace queue-status --json # What conclusions exist? honcho conclusion list --observer <peer_id> --json honcho conclusion search "expected topic" --observer <peer_id> --json ``` ### Session context looks wrong? ```bash # Raw context an agent would receive honcho session context <session_id> --json # Summaries feeding the context honcho session summaries <session_id> --json # Recent message history honcho message list <session_id> --last 50 --json ``` ### Dialectic giving bad answers? ```bash # What the peer card says honcho peer card <peer_id> --json # Conclusions on the specific topic honcho conclusion search "topic" --observer <peer_id> --json # Exercise the dialectic directly honcho peer chat <peer_id> "what do you know about X?" --json ```