agentleFS
robertn702robertn702/opencode-episodic-memory/skills/remembering-conversations/SKILL.md

remembering-conversations

Skill4 starsChanged 48 days agoMITView on GitHub

Recall past OpenCode conversations when the user references previous work, past decisions, or earlier sessions — "how did we handle X", "the conversation about Y", "what did we decide", "we tried this before", "last week we...". Use episodic_search, then episodic_read_window for a bounded window, and episodic_read_session only when the full session is needed.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. obra/episodic-memory★ 487same name
    2. PracticalSwan/agent-skills★ 22same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT search for questions answerable from the current codebase or the current conversation — the index is for cross-session recall, not …

    line 21
  2. Distinctive:

    If search returns nothing relevant, say "I don't have a past conversation about that" rather than confabulating.

    line 56
  3. Very specific:

    Only OpenCode sessions are indexed (anything before the OpenCode switch is not, unless it lives in opencode.db).

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remembering Conversations

You have episodic memory: every past OpenCode session is indexed and searchable via three native tools.

When to search

Search proactively when:

  • The user references prior work: "like we did with X", "the conversation about Y", "what did we decide about Z", "we tried that before"
  • You're about to propose an approach the user may have already evaluated or rejected
  • A bug or error message feels familiar ("didn't we see this before?")
  • The user asks about their own history: "when did we set up X", "which repo was Y in"

Do NOT search for questions answerable from the current codebase or the current conversation — the index is for cross-session recall, not code search.

How

  1. episodic_search with a natural-language query describing the topic and intent, not exact keywords ("migrating from Claude Code to OpenCode", not "claude opencode").
    • Narrow with after/before dates. Local indexes also support an exact text substring (an error string, a flag name, a file path).
    • On local indexes, use mode: "text" for lexical BM25 search: every query word must appear (token-based AND, BM25-ranked) — not phrase/adjacency or substring matching.
    • Remote indexes support only vector search, without text filtering. Include relevant terms in query; do not retry unsupported text/hybrid modes.
  2. Skim the returned excerpts (date, session title, score, and anchor). Vector similarity scores are NOT calibrated probabilities: ≥ ~0.55 is a strong match, 0.4–0.55 is likely relevant, and < ~0.35 is weak or merely adjacent. These thresholds apply only to vector results. For hybrid results, use the snippet and the rrf label instead; RRF scores are on a different scale. Say when the corpus doesn't really contain the topic.
  3. episodic_read_window with the result's session ID, anchor message ID, and source_id (required for remote indexes) to inspect a small window first. Current-source windows read privacy-gated live messages. Foreign-source windows read labeled indexed exchanges: before/after count chunks, not messages, and content may be stale until that source syncs. Missing or stale anchors cannot expand. Stop on privacy denials rather than trying indexed reads.
  4. episodic_read_session with the session ID and the same source_id when the window is insufficient or unavailable. Use indexed: true for indexed excerpts, including legacy unanchored hits. Do not present these as a full live transcript.

Answering

  • Cite what you found with its date and session title ("on 2026-07-19, in 'Fix login User-Agent to get past the bot wall', we concluded...").
  • Distinguish "we decided X" from "we tried X and abandoned it" — the transcript usually records the verdict; report it accurately.
  • If search returns nothing relevant, say "I don't have a past conversation about that" rather than confabulating.

Limits

  • Only OpenCode sessions are indexed (anything before the OpenCode switch is not, unless it lives in opencode.db).
  • Conversations containing the marker DO NOT INDEX THIS CHAT are excluded — that includes conversations about this tool itself that quote the marker.
  • Excerpts embed user/assistant text and tool names, not tool output.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.