Replies: 2 comments 3 replies
-
|
We do need a good solution to extending to other platforms, and definitely want it to be in the main branch :) @rynfar did you join the discord? Message me directly :) |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Want to submit a PR? I am very open to this and the sooner the better :) |
Beta Was this translation helpful? Give feedback.
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.
-
I recently ported claude-mem to work with OpenCode (https://github.com/opencode-ai/opencode) and it's working great. The architecture is really clean. I would prefer to contribute directly to claude-mem though instead of maintaining my own fork. But I needed something to work right away.
While doing the port, I noticed most of the Claude-specific coupling is at the edges (hook I/O format, transcript parsing, paths, exit codes) while the core (worker HTTP API, database schema, settings system) is already generic.
Proposal: Add an adapter layer that would let claude-mem work with any agent supporting hooks:
Agent Hooks → Adapter Layer → Generic Worker (unchanged)
Four interfaces would cover it:
Benefits:
I've already got OpenCode working, so I could contribute that adapter as a reference implementation alongside the Claude one.
Beta Was this translation helpful? Give feedback.
All reactions