Skip to content

[FEATURE]:Enable persistent memory for the system, supporting information retention across sessions and at the project level #32658

Closed as not planned

Description

@PureZentax

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

The persistent memory feature is not yet available, and I imagine the OpenCode team is already considering it.

As a temporary solution, I have developed a Skill which you are welcome to try at: https://github.com/PureZentax/open-memory. Beyond this, I'm genuinely eager to get involved in building the persistent memory module itself.

I'd also love to hear everyone's thoughts on persistent memory. Feel free to join the discussion in this issue.

Activity

  1. github-actions commented on Jun 17, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Please review these issues to see if your request is already covered, and consider contributing to the existing discussions.

  2. fixXxerTech commented on Jul 29, 2026

    @fixXxerTech

    I'd like to work on this. My design uses SQLite + FTS5 (no new infra), post-turn extraction via a compact LLM call, and SystemContext injection as a \core/relevant-memories\ source. Phased approach: CRUD + TUI panel first, then auto-extraction, then agent tools (\search_memories\ / \store_memory). I've written a detailed design doc. Happy to open a feature issue with the full breakdown if that's preferred.

  3. Drewlius commented on Aug 2, 2026

    @Drewlius

    I would recommend hosting supermemory locally on your machine if you do not want to connect to any more third party services. however their hosted environment is a great starting point to learn how to interact with the service. pretty much solves the agent memory need and can be bundled up and carried across almost every llm/agent/platform you use. they also provide ample documentation and SDK's to implement the service wherever you want where they don't already have native built in plugins or you can't connect via an MCP server.

  4. github-actions commented on Oct 1, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions