anthropics / anthropics/claude-plugins-official

Plugin Proposal: CogniCore Persistent & Transferable Experience Memory for Claude

未關閉
#5,335 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Python
星號
36.3k
分支
4.1k
平均合併
2 天 14 小時
30 天內合併 PR
539

描述

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.

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

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.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
ai-infra-agents, python
領域
ai-infra-agents, developer-experience
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
冷清
描述清晰度
需要釐清
新手友好度
18/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。