Memory library for building stateful agents
Honcho is a memory service for software agents that stores messages and events, builds representations of people and other entities over time, and provides session context, search results, and natural-language insights. It is for developers building agents that need persistent, changing state across conversations and projects, using a managed service, local stack, or self-hosted FastAPI server. The catalogue entries connect coding agents and MCP clients to Honcho’s memory system.
This repository also configures its own agents. See what honcho tells them →
Skill Claude CodeCodex
Gives AI agents persistent memory across conversations using Honcho. Automatically saves and retrieves user context so the AI remembers preferences, history, and facts between sessions. Use when you need the AI to remember past conversations, recall what a user has told it, inject relevant context into prompts, or…
Skill Claude Code
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.
Skill Claude Code
Integrate Honcho memory into existing Python or TypeScript codebases. Use when adding Honcho SDK, setting up peers, configuring sessions, and accessing Honcho's representation.
Skill Claude CodeCodex
Persistent cross-session memory via Honcho — recall what you know about the user before working, and save durable insights after.
Skill Claude CodeCodex
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.
Skill Claude CodeCodex
Build, launch, and drive a local Honcho stack to verify a change at its runtime surface (the /v3 HTTP API and the deriver queue). Use when verifying a diff or confirming a change works in the running app.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: