REACTORSYSTEMS // CORE · MACOS 15+
Claude Code,
with a systems pane.
A real terminal on the left. On the right, a native pane that reads the session as it happens: context, tool calls, limits, cost and your repo.
- TICKS
- 60
- REFRESH
- DISPLAY
- FORCE PUSH
- NEVER
Claude Code v2.1.296
Opus 5.5 · ~/devs/apps/ularnaga
add a leaderboard under the score and keep the top ten
The store now keeps the ten best runs, sorted by score then length. LeaderboardView sits under the score on the game-over screen. Running the tests before I hand it back.
◜ EXECUTING▰▰▰▰▱▱▱▱3.4s
◉ online · ularnaga · $1.84
⌘ awaiting directive
- STATE
- ENGAGED
- MODEL
- opus-5-5
- UPTIME
- 00:41:12
◉ Claude is working · changes wait for the turn
- M Sources/Game/ScoreStore.swift ◆
- A Sources/Game/LeaderboardView.swift ◆
- M Sources/Game/GameView.swift
- ◆ edited by Claude this session
- 14:02 EXEC swift test
- 14:02 WRITE LeaderboardView.swift +71
- 14:02 EDIT ScoreStore.swift +38 −4
- 14:02 READ GameView.swift
◉ all systems nominal
01 // CORE
Read the session at a glance.
OUTER RING
Context
Sixty ticks fill clockwise with the context window: cyan, then gold past 70%, red past 90%.
SEGMENTS
Tool calls
Every tool call sends a spark into a segment, tinted by what it did: reads cyan, edits gold, commands green.
ARCS
Output
Three arcs turn with the reply as it streams, faster while Claude is writing.
ORBITS
Subagents
Each running subagent circles the core until it reports back.
Drawn natively at your display’s frame rate.
02 // METERS
Know before you hit the wall.
How full the context is, your weekly limit with the 5-hour window as the gold strip beneath it, and what the session has cost against a budget you set.
OPS LOG
- ◌ EXEC swift test
- ✓ WRITE LeaderboardView.swift
- ✓ EDIT ScoreStore.swift
- ▲ EXEC swift build exit 1
- ✓ READ GameView.swift
Every operation in order, faults flagged, with two minutes of activity above it.
03 // REPO CONTROL
Git that waits its turn.
Branch, ahead and behind, and the working tree, with the files Claude touched this session marked ◆. Fetch, pull with rebase, push, or sync main in one click. Stuck on a conflict? ASK CLAUDE types the request into its prompt.
- ◉ No force push. There is no button for it.
- ◉ Stash on confirm. A dirty tree asks first.
- ◉ Locked while Claude works. File-changing actions wait for the turn to end.
- ◉ No index-lock fights. Status checks never take git’s lock.
LAUNCH SEQUENCE
-
Right-click a folder in Finder → Open in Reactor. Or drop it on the Dock icon, or press ⌘O.
-
Your installed claude starts in that folder with your settings and account.
-
One window per folder. Open it again and it comes forward. ⇧⌘R restarts claude.
04 // QUERIES
Do I need Claude Code?
Yes. Reactor runs the claude command already installed on your Mac and uses your own Claude account. It does not include a subscription.
Why isn’t it on the Mac App Store?
The App Store sandbox won’t let an app start a command-line tool in any folder you choose, so Reactor is a notarized download instead.
Does Reactor send my code anywhere?
Reactor has no server and no analytics. The only network traffic it starts itself is git fetch, pull and push to your repository’s remote, when you press those buttons. Claude Code talks to Anthropic exactly as it does in any other terminal.
Can it mess up my repository?
It never force-pushes, stashes only after you confirm, and disables file-changing actions while Claude is working. Its status checks never take git’s index lock, so they can’t collide with Claude.
Does the core keep moving with Reduce Motion on?
No. With Reduce Motion on, the core stays still and only its readings change.
Is Reactor made by Anthropic?
No. Reactor is an independent app by frostycle.
Something else? Open a channel.
Bring the core online.
A notarized download for macOS 15 and later. Coming soon.
▸ COMING SOON