# Honcho Memory

> Persistent cross-session memory via Honcho — recall what you know about the user before working, and save durable insights after.

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

---


# Honcho memory

You have a persistent memory of this user that survives across sessions, backed by Honcho. In `hybrid` or `context` recall mode the opencode-honcho hooks inject relevant context each turn; in `tools` mode this skill is how memory reaches you. The hooks record the conversation in every mode. This skill is for the times you should reach for memory *actively*.

## When to pull memory

Before non-trivial work, query memory instead of guessing:

- The task touches the user's preferences, conventions, or past decisions
- You're about to make an assumption you could instead verify ("which package manager?", "how is auth done here?")
- The user references something from "before" or "last time"

Use the Honcho tools:

- `honcho_search` — semantic lookup over past messages
- `honcho_chat` — ask a natural-language question about the user or project ("what's their testing style?")

## When to save memory

After you learn something durable, persist it with `honcho_create_conclusion`:

- A decision with rationale ("chose SQLite over Postgres — embedded, zero-setup")
- A stable preference ("prefers small, focused PRs")
- A non-obvious gotcha or root cause worth remembering
- A convention specific to this codebase

Keep each conclusion to one concise statement with the *why*. Review before adding near-duplicates.

## When not to bother

Skip memory for throwaway or purely mechanical tasks — running a build, answering a general knowledge question, trivial edits. Don't narrate that you checked memory; just use it.