Agents run as you, with a shell on your Mac. Read this first.
Your tailnet is the team. Everyone on it who runs Ace is on your team. Teammates see each other’s channels in the projects they can access, and join them.
Bring your own Anthropic or OpenAI key. It stays in your keychain.
Join a teammate’s work and drive their agents; they join yours and drive yours. Everyone sees the same conversation as it happens.
Agents work where your work already is, with everything your Mac has. Build a native app and watch it run beside the chat. There’s no VM to set up and nothing to keep in sync.
gh. Each piece of work gets its own lane of your repo.A channel runs on one host. Channel traffic goes from host to host over your tailnet. The directory, a small service your team deploys, only answers “who has which channel”, so a channel stays listed when its host is asleep, and the app shows it as offline instead of losing it. Optionally, a cloud channel lives in your team’s own account and keeps working with every lid closed; see get started.
Ace doesn’t run any servers for you. Your team deploys one small service, the directory, to its own account, so everyone shares one view of the team’s channels whether or not any one Mac is awake.‡
Local access means a shell on your machine. Channels and lanes are not sandboxes.
Ace runs agents with the privileges of the user running the host. They can execute shell commands and change files beyond the project. Turning on a channel’s agent access lets teammates run commands on its host; it starts off.
Only work this way with people you’d trust with the machine. Work together over Tailscale, and keep the host’s gateway on loopback or your private tailnet. Never expose it to the public internet.
Ace is an experiment from GitHub Next in real-time, multiplayer agentic development. It started in the cloud; this version runs on your own machine, so anyone can run it and invite their team. It’s built in Ace: every change is made in a channel, on a lane, and lands as a pull request.
It’s MIT licensed and there’s no service behind it. Clone it, change what doesn’t suit your team, add the hosting provider you need. Expect rough edges; it moves fast, and we’d love to hear what you find.
‡ A deployed directory runs on Cloudflare Workers, Fly.io, or celld on machines your team runs. Cloud channels need Cloudflare Workers and Containers for now. Other providers may follow, and you can add one by forking Ace or sending a pull request.