macOS 14+ · Apple SiliconNative Swift · no ElectronFully local

Your agents,
live in the notch.

Arcade Agents watches every AI coding agent you run, shows you what each one is doing, and lets you approve — or stop — what it wants, without leaving your editor.

Claude Code · Codex · Grok Build · Kiro CLI

Running Bash
ARCADE AGENTS3 active

The real thing, at real size — click a state, try Allow or Deny, and watch a finished agent take its lap.

Every agent. One glance.

Stop context-switching to babysit a robot.

From the moment an agent starts to the moment it needs you — all in a strip of black the width of your notch.

Watch it work, live

Not a log of what finished — what's happening now. The notch reads Running Bash while the command is still running, so a long build looks busy instead of looking dead.

A creature per agent

Claude, Codex, Grok and Kiro each get their own body — you can tell them apart at a glance. The shape says which tool it's using; the colour says whether you're needed: pink working, green done, yellow waiting on you.

Approve in the notch

When an agent wants to run a command or edit a file, the island opens with the command and two buttons. Allow or deny without touching your terminal.

Not just a monitor

Four things nobody else in the notch does.

Risk-scored approvals

It reads the command before you do.

Every request is scored by blast radius. rm -rf and force-pushes light up red with the reason spelled out; a git status barely registers. Tick "always allow" on the boring ones and it stops asking — but a destructive command can never become a rule.

DESTRUCTIVEforce push — rewrites remote history
git push --force origin main
Approve from your phone

Start a long run. Walk away.

The gate already waits up to 24 hours for a human — so answering from the kitchen costs nothing. Scan a QR, and pending approvals show up on your phone with the same risk read. Local network only. No cloud, no account, off by default.

Scan with your phone
http://your-mac.local:8787
· fresh token each time
· never leaves your Wi-Fi
The audit trail

What did it touch while you were gone?

Every tool call and every decision, written to disk as it happens. Come back from lunch and read exactly what ran — or hand the CSV to whoever asks whether agents can be trusted against production.

14:02:11Claude Codeapproved
14:02:44Codexread
14:03:09Grok Builddenied
The scoreboard

Which agent is earning its keep?

Tools run, approvals granted, and a trust score — the share of an agent's requests you actually said yes to. An agent you keep denying is one you don't trust, and now you can see it.

#1
Claude Code
142 tools · 38 approved
96%
#2
Grok Build
88 tools · 20 approved
74%
#3
Codex
51 tools · 9 approved
52%
The arcade layer

It's a serious tool. It just doesn't behave like one.

The safety machinery is real. The way it tells you about it isn't po-faced.

Victory lap

Finish a run, take a bow.

When an agent completes, its creature goes green and runs the length of the island — hopping, throwing off pixel sparks. A second and a half, then it's back to being a quiet ear. It's how you catch a finished run out of the corner of your eye instead of alt-tabbing to check.

Boss fight

A destructive command isn't just another card.

When something scores critical — a force push, a recursive delete — the island doesn't quietly ask. The card turns into a boss fight, the creature grows, and the reason is spelled out in plain English. Denying it is the win, and the scoreboard counts it.

⚠ BOSS FIGHTdestructive
rm -rf ~/Library/Developer
Collision warning

Two agents, one repo, no idea about each other.

Run Claude and Grok in the same project and they will happily stomp each other's edits — neither one knows the other exists. Arcade Agents does, and it says so, loudly, before it costs you an hour. It also tracks your git worktrees, so you can give each agent its own.

⚠ COLLISIONtwo agents editing sparrow
both in ~/sparrow
Zero config

Launch it once. It wires up your agents.

It writes one hook into each agent's own config — your existing hooks preserved, every change backed up first.

Claude Code
watching
Codex
watching
Grok Build
watching
Kiro CLI
coming soon

Put your agents in the notch.

$4.99 / year · cancel anytime · no account, nothing leaves your Mac.

macOS 14+Apple SiliconDeveloper ID signed< 50MB RAM
Questions

Frequently asked.

Which agents does it support?

Claude Code, Codex and Grok Build today, with real approvals and live status — Kiro CLI is on the way. Each one speaks a different hook dialect, and Arcade Agents translates all of them, so an approval genuinely blocks the agent until you decide.

Why does Grok ask about every single command?

Because it has to. Grok exposes only one place to intercept a tool call, so every call passes through the gate — where Claude and Codex have a dedicated approval event and everything else flows straight through. Set Auto-approve read-only in Settings and the boring ones stop asking; teach it a rule and they stop for good.

Does anything leave my Mac?

No. There's no cloud, no account, and no telemetry. Agents talk to the app over a local socket. Phone approval, when you turn it on, serves a page on your own Wi-Fi behind a fresh token — it never touches the internet.

How do approvals actually work?

When an agent wants to run a tool, its hook calls a tiny bridge that opens the island and waits. You click Allow or Deny, and the agent — blocked the whole time — proceeds or stops. If the app isn't running, the bridge gets out of the way instantly so nothing ever hangs.

What if I don't have a notch?

It falls back to a floating pill at the top-center of your screen, and rides above fullscreen apps so it's there even when you're heads-down in an editor.

Is it heavy?

No. Native Swift, no Electron, under 50MB of RAM and near-zero CPU when idle. The characters and the 8-bit sounds are both generated in code — there isn't a single image or audio file in the app.

Can I run several agents at once?

That's the point. Every session shows up as its own creature in the notch, approvals queue so none get lost, and the Worktrees view tells you which agent is live in which git worktree. If two agents end up in the same project, it warns you — they can't see each other, but it can.

macOS says it's from an unidentified developer.

The app is signed with a Developer ID certificate. The first time you open it, Control-click the app in Applications and choose Open — after that it launches normally. It's a one-time step.