agent-memory

Store and retrieve persistent conversational memory across agent sessions.

Updated May 17, 2026
One-click install
npx skills add https://github.com/tiankong0101-byte/skills-registry --skill agent-memory-tiankong0101-byte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-memory
Source: https://github.com/tiankong0101-byte/skills-registry/tree/main/skills/agent-memory
Command: npx skills add https://github.com/tiankong0101-byte/skills-registry --skill agent-memory-tiankong0101-byte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps agents retain and recover important context across separate sessions, reducing repetition and preserving continuity for ongoing work and personalized interactions.

Core Features & Use Cases

  • Persistent Memory Storage: Save key facts, preferences, and structured context for later retrieval.
  • Context Recall: Retrieve prior information by key or semantic lookup when a conversation resumes.
  • Memory Maintenance: Update, delete, or list stored entries as user needs change.
  • Use Case: A user can ask the agent to remember project preferences, then later retrieve them during a new session without re-explaining everything.

Quick Start

Ask the agent to remember the key details from this conversation for future sessions.

Frequently Asked Questions about agent-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retain conversational context across separate agent sessions?

Persistent memory storage saves key facts and preferences for cross-session context retention. Agents retrieve prior information by key or semantic lookup when a conversation resumes, reducing repetition and preserving continuity.

What's the best way to recall user preferences in a new agent session?

Context recall retrieves prior user preferences by key or semantic lookup. You ask the agent to remember key details in one session, and it later retrieves them during a new session without re-explaining everything.

Do I need an API key to manage persistent memory for agent workflows?

Yes, you need an OPENCODE_API_KEY for authentication to access memory operations securely. This key manages stored context and protects persistent conversational memory during cross-session knowledge management workflows.

Can I update or delete stored context entries as user needs change?

Yes, memory maintenance supports updating, deleting, or listing stored entries. You can modify stored context entries as user needs change, ensuring long-term knowledge management remains accurate for ongoing work.

How does semantic lookup work for retrieving long-term knowledge management data?

Semantic lookup retrieves prior information by matching meaning rather than exact keys. This context recall mechanism helps agents find relevant stored facts and structured context when a conversation resumes.

Why does my agent lose project preferences between sessions?

Agents lose project preferences without persistent memory storage. Saving key facts and structured context for later retrieval ensures cross-session context retention, preventing the need to re-explain preferences in new sessions.