Honcho CLI

you@honcho-cli ~ %

██╗  ██╗ ██████╗ ███╗   ██╗ ██████╗██╗  ██╗ ██████╗
██║  ██║██╔═══██╗████╗  ██║██╔════╝██║  ██║██╔═══██╗
███████║██║   ██║██╔██╗ ██║██║     ███████║██║   ██║
██╔══██║██║   ██║██║╚██╗██║██║     ██╔══██║██║   ██║
██║  ██║╚██████╔╝██║ ╚████║╚██████╗██║  ██║╚██████╔╝
╚═╝  ╚═╝ ╚═════╝ ╚═╝  ╚═══╝ ╚═════╝╚═╝  ╚═╝ ╚═════╝

v0.1.4

getting started

honcho init

configure API key and server URL

honcho start [--setup basic]

run a local Honcho stack (Docker)

honcho doctor

verify connection and workspace health

NEW in v0.1.4local stack

honcho start / status / stop

lifecycle for the local Docker stack

honcho start --setup basic

interactive LLM + feature wizard

HONCHO_BASE_URL=http://127.0.0.1:8000

prefix any command — CLI stays on api.honcho.dev until you set this

commands

pattern

honcho <command> [args] [-w workspace] [-p peer] [-s session]

example

honcho peer chat "what does alice prefer?" -p alice -w agents

workspace

list · create · search · delete · inspect · queue-status

peer

list · create · search · inspect · card · chat get-metadata · set-metadata · representation

session

list · create · search · delete · inspect · view · add-peers context · get-metadata · set-metadata · peers remove-peers · representation · summaries

message

list · create · get

conclusion

list · create · search · delete

config

inspect current configuration

See it in action.

Query memory, inspect workspaces, and run a personal stack — scriptable, composable, and built to be driven by agents as readily as by humans.

View on GitHub Read the docs

you@honcho-cli ~ %

demo · 1/6 · text

[Features]

Built for the shape of real work.

Memory that reasons, not just recalls

Query the dialectic API directly. honcho peer chat returns answers grounded in a peer's full representation — not retrieval, reasoning.

A personal stack in one command

honcho start runs API, deriver, Postgres, and Redis via Docker. Your hosted default stays put — prefix commands with HONCHO_BASE_URL to talk to local.

Agent-friendly output

Every command emits JSON when stdout isn't a TTY or when --json is forced. Structured errors with stable error codes.

Shared config with the rest of Honcho

Reads and writes ~/.honcho/config.json — the same file plugins, host integrations, and SDKs use. On managed servers, honcho init can log you in via the browser.

Install

Three seconds to the first command.

$ uv tool install honcho-cli

View on GitHub Read the docs