Where agents run
Your Mac, a teammate’s Mac shared as a host, or a cloud workspace.
Every run happens on a host: the machine where the agent reads the code, edits it and runs the project's checks. Teammates follow the run from anywhere, on a Mac or in the browser, but the work itself happens on its host.
| Host | Who starts it | Where the code is | Status |
|---|---|---|---|
| Your Mac | You | Your project folder | Available |
| A teammate's Mac | You ask; the Mac's owner (or a rule they set) accepts | That teammate's clone | Available |
| A cloud workspace | An editor, once the team's owner allows it | A short-lived cloud machine, one per run | Rolling out |
Your Mac
A run on your Mac uses your own Claude Code sign-in, in a project folder you added and authorized. The agent works under Vixentio's guard and your project's permission mode, and it never writes outside the project or inside .git.
Linking the run to a piece of shared work lets your team follow it live, send guidance and review the result. Your code stays in your folder; teammates see progress, previews and the review according to their role.
A teammate's Mac
A teammate can offer their Mac to the team as a host. Then the team's editors, on another Mac or in the browser, can ask that Mac to run a piece of shared work.
Share a Mac as a host
- Open the project's Team area (or Settings › Developer › Agents).
- Turn on Share This Mac as a Host. It's off by default and applies to this Mac only.
- Choose who may start runs without asking you: nobody (you're asked every time, the default), the team's editors, or people you choose.
- Set how many agents may run at once (2 by default, at most 8), which permission modes you accept from others, and, if you like, Only During These Hours.
Ask a teammate's Mac to run work
- On the work's page, under On a Teammate's Mac, pick a Mac marked Takes requests and choose Ask to Run….
- Choose a permission mode the host accepts and, if you want, add a short note (no paths, links or code).
- The host's owner sees who asked, the project, the work, the mode and its budget, and chooses Accept, Decline, Later or Always Allow from you. A rule they set can accept for them.
Once accepted, the run starts through the same Request, Draft and Approve steps as any task on that Mac, under its guard. The work's timeline records who asked, who accepted and what happened.
A request nobody answers expires after 10 minutes. If the host goes offline during a run, the run stops and the timeline says where it stopped: for example "Dev's Mac went offline; the run stopped at editing".
A cloud workspace
A cloud workspace is a short-lived machine made for one run and deleted when the run ends. It clones the project's repository, runs the agent with Claude Code under the same guard and permission modes as a Mac, starts the dev server for live previews, and reports to the team like a Mac does. No Mac needs to stay on.
Setting it up, repository access, secrets, the region and how models are paid for are in Cloud workspaces.
Choosing a host
- Your Mac when you're working on it yourself and want the change in your own folder.
- A teammate's Mac when someone else's machine already has the project set up, or you're on the web.
- A cloud workspace when no Mac should have to stay awake, or several agents should run without tying up anyone's machine.
Whichever host runs it, the team sees the same work page: the live preview, the timeline, guidance, the review and Publish.