are people using these things but isolating agents to some sort of containerization individually or do you have like one big dev env ? probably time i get around to sorting a better dev container strategy just to isolate agents here but trying to think of the best way to set this up locally.
I really think that using something like Paseo (I use Ouijit[1] because I think it's actually a step ahead of where most of these multiplexers are) and nono[2] is basically the best coverage you can have, and really lets you go crazy with auto mode or permission skipping withiout having to worry about any security concerns.
A lot of people lean into the VMs but realistically it's not actually doing a lot of the security work that you need and leaves you wide open to prompt injection/exfiltration attaacks. The flexibility of a good nono setup (which is easy because they ship a nono skill that claude can consume) actually locks things down significantly better
> ACP catalog, any agent speaking the Agent Client Protocol is supported through a generic adapter. Paseo ships a curated catalog of one-click installs (Cursor, Gemini, GitHub Copilot, Hermes, Kimi, Qwen Code, and 25+ more), and you can add any other ACP agent yourself.
> Either way, you install the underlying CLI. Paseo runs it.
That is the value. You can run them remotely from your phone and set them up on a headless machine too. You’re not bound to your terminal.
My usual workflow is to still use the terminal for heavy work. But sometimes I just want to prompt from my phone and run a few tasks or do some planning. Then I can simply resume the session in the terminal later. It's the flexibility.
If you’re happy with OpenCode as the harness, OpenChamber is great. But if you prefer using different harnesses under the hood, Paseo is a better fit.
I installed it on my homelab and can access the same sessions from my MacBook or iPhone at any time. Been really nice to use so far.