Running multiple client projects in herdr: best practice for hard isolation between sessions?
I'm running several client projects on a Mac mini, and I manage my agent sessions with herdr. Locally I have a projects/ folder containing one subfolder per client: GitHub repos, Shopify themes, Next.js apps, etc.
What I want is simple: every workspace (with its sub-sessions) must be completely isolated from the others.
A generic command, a prompt pasted in the wrong pane, or an instruction that was meant for one client must never be able to affect another client's files or sessions. I don't want to make a mistake that creates problems for a client just because of a copy-paste error.
So far I've found two options, and both have drawbacks:
- One macOS user per client. This gives real isolation, but it's very clunky to manage with herdr (switching users, separate environments, credentials, etc.).
- Claude Code / Codex sandboxes. Good in principle, but when I create a new session directly from herdr, it doesn't start with the sandbox settings and guidelines I'd want. It's easy to end up with an unrestricted session without noticing.
Questions for people who've solved this: What's the best practice for per-project isolation in herdr?
Is there a plugin, config, or pattern in herdr to enforce security or sandboxing on every new session by default? Do you scope each workspace to its own directory (per-project config, containers, separate users), and how do you make sure new sessions inherit it? Am I missing something obvious?
Thanks!