Same. For some reason late opus model are very superficial doing ux work and so am using gpt for that, but backend is much better engineered by claude, gpt prefer to duplicate everything it needs on the spot causing class sprawl

▲

bredren 13 hours ago | parent [-]

How are y'all carrying context history from one agent to the other?

I also flip between the models due to quota, TUI enhancements, model updates and service availability.

To handle this, I built a thing that normalizes your transcripts between Claude Code and Codex into a shared DB, then a CLI and skill.

It has made it so it doesn't matter what I built where (or when) I just refer to the work and drop in a /total-recall (or $total-recall on codex) and the agent brings it into the current convo.

I realize there are a lot of ~memory tools out there, but I think particular my approach and product behavior is unique.

If you're open to giving it a try, I'd appreciate any feedback: https://contextify.sh recent show hn: https://news.ycombinator.com/item?id=48777790

	▲	avereveard 2 hours ago \| parent \| next [-]
		steering: You are the sole owner of the project implementation. User maintained documentation: - goals.md for the project overall goals - tech.md for guidance on how to build the project Agent maintained documentation, current state living specs, these are not logs: - project.md is a map of the code, components and features. - choices.md write here all decision taken by the user. Do not duplicate information between these document.
	▲	nberkman 12 hours ago \| parent \| prev \| next [-]
		Sounds similar to the tool I built: https://github.com/neilberkman/ccrider#ccrider (although it's OSS whereas yours appears to be commercial)
	▲	mptest 6 hours ago \| parent \| prev [-]
		> how are yall carrying context... Personally I just , in the orchestration loop, have all decisions be constantly reviewed and deliberated on and the decisions logged in a permanent way, that way everything is auditable, the model if needed can go back and look at why x or why decision was made or x or y tool used, and they're all labeled as D-1234 or whatever. Plus I have it log the council discussions and always include provenance or the opinions so fable can go back after every major implementation and review how the orchestration loop could be improved. Basically have it log as much thinking in an organized compartmentalized way is better than any memory feature I've found though I haven't tried many. Auditable logs for every major decision, use 5.5 with reckless abandon (still have 3 resets myself). Not claiming this is perfect but it has led to a very easy time of any fresh agent picking up the project. I also keep a task queue and project status and agent playbook that also get refined based off the logs of how a run went