anthropics / anthropics/claude-plugins-official
Plugin Proposal: CogniCore Persistent & Transferable Experience Memory for Claude
- Lingua principale
- Python
- Stelle
- 36.3k
- Fork
- 4.1k
- Merge medio
- 2g 14h
- PR unite (30g)
- 539
Descrizione
I’d like to propose CogniCore as a plugin/integration for Claude that adds a persistent experience layer to Claude workflows.
The goal isn't simply to store conversation history.
The idea is to allow Claude to retain validated experience from completed tasks and reuse it in future sessions or transfer it between agents.
For example:
Claude Agent A
↓
Solves a task
↓
Approach A → ❌
Approach B → ❌
Approach C → ✅
↓
Tests verify the result
↓
CogniCore stores the experience
↓
Claude Agent B
↓
Similar task
↓
Retrieves relevant experience
↓
Reuses / verifies it
A transferred experience could contain:
What problem was encountered
Approaches that were attempted
Which approaches failed and why
Successful approach
Verification evidence
Project/environment conditions
Provenance
Confidence
Supersession/invalidation information
The important distinction is between:
Conversation memory
"What did Claude say previously?"
and
Experience memory
"What did Claude learn from completing previous work?"
Verification
I don't want an agent saying "this worked" to automatically become trusted knowledge.
I'm experimenting with an experience lifecycle:
Observed
↓
Evidence
↓
Verified
↓
Promoted
↓
Transferable
↓
Revalidated in new context
This also allows failed approaches to become useful memories.
For example:
Approach A failed because the module was stateful.
A future agent can recognize that condition and avoid repeating the same mistake.
Claude plugin workflow
The plugin could expose operations such as:
Search relevant experience
Save completed experience
Transfer experience
Verify experience
Record feedback
A typical workflow could become:
New task
↓
Search relevant experience
↓
Check project/environment compatibility
↓
Claude performs task
↓
Verify outcome
↓
Store/promote experience
The memory backend can remain local or application-controlled, with MCP providing a way to connect Claude to the memory layer.
I've been developing Cognicore as an open-source project and experimenting with persistent memory, reflection, experience reuse, MCP integrations, and coding-agent workflows.
GitHub:
https://github.com/cognicore-dev/cognicore-my-openenv
I'm proposing this as an optional plugin rather than something that changes Claude's core behavior.
The goal is simple:
One Claude agent learns something useful. Another Claude agent shouldn't have to learn it from scratch.
I'd be interested in feedback on whether this would be a useful addition to the official Claude plugin ecosystem and what the preferred plugin architecture would be.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
No files, tests, or implementation entry points are named; the issue is a broad plugin proposal around CogniCore and Claude plugin/MCP workflows. Start by getting maintainer feedback on whether this belongs in the official plugin ecosystem and what architecture or acceptance criteria would apply. Done means the scope and integration path are agreed, not just code is written.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- ai-infra-agents, python
- Ambito
- ai-infra-agents, developer-experience
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Tranquilla
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 18/100