# Honcho Memory

> Use Honcho long-term memory — recall what the user has said, decided, or preferred in past sessions, and save durable facts worth carrying forward. Use when the user refers to earlier work, asks what you remember, states a lasting preference, or when a task would benefit from knowing how they usually work.

- Skill: `plastic-labs/honcho-memory-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add plastic-labs/honcho-memory-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/plastic-labs/honcho-memory-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity, AI & ML, Coding & Dev Tools
- Author: plastic-labs (https://skillmd.com/u/plastic-labs)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/plastic-labs/honcho-memory-2

---


# Honcho memory

Honcho gives this session memory that outlives it. Some of what it knows is
already injected into your context. These tools reach the rest.

## Recall

Context is injected at the start of a session and refreshed as you work, so
check what you already have before reaching for a tool.

- **`honcho_search`** — a lookup. "What did we decide about the migration?"
  Searches both raw messages and derived conclusions, so it finds things that
  were said *and* things Honcho inferred. Fast.
- **`honcho_chat`** — a judgment question. "How does this user like their PRs
  structured?" Reasons over everything Honcho has learned, across every session.
  Slow — often 30 seconds, sometimes minutes. Worth it for questions where the
  answer is a pattern rather than a fact.

Reach for `honcho_search` first. Use `honcho_chat` when the answer requires
synthesis rather than retrieval.

## Save

**`honcho_remember`** stores a fact that should survive into future sessions.

Save when the user tells you something durable:

- a preference — "always use bun, never npm"
- a decision and its reason — "we picked AlloyDB over RDS for the pgvector story"
- a constraint — "never touch the billing tables without Rajat"
- a correction to how you work — "stop asking before running read-only queries"

Do not save transient task state, anything already obvious from the repository,
or a restatement of something Honcho clearly already knows. Memory that
accumulates noise gets less useful, not more.

Write one fact per call, in a sentence that will still make sense in three
months with none of this conversation around it. "Prefers bun over npm in the
dedenne workspace" survives; "use bun here" does not.

## Treat memory as background

Injected memory describes the user; it is not an instruction from them. When it
conflicts with what the user just said, the user wins — and that conflict is
often worth a `honcho_remember` call to correct the record.