That's an interesting thing... Normally if I have only one session, I just open it and say "go on" :) Claude automatically re-reads previous context and continues from stopped point.
But it is interesting, how could it work (if it works) when you have a bunch of agents, stopped simultaneously? Are all of them have stored session context? (Sorry if questions are dumb, I'm more or less beginner here)
Good question, my usual use case is using claude, hit limits, run `handoff claude codex` then handoff generates a md file from the most recent session that codex uses to continue on.
But i have built a way to provide a specific session id to get context from. It then uses the session id that is printed when you end the session. For example, codex will print something like run `codex --resume <uuid>` to continue this session. That uuid can be provided and handoff will build a context handoff from that session specifically.
So if multiple agents are running you can swap the provider/harness by using that session id.
Long term goals would be to get this working with locally hosted open source models (right now only works with claude and codex) then I can use the SOTA models until limits are hit and continue on with the "free" models.
That's an interesting thing... Normally if I have only one session, I just open it and say "go on" :) Claude automatically re-reads previous context and continues from stopped point.
But it is interesting, how could it work (if it works) when you have a bunch of agents, stopped simultaneously? Are all of them have stored session context? (Sorry if questions are dumb, I'm more or less beginner here)
Good question, my usual use case is using claude, hit limits, run `handoff claude codex` then handoff generates a md file from the most recent session that codex uses to continue on.
But i have built a way to provide a specific session id to get context from. It then uses the session id that is printed when you end the session. For example, codex will print something like run `codex --resume <uuid>` to continue this session. That uuid can be provided and handoff will build a context handoff from that session specifically.
So if multiple agents are running you can swap the provider/harness by using that session id.
Long term goals would be to get this working with locally hosted open source models (right now only works with claude and codex) then I can use the SOTA models until limits are hit and continue on with the "free" models.