alt Hacker NewsSame. 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
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
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