SkillFoxx

Honcho for Claude Code plugin

Honcho plugins from Plastic Labs: Claude Code memory that survives sessions and skills for wiring the Honcho SDK into your app.

  • 77 ★ on the repository
  • Last commit
  • MIT
Plugin

Broad access

Why this level

  • The content of your sessions is sent to the external Honcho memory service.
  • The plugin stores conclusions about the user and reuses them in later chats.
All reasons and checks

plastic-labs/claude-honchoAuthor:plastic-labs

Install

Manual install

/plugin marketplace add plastic-labs/claude-honcho

Then `/plugin install honcho@honcho` for memory or `/plugin install honcho-dev@honcho` for the SDK skills.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The content of your sessions is sent to the external Honcho memory service.
  • The plugin stores conclusions about the user and reuses them in later chats.

This is third-party code. Review the repository files before installing.

What it does

The repository is a marketplace of two Claude Code plugins built on the Honcho memory service. The `honcho` plugin keeps memory across sessions: Claude remembers preferences, projects and what it was doing before a restart or context wipe. Each Claude Code chat maps to its own Honcho session, while memory about the user is shared across projects. MCP tools such as `search`, `chat` and `create_conclusion` search messages, query memory and save conclusions. The `/honcho:interview` and `/honcho:insights` commands capture stable preferences and turn memory into CLAUDE.md edits. The second plugin, `honcho-dev`, holds the `integrate`, `migrate-py` and `migrate-ts` skills for building apps on the Honcho SDK.

Who it is for. Developers who work in Claude Code a lot and are tired of re-explaining preferences and project context after every session reset.

Good fit when

  • A session starts fresh but Claude should remember decisions from yesterday's work.
  • A team writes into one workspace and everyone needs the shared context.
  • You want to describe your coding style once with `/honcho:interview`.
  • Accumulated memory should become CLAUDE.md rules through `/honcho:insights`.
  • An app needs the Honcho SDK and the `integrate` skill from `honcho-dev` helps.

Not a fit when

  • Chat content must not be sent to an external cloud service.
  • You need memory without an account and without access setup.
  • You work without Node.js on PATH: the plugin ships as a bundle but runs on Node.

Example request

Recall how we decided to organize migrations in the last session and continue from there.

Limitations

Claude Code 2.1.287 or newer, Node.js on PATH and an account at app.honcho.dev are required. Memory is stored on the Honcho side: with browser sign-in data goes to the service cloud, and for self-hosting you set `baseUrl` in the config, while browser sign-in is cloud-only. All configuration lives in `~/.honcho/config.json`, sessions are tied to the repository and machine name, and the session layout cannot be changed. For a different session layout connect the Honcho MCP server separately.

How to disable. Uninstall the plugins with `/plugin uninstall honcho@honcho` and `/plugin uninstall honcho-dev@honcho`. Delete saved memory in Honcho and the `~/.honcho/config.json` file by hand.

FAQ

How do I install Honcho in Claude Code?

Run `/plugin marketplace add plastic-labs/claude-honcho`, then `/plugin install honcho@honcho` and `/reload-plugins`. After that `/honcho setup` opens browser sign-in or API key entry.

Where do my keys and sign-in go?

Sign-in and the key stay in the plugin pane and never reach Claude. The config sits in `~/.honcho/config.json` and environment variables override it.

How do I import past sessions?

The `/honcho import` command adds past Claude Code sessions to Honcho and skips chats already saved. The `--yes` option confirms the upload.

How do the two plugins differ?

`honcho` gives Claude Code memory across sessions. `honcho-dev` remembers nothing: it holds the `integrate`, `migrate-py` and `migrate-ts` skills for apps on the Honcho SDK.

Can a team share memory?

Yes, members write into one shared workspace, for example `team-acme`. Each chat has its own session, and Honcho reasoning can draw on context from several people.

Discussion

No questions or reviews yet.

Plugins

Honcho memory plugin for OpenClaw: separate models of the user and the agent and honcho tools beside the built-in memory.

PluginExtended access95

Long-term memory for OpenCode: preferences and project decisions survive restarts, context wipes and fresh chats.

PluginExtended access62
Official

Honcho MCP gives an agent memory about a user: it stores conclusions from conversations and answers questions about them.

MCP serverExtended access8.1K
Official

The Supermemory plugin for Claude Code: persistent memory across sessions with automatic prompt recall, conversation capture and a codebase index

PluginBroad access2.8K
Official

A Claude Code plugin that connects the agent to shared organizational memory with access control, audit and signed erasure

PluginBroad access320

A Claude Code plugin that gives the agent a name, a personality and memory across sessions, plus chat channels.

PluginBroad access64

README in short

The plugin ships as a self-contained bundle with no extra dependencies. Memory loads at session start, and the Honcho pane shows a session link, processing history and the user card.

README badge

Report a problem