Honcho Cli

Name: Honcho Cli
Author: plastic-labs

plastic-labs/honcho

412 installs
6.4k repo stars
Updated August 4, 2026
plastic-labs/honcho

honcho-cli is a Claude Code skill that inspects Honcho peer memory, sessions, queues, and dialectic quality via the honcho terminal CLI with JSON output when debugging live agent workspace deployments.

About

honcho-cli is a debugging skill from plastic-labs/honcho for developers operating Honcho agent memory deployments. It wraps the Honcho Python SDK with agent-friendly defaults: JSON output via --json or piped mode, structured errors, and input validation. Use the honcho command to inspect workspace state, peer representations, memory contents, session context, queue status, and dialectic quality when a production or staging Honcho deployment misbehaves. Interactive TTY sessions render human-readable tables; scripted checks emit JSON arrays for jq parsing. Allowed tools include Bash(honcho:*), Bash(jq:*), Read, and Grep. Developers reach for honcho-cli during incident response on agent workspaces, not when initially scaffolding a new Honcho integration from scratch.

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

Honcho Cli by the numbers

412 all-time installs (skills.sh)
+24 installs in the week ending Aug 4, 2026 (Skillselion tracking)
Ranked #1,935 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
Security screen: LOW risk (skills.sh audit)
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/plastic-labs/honcho --skill honcho-cli

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/plastic-labs/honcho/honcho-cli.svg)](https://skillselion.com/skills/plastic-labs/honcho/honcho-cli)

Installs	412
repo stars	★ 6.4k
Security audit	3 / 3 scanners passed
Last updated	August 4, 2026
Repository	plastic-labs/honcho ↗

How do you debug Honcho agent memory from the terminal?

Inspect Honcho peer memory, sessions, queues, and dialectic quality from the terminal when debugging an agent workspace deployment.

Who is it for?

Developers debugging live Honcho agent workspace deployments who need structured CLI introspection of memory, sessions, and queues.

Skip if: Developers who do not run Honcho deployments or who only need to scaffold new Honcho SDK integrations without production debugging.

When should I use this skill?

A user asks to inspect Honcho peer memory, check session context, diagnose queue backlog, or evaluate dialectic quality on a deployment.

What you get

JSON or table dumps of peer memory, session state, queue status, and dialectic quality metrics from a live Honcho deployment.

Memory and session state dumps
Queue and dialectic diagnostic output

Files

SKILL.mdMarkdownGitHub ↗

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

honcho workspace inspect --json

2. Find the peer

honcho peer list --json
honcho peer inspect <peer_id> --json

3. Check peer's memory

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

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

honcho workspace search "query" --json
honcho peer search <peer_id> "query" --json

Debugging playbook

Peer not learning?

# 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?

# 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?

# 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

Related skills

Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k

Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k

CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k

Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k

Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72

Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10

FAQ

What does honcho-cli output in scripted mode?

honcho-cli outputs JSON arrays when piped or passed --json, making collection commands machine-parseable with jq. Interactive TTY sessions default to human-readable tables for manual Honcho deployment debugging.

Which Honcho states can honcho-cli inspect?

honcho-cli inspects peer representations, memory state, session context, queue status, and dialectic quality on Honcho deployments. Developers use it for terminal introspection during agent workspace incident response.

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.

AI & Agent Buildingagentsautomation