# Cloud agent on your Mac

Source: https://corespeed.io/use-cases/cloud-agent-on-your-mac

A cloud agent on your Mac is an agent running in the cloud that uses your Mac's shell, files and apps through Tie. The tied Mac serves them as device tools, such as device__studio-mac__shell_run. It shares only what you turn on, and every call passes your organization's approval policy.

The job: Let an agent running in the cloud use your Mac's shell, files and apps, for the work only your machine can do.

## The prompt

Paste this line into Claude Code, Codex or Cursor:

```text
set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl), then use my tied Mac to run the tests in ~/code/site and tell me which ones failed and why.
```

It starts with the setup line, so it works on a machine without CoreSpeed: the agent fetches https://corespeed.io/SKILL.md, adds the MCP server and signs you in, then does the job.

## Set up first

On the Mac, install Tie for Mac or run npx @corespeed/cs tie, and share the folder your agents may use. The browser and screen providers start off until you turn them on.

## The tools it calls

- `device__studio-mac__fs_list`: See what is in the shared folder
- `device__studio-mac__shell_run`: Run the tests on your Mac
- `device__studio-mac__fs_read`: Read the failing tests and their code
- `device__studio-mac__click`: Click in an app with no API, if screen is on

## Steps

1. **Tie your Mac**: Run npx @corespeed/cs tie on the Mac, share ~/code, and enter the code it shows on any device signed in to CoreSpeed.
2. **Paste the prompt**: Your cloud agent lists the folder, runs the tests on your Mac and reads the files behind each failure.
3. **Gate what sends**: Turn on screen only for apps with no API. Write an approval sentence for any keypress that sends a message.

The full write-up: https://corespeed.io/blog/cloud-agents-meet-your-mac

## Questions

### What can the agent reach on my Mac?

Only what you turn on. File tools stay inside the folders you share and commands start in one; browser and screen start off.

### Can it use apps that have no API?

Yes, with the screen provider on. macOS asks you to allow Accessibility and Screen Recording first.

### Does a command run as me?

Yes. A command runs as your user and can reach what your account can. The device's deny list refuses common destructive commands.

### How do I stop it?

Run cs tie pause, or turn one provider off with cs tie provider. cs untie removes the machine.

All use cases: https://corespeed.io/use-cases (Markdown: https://corespeed.io/use-cases.md)

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [TIE: let any AI agent use your computer](https://corespeed.io/tie): TIE lets Claude Code, Codex, Cursor or any MCP agent use your Mac, Linux or Windows computer: shell, files, browser and screen, under your rules.
- [Claude Code and Codex for teams, on one set of rules](https://corespeed.io/use-cases/team-of-agents): Each teammate keeps Claude Code, Codex or Cursor. Connections, memory, approvals, budgets and the activity trail are the organization's. One prompt to paste.

## Sources

- cs tie: https://corespeed.io/docs/cli/tie
- Approvals: https://corespeed.io/docs/approvals
- Tie: https://corespeed.io/tie
- Cloud agents, meet your Mac: https://corespeed.io/blog/cloud-agents-meet-your-mac

Reviewed 2026-11-14.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)
