Give every agent in Herdr its own Vercel Sandbox
Herdr can place each terminal coding agent in a separate Vercel Sandbox, then return its work as an opt-in Git patch instead of letting remote edits touch the local checkout.
Herdr’s Vercel plugin gives Claude Code, Codex, and OpenCode **one isolated Sandbox per agent**. It uploads the project, installs the agent, opens a connected pane, and exposes every action as **JSON**.
Use the first invocation to inspect the complete upload set, then run it again to create the environment. Parallel agents stay off the local machine, and completed changes return as a **Git patch** that you choose whether to apply.
Herdr’s Vercel plugin gives Claude Code, Codex, and OpenCode **one isolated Sandbox per agent**. It uploads the project, installs the agent, opens a connected pane, and exposes every action as **JSON**. Use the first invocation to inspect the complete upload set, then run it again to create the environment. Parallel agents stay off the local machine, and completed changes return as a **Git patch** that you choose whether to apply. Isolation does not remove trust decisions: project files are uploaded to Vercel, applying remote work remains your responsibility, and usage incurs **standard Sandbox rates**. Permanent deletion still requires a typed confirmation.
This packages per-agent cloud isolation into a usable local workflow with inspectable uploads, JSON action records, and reviewable Git patches. It strengthens the case for parallel agents without local contention, while making the trust boundary explicit: code leaves the machine, remote output is not accepted automatically, and separate sandboxes carry stronger isolation and cost implications than user separation inside one sandbox.