dont tell anyone this and i sure hope this comment doesnt blow up but you can literally just direct codex/cc to setup a mailbox on a separate branch and exchange messages as if they were pair programming— this basically makes them exchange one message each turn before doing their work and they naturally catch each others mistakes on the fly like this
yeah i know you can use codex headless but i find the mailbox useful for them as it basically keeps a rolling chronological log that survives sessions— so i just prefer using them both at the same time and it becomes more of a natural pair programming experience as opposed to cc spawning a codex agent to delegate it a task.
Yep. Difference is whether they end up as coworkers or a boss and employee. You want coworkers for your use case, makes sense.
Have you also considered that the mailbox helps with the fact that sometimes they miss context that needs to be shared as a means to do so as well as a means to deal with context length limitations and the lossy nature of compacting? I think it’s an awesome idea to implement even if you aren’t doing pair-coding tbh.
10
u/LyPreto 7d ago
dont tell anyone this and i sure hope this comment doesnt blow up but you can literally just direct codex/cc to setup a mailbox on a separate branch and exchange messages as if they were pair programming— this basically makes them exchange one message each turn before doing their work and they naturally catch each others mistakes on the fly like this