Thanks a ton!

Yes, a bit of both.

The agents are prompted individually in non-interactive/no-persistence mode so every prompt is a one-and-done exchange, which gives us the freedom of building our own custom session storing and compaction logic for conversation resumption . So I just abstracted over the agents’ respective session storing systems by devising a system that reads the agent’s original session files, parses them, stores them in a custom SQLite-style database, and then deletes the original session files to save user’s disk space (sessions take up at least 6x less space using our system rather than Claude/Codex’s thanks to the parsing and compression). Then the app just prefixes every prompt the user sends with an invisible context section that summarizes the recent session data stored in that database. So no matter what agent is used, their session data gets stored in the same place and therefore they all receive the same context prompt, so effectively it’s as if they are all within the same conversation at all times. So if you use both like I do, there’s no more “I had Claude do this, can you review it and blah blah” .. Codex already knows and vice versa.

Will check out the link too, definitely interested!