3 ms·
Like some others, I also built this myself. Overly simply, with tmux, a memory tree, and handoff files and an orchestrator. And yet for how simple it was, it wa
by eigenblake 2mo ago
Like some others, I also built this myself. Overly simply, with tmux, a memory tree, and handoff files and an orchestrator. And yet for how simple it was, it was so effective at minimizing the amount of duplicate context. It's like having shared specialist subagents who source and derive important shared knowledge from separate threads. It's useful because some skills just take too much of a token penalty to invoke and a single shared persistent session just lets that issue melt away. One agent pays the cost of that large skill once, and you don't have to keep paying for it in input tokens for the rest of that conversation.
- onlyrealcuzzo 2mo agoDoes this work for different harnesses like Codex and Antigravity?
- vanjajaja1 2mo agocodex has been able to send messages across threads for a long time
- JV00 2mo agoBut what if I use parallel agents from different harnesses? Then I probably need to build my own communication tool
- throwaway314155 2mo agoYou can have Codex access Claude’s conversations trivially. The other way around not so much as OpenAI locks everything server side.
- throwaway314155 2mo agoI take this back. Apparently the codex conversations are indeed stored in jsonl files in the users .codex directory.
- Yokolos 2mo agoHave you maybe documented this anywhere or do you have suggestions for repos to look at that do this? This sounds interesting and I'd like to look into this myself
- maxrev17 2mo agoLikewise I have the ability for agents to talk cross harness etc. pretty useful, token efficiency in question :p useful when you got lazy though and have 2 convergent sessions.