upvote
> Claude Code’s "Memory" feature was the tipping point for me

My standing orders are the default MEMORY.md must be a stub directing Claude to another MEMORY.md file in the local folder, project, etc.

All memories remain with their respective projects over syncs, moves, devices, etc. The stub must state all this clearly, and nothing else.

This has worked very well.

If you give the model/memory a name, that name can be persistent and independent over "backend" model swaps.

reply
I use opencode with claude models through a GitHub subscription. I've also used claude through Amazon Bedrock.

Both give you optionality because they support N models.

reply
They can’t allow third party software because the third parties save the outputs of Claude responses and distill them into new models to compete with Claude.
reply
This distilling sounds wonderful to me as an end user. Is there some place we can donate our chats and output?
reply
There's https://github.com/badlogic/pi-share-hf by the creator of pi-coding-agent, to redact session data and publish on Huggingface. You can find others of the same idea for Claude Code/Codex on Github, though of varying redaction quality. Or have your LLM fork pi-share-hf to work for your preferred coding agent.

Clem Delangue (HF CEO) tweeted about this[1] and mentioned https://traces.com/ for exporting Claude sessions

Edit: It looks like HF now supports importing your agent's session directory directly[2] (I hope they're redacting PII?)

[1] https://x.com/ClementDelangue/status/2041189872556269697

[2] https://huggingface.co/changelog/agent-trace-viewer

reply
Yeah who just goes and indiscriminately vacuums up data so they can train their products they’re going to sell with no intention of giving compensation to the very entities that made their products possible?
reply