# Tie: let any AI agent use your computer

> Tie lets any agent, anywhere, use your computer. Every call goes through your rules.

Source: https://corespeed.io/tie

Tie is part of CoreSpeed. It puts your computer behind CoreSpeed's MCP endpoint, so every agent you use can reach it, wherever that agent runs, under your rules. Tie is in beta.

## What an agent gets

Each machine you tie shows up in your agent as its own set of MCP tools, named `device__<machine>__<tool>`. With every provider switched on, a machine serves 47 tools:

- Shell and files (9 tools): commands that start in one folder you choose, `~/Work` by default, and file tools that stay inside it.
- Browser (11 tools): drive a browser on that machine. Off until you switch it on.
- Screen (27 tools): see and use the screen, apps and windows. Off until you switch it on.

Your computer already has your apps, your files and your logins, so an agent working there does not start from an empty sandbox.

## Every call goes through your rules

On its way to your computer, every command passes three checks:

1. Read-only? Reads, such as listing or reading files, run without asking.
2. Your rules. Anything else is allowed, sent to you for approval, or refused, by the rules you set.
3. The machine's deny list. The machine itself refuses the destructive commands agents usually write, such as `sudo`, even when a call was approved. Its file tools never open `~/.ssh` or `~/.aws`.

Approval requests go to you, not to the machine: a notification on your own Macs, the dashboard, Slack or email. Whichever you answer first counts. Pause, and every call is refused before it reaches the machine.

## Set it up

1. Tie the computer. On a Mac, download Tie for Mac (https://assets.corespeed.io/releases/tie-mac/latest/Tie.zip); it lives in the menu bar. Anywhere else, run `npx @corespeed/cs tie` in a terminal (a Linux box over SSH works too). It shows a code and opens app.corespeed.io/tie in that machine's browser; confirm there, or enter the code anywhere you're signed in, your phone included.
2. Connect your agent, once. Give it this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`. To add the server by hand, see https://corespeed.io/docs/mcp#set-up-your-client.

`cs untie` revokes the machine, removes its credential and stops it starting at login. The command reference: https://corespeed.io/docs/cli/tie

## Questions

### What can an agent reach on my computer?

Only what you turn on. Shell and files start in one folder you choose (`~/Work` by default). The file tools stay inside it and never open credential folders such as `~/.ssh` and `~/.aws`. Browser and Screen are off until you switch them on. A command runs as you, so it can reach what your account can: every command goes through your approval rules, and a deny list refuses the destructive ones agents usually write, such as `sudo`.

### Where do approval requests go?

To you, not to the machine: a notification on your own Macs, the dashboard, Slack or email. Whichever you answer first counts. Reads never ask.

### Which agents work with it?

Any agent that speaks MCP: Claude Code, Codex, Cursor, Claude, ChatGPT, VS Code and more. Your machines show up as tools named `device__<machine>__<tool>`.

### What happens when I pause or untie?

Pause, and every call is refused before it reaches the machine; the pause holds even when CoreSpeed can’t be reached. `cs untie` revokes the machine, removes its credential and stops it starting at login.

### Is anything recorded?

When an approved call drives the browser or the screen, Tie keeps before-and-after screenshots of it, on that machine only.

### What does it run on?

Mac, Linux and Windows. On a Mac, Tie for Mac lives in your menu bar; anywhere else it is one line in a terminal, `npx @corespeed/cs tie`, including a Linux box over SSH. Screen and browser control is built on the open-source Cua Driver; on Linux it needs a desktop session.