Tie

Tie is a computer-use product from CoreSpeed Inc. that puts your own computer behind CoreSpeed so agents running anywhere can reach it as a set of tools. It is currently in beta, with a Mac menu-bar app and a one-line terminal install for Mac, Linux and Windows.

What It Is

Tie connects a machine you own to any agent that speaks MCP, including Claude Code, Codex, Cursor, Claude, ChatGPT and VS Code. Once a machine is tied, it shows up to the agent as tools named device__<machine>__<tool>. Shell and file tools start in one folder you choose (~/Work by default), while browser and screen control are off until you switch them on. Because the agent works on your real computer, it can use your signed-in Chrome, installed apps and existing files instead of starting from an empty sandbox.

How the rules work

Every command passes through your approval rules, and a deny list refuses destructive commands agents commonly write, such as sudo. Read-only calls do not ask for approval. Approval requests go to you rather than the machine, via a notification on your Macs, the dashboard, Slack or email, and whichever you answer first counts. File tools stay inside the chosen folder and do not open credential folders such as ~/.ssh and ~/.aws. When an approved call drives the browser or screen, Tie keeps before-and-after screenshots on that machine only.

Setup and control

You tie a machine by running npx @corespeed/cs tie and confirming in the browser it opens, or by entering the code from another signed-in device. Then you connect your agent once by giving it the line set up https://corespeed.io/SKILL.md, or by adding the MCP server manually. Multiple machines can be tied and each becomes its own set of tools. Pausing refuses every call before it reaches the machine, even if CoreSpeed cannot be reached, and cs untie revokes the machine, removes its credential and stops it starting at login. Screen and browser control is built on the open-source Cua Driver, and on Linux it needs a desktop session.