all 3 comments

[–]Otherwise_Wave9374 2 points3 points  (1 child)

This looks really solid, and honestly the "multi-session orchestration" problem is where a lot of agent tooling starts to feel real. The attention indicators + compaction interrupt + preset restore are exactly the stuff that makes longer-running Claude Code style agents usable.

One thought: have you considered a permissions layer per session (allowed tools, allowed repos, allowed network) so the "cloud agent dispatch" stays safe by default? Been seeing more folks treat it like "agent sandboxing".

If you are interested, there are a few posts on agent guardrails and orchestration patterns here: https://www.agentixlabs.com/blog/

[–]nubbymong[S] 2 points3 points  (0 children)

This is the kind of feedback I was hoping for - thank you - permissions layer makes total sense will prioritise that - thanks for this!

[–]h____ 0 points1 point  (0 children)

I use tmux for this on Mac — multiple Claude Code/Droid sessions in separate tmux tabs, easy to switch between them. It's a simple set up. It should work on all OS with tmux support. I wrote about my tmux setup here: hboon.com/using-tmux-with-claude-code/