Key Features
Tech Stack
What I really want is context “check-ins” so I can save and restore state between agents easily. Keeping conversation history gets close
There is definitely value in letting codex take a swing at tasks. I've found multiple times where codex has come up with stronger implementation plans on complex changes.
I actually have a feature of resuming conversations begun on one service on the other. It was working, but I had to prune it for the initial release. If there was strong interest in this I could seek to bring it back.
But maybe you're thinking of more of a /compact and resume on the other service to get the cleanest context to start a convo from?
Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.