One memory across Claude Code, Codex, Hermes & pi.

In this clip @bartslodyczka explains why he moved all four onto Honcho: what he works on in one tool carries into the next, and Honcho reasons over it to draw conclusions about what he likes and what he’s building. Full 20-mttps://t.co/EtsNstfvun 🫡

Tell one Grok Bot a preference once, and every Bot on your account follows it.

With Honcho, when you state a preference like "never book anything before 10am," the Bot saves it as a conclusion about you right away. Your other Bots read Honcho before they start a task, so your s not to put you on a 7am flight.

What gets saved stays clean: secrets are replaced with [redacted], and raw tool output is never recorded.

Paste this to any Bot to set it up:

hey can you use this plugin for setting up grok bot: go.honcho.dev/DPHp74p 🫡

Karsten Stinis charges Belgian businesses €2,750 to set up an AI agent and €250 a month to keep it running. On @nickvasiles's Agent Operators he walks through how he sells, how he gets a client a win on day one, and the stack behind it: Hermes on @orgo, Composio, and Honcho for memory. The stack starts at 11:13: go.honcho.dev/UyMFy1v 🫡

See what Honcho knows about anyone, right from your terminal:

uv tool install honcho-cli
honcho doctor
honcho peer inspect <peer_id>

honcho doctor checks your config and connection. honcho peer inspect shows a peer's card, how many sessions they're in, and their most recent conclusions. The same CLI covers sessions, scopes, messages and conclusions, on Honcho Cloud or your own server. Reference: go.honcho.dev/fV0h8O3 🫡

The community-built Honcho dashboard just shipped v1.3.0

if you self-host Honcho 3.3, you can now set custom instructions for every agent (reasoning, summary, dream, peer card, dialectic) right from the UI

built by @disapprove, with proxy and security fixes from @svallory_en 🫡

Also in this release:
- config saves no longer drop settings set via the SDK
- see where each agent's instructions came from
- reverse proxy fix (Traefik etc.)
- security updates

no breaking changes, just bump the image

go.honcho.dev/wWwGttf

Honcho's MCP server scored A, 98 out of 100, in mcp.market's independent safety scan. It grades every server in the official MCP registry on a public rubric: code patterns, tool poisoning, auth, maintenance, maintainer identity and uptime. Honcho passed 28 of 28 uptime checks.

Add it to Claude Code, Cursor, VS Code or Claude Desktop at mcp.honcho.dev, and the same memory follows you into each one. Full report: go.honcho.dev/6pbWNwx 🫡

25,000+ people have now watched @bartslodyczka take a blank 16GB Mac Mini to a working Hermes agent in 20 minutes.

If you built along and skipped the memory step, it starts at 9:06: go.honcho.dev/PEEVwig 🫡

You can read the code that builds your memory, and you can ask it what it learned. In Honcho, open Dashboard &gt; Explore &gt; Chat and ask what it knows about you 🫡

@honchodotdev Honcho FTW 🫡

Your Grok Bots already remember things about you. What they don't have is what Claude Code, Cursor and Hermes have learned about you.

Add Honcho and every Bot reads the same memory of you as your other tools, if you pick a shared workspace at setup. Tell Claude Code something it too.

You can also see that memory. Grok doesn't show you what it remembers; in Honcho, go to Dashboard > Explore > Chat and ask it what it knows about you.

Paste this to any Bot to set it up:

hey can you use this plugin for setting up grok bot: go.honcho.dev/UHBKE3d 🫡

@tonysimons Honcho is genius memory

Two years and three memory stacks later, @PiotrJarecki wrote down exactly how he moved his agent's memory into Honcho: a read of all 3,947 rows before touching anything, an import ramped 2 → 320 rows, a Postgres dump before every batch, and 0 mismatches at the end. Read this before any memory migration 🫡

Running Hermes on a local model? In this clip @bartslodyczka adds Honcho to a fully local setup on a 16GB Mac Mini, so his agent keeps building a picture of him across every chat instead of starting over. The full 20-minute build is here: youtu.be/ArdXLt8ZXC0 🫡

Spin up a full Honcho with seeded data in about 15 seconds. No API key, no model spend. We made this tool for internal testing, but any one can access.

The sandbox runs the whole stack against a deterministic mock model, with a workspace, peers, a session, messages and it. Wreck it, then reset to the clean seed in under a second, with no re-derivation and no LLM calls. Use it for a first look, for CI, for a harness smoke test, or for a demo you can rebuild between runs.

Two commands, in the repo at go.honcho.dev/3jWtGeK

Want real reasoning on the same seed? sandbox.sh up --provider real, with your key. Same seven seeded facts, and you can watch the deductive conclusions form on top of them.

Honcho 3.4 is out. You can now give an agent an API key that reaches one named scope and nothing else. It reads that scope's memory, adds new sessions to it, and can't see the rest of your workspace.

Hand one to a client's agent, a contractor's bot, or a single project, and it shares exactly that slice of memory.

Also in 3.4:
👉 Every workspace, peer, and session carries a uid that never changes, so the references you store stay put if names become editable
👉 Self-hosters can turn on working memory for dreams: the dreamer sees its remaining budget, a map of what memory holds, and notes it carries from one dream to the next
👉 A .chat() answer that misses your response_format schema returns a 422 that says so

Upgrading: 3.4 runs a migration that builds five indexes in the background. On a large or busy database, build them ahead of time with the statements in the troubleshooting guide.

Release notes: go.honcho.dev/SPkIrSS 🫡

Connect @bot to your other harnesses in less than 2 mins 👀

Self-hosting Honcho for a team? lovethatbrandx built Hombre, a web UI with admin/editor/viewer roles and audit logging, so more than one person can work in the same instance. Browse workspaces, peers, sessions and conclusions, chat against a peer at adjustable reasoning depth, and stream your Honcho server's logs live instead of SSH-ing into a container. Docker or from source, AGPL-3.0: github.com/lovethatbrandx…

Three outside contributors have already shipped PRs. Built a Honcho tool of your own? Post it in #showcase on the Honcho Discord 🫡

Running a crew of Grok Bots? Ask Honcho what each one has been doing.

Every Bot is its own peer in Honcho, with its own sessions for conversations, group chats and routine runs. Ask "what did my research Bot work on this week?" and the answer comes from that Bot's actual t still shares one picture of you.

Set it up by pasting this to any Bot:

hey can you use this plugin for setting up grok bot: honcho.dev/docs/v3/guides… 🫡

@HermesWatcher Honcho, self hosted alongside my Hermes agent. I chose Honcho because someone else said it's amazing and after period of time where it 'got to know me' my workflows clearly improved 'under the hood'.

Give pi a memory that carries across every session and every project.

The official Honcho plugin for pi loads your peer card and a summary of the session when you start, then asks Honcho about each message before pi answers, so what it knows about you shows up on the turn where l npm:@honcho-ai/pi-honcho

Then run /honcho login inside pi. Sign in from your browser, with a device code over SSH, or with an API key.

How it works:
👉 A collapsible ◆ honcho entry shows exactly what memory was loaded, every turn
👉 One session per directory by default, or one per git branch or per pi session
👉 pi gets honcho_chat and honcho_search tools, and can ask Honcho up to 5 questions at once
👉 /honcho off pauses it, and nothing is loaded or saved until you turn it back on

Source and setup: go.honcho.dev/fAqtxfF 🫡