Remote <-> local switch

[Bnowako]

Problem:
I feel like the bottle neck for developing code very often is

1. the agents stops working when you close your terminal/computer
2. when you start new task it has to gather a lot of context which takes time
3. If the background agent does something not quite perfectly, you want to improve it but on your local machine, the switch takes a lot of time

Would be great to have an easy way of:

• continuing local session from opencode/claude/codex etc. in background-agents eg. CLI open-inspect bg takes the session and starts it in the background
• taking the context from background-agents session to the local session. eg. open-inspect continue --session af40336c686bdc664f1074db73fc37a5

Don't want to go on the tech details too much, I hope this description outlines the idea.

[sidpalas]

You would also want to clone the filesystem state (one simple solution might be to handle this via git branches)

[sidpalas]

Have you explored a workflow for continuing the work within the sandbox? (e.g. via code-server running inside?)

---

(Not discounting your feature idea -- just providing a potential workaround available now!)

[ffesseler]

+1. I suggested something along those lines a few weeks ago but now, rereading it, the description was probably too solution-oriented but the needs were the same.

[ffesseler]

continuing local session from opencode/claude/codex etc. in background-agents eg. CLI open-inspect bg takes the session and starts it in the background

Something that would work like the remote-control command in Claude code or Warp, I suppose.

[ColeMurray]

@Bnowako it's definitely an interesting idea, i did a brief bit of research into it a while back. as others above have mentioned, it's fairly nuanced to implement, as we'd need to clone the entire sandbox state locally. i added the code server and CLI support as the intermediate, but not exactly comparable.

For this specific flow, i primarily use GH as the intermediary, pushing to a branch and then pulling state locally. Perhaps this would be an option as an automated flow. An alternative would be to make use of R2, which may or may not be an easier path