ace

A tool for building software together, locally. Collaborate with agents and your team, all from your own machine.

Agents run as you, with a shell on your Mac. Read this first.

An experiment from GitHub Next
Open source, MIT licensed
expect rough edges
over Tailscale luke-studio mara-mbp desk-mini
YOU
MODEL PROVIDER
DIRECTORYYOUR TEAM’S ACCOUNT
YOUR MACHINE · nate-mbp
CHANNELS
+ new channel
dark-mode
swing-knob
bass-track
#dark-mode
WHILE YOU WERE AWAY
2 messages from mara · 1 agent run
✳ Pads glow on the downbeat · +18 −4
@ mara mentioned you: “ship it?”
N
nate
Beats needs a dark mode. Ideas?
L
luke luke-studio
Keep the pads lit, like a synth on a dark stage.
M
mara mara-mbp
And dim the labels so the pads pop.
N
nate
@ace do it
✳
agent
read Sources/Theme.swift
edit Theme.swift, Pads.swift
make run
✓ Beats is live
THE AGENT ASKSLit pads in the dark?
DimGlowOff
L
luke
@ace glow, on the downbeat
✓ rebuilt · +18 −4
Message
~/code/beats
+31 −9 · 2 files
BEATS● LIVE
TEMPOSWINGLEVEL
LUKE’S SCREEN · luke-studio
#dark-modeon nate-mbp
N
nate
Beats needs a dark mode. Ideas?
L
luke
Keep the pads lit, like a synth on a dark stage.
Message

    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.

    Work in each other’s channels.

    Join a teammate’s work and drive their agents; they join yours and drive yours. Everyone sees the same conversation as it happens.

    JAM, THEN @ACE
    Talk it through in the channel. The agent reads the room, so @ace do it is enough.
    EITHER DIRECTION
    When an agent asks the channel a question, whoever knows the answer replies, and it carries on.
    CATCH UP
    Mentioned in a channel you didn’t start? While you were away says who said what, and what the agents finished.
    YOUR CALL
    Teammates can ask your agent only once you turn on its agent access. It starts off.

    All the comforts of your own machine.

    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.

    YOUR TOOLS
    Your shell, toolchains and signed-in CLIs: Xcode, Swift, Bun, Docker, gh. Each piece of work gets its own lane of your repo.
    YOUR APPS
    With desktop tools on, agents operate the Mac’s apps, and show a native app’s window live in a split while they build it.
    YOUR HARDWARE
    The board on USB, the speakers on your desk. If your Mac can reach it, so can the agent.
    YOUR KEYS
    Model calls go straight from your Mac to the provider, with your key. No Ace service sits in between.

    Where it runs.

    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.

    channel traffic, host to host over the tailnetlistings only, to the directorya teammate opening a channelhosted by your team

    Deploy your team’s directory. Recommended

    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.‡

    WHAT IT HOLDS
    Your projects, hosts, where each channel lives, project shares and who’s here. No channel content: messages, code and diffs stay with each channel.
    SETTING IT UP
    In the app, Team setup → Get your team started deploys it to your Cloudflare account with your own wrangler login, and joins it. From a checkout, one command deploys it to Cloudflare or Fly.io.
    JOINING
    Send the invite from Settings → Team → Invite…, or approve a teammate’s Ask to join. Hosts reach the directory with a shared team secret, kept in each keychain.
    LOCAL ONLY
    One Mac on the tailnet can serve it instead: Create directory → This Mac. Channels only stay listed while that Mac is awake and online.
    WITHOUT ONE
    Teammates still see each other’s channels while their Macs are online; sleeping hosts’ channels drop out of view.

    Agents run as you.

    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.

    FORK

    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.