Repository navigation
Would love pluggable Memory/Knowledge Base e.g. MemPalace #15896
adamslogic
started this conversation in
Ideas
Replies: 1 comment 2 replies
|
For the cross-agent cold-start problem you describe, WorkLedger keeps continuity at the work-item level. The next supported coding session can load what was decided, what is still open and what should happen next, with recorded activity and delivery evidence available to inspect. That gives a new Claude Code, Codex CLI or other supported session a concrete starting point without relying on the previous conversation to hold the project’s working history. Capture and continuation are configured for the coding tool you use. We build WorkLedger at Digital Disruptors. If that is the part you want to try, our free guided 30-day pilot starts with one supported tool and one repository: https://workledger-ai.com/early-access |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have been using Paperclip for a while now and I am curious what the maintainers would think about pluggable memory management. For example, this popular AI memory tool -- MemPalace (https://github.com/MemPalace/mempalace) can even mine knowledge from any existing agentic conversation history. It means having multiple agent types across orgs (Gemini, Claude, Codex, Hermes, etc.) would be a non-issue when it comes to managing a background vector DB and could even auto-update as new history aggregates over time. A cold-start exploration process managed by Paperclip when introducing a new agent with a pre-existing conversation history would also be possible.
All reactions