A native app that unifies all your coding agents

A developer just launched a native desktop app for coding agents, built in Rust on top of GPUI, the GPU-accelerated framework behind the Zed editor. The project debuted as a Show HN post on Hacker News, where it climbed to 171 points. The pitch is simple: run every coding agent in one place, on your own machine, with no Electron and no cloud sitting between you and your tools.

What stands out here is the focus on speed and ownership. Most agent frontends today are web wrappers. This one goes native and keeps your data local.

What was launched

The app is a Mac-native client (signed and notarized) that connects to multiple coding agents and pulls them into a single, unified timeline. According to the Hacker News post, it uses GPUI for instant launch and smooth scrolling through years of transcript history, sidestepping the sluggishness that plagues Electron-based tools.

Key capabilities

Here’s what the app brings to the table, based on the details shared on Hacker News:

  1. One timeline for every agent. Each agent connects over its strongest native interface, whether that’s stream-json, JSON-RPC, or live events. The app normalizes them into a single provider-neutral model, so you’re not juggling separate windows or formats.
  2. Git-backed checkpoints. Every prompt checkpoints your working tree under a hidden git ref. That means you can roll back your code and the provider conversation together, not just the chat log. This is the feature that matters most for anyone who’s watched an agent make a mess of a working directory.
  3. Keyboard-first control. ⌘N starts a session, Enter queues a follow-up while the agent works, ⌘Enter steers it mid-turn, and Escape stops it. Every control works without a mouse.
  4. Local by default. Projects, sessions, transcripts, and provider IDs all live on your disk. No account, no telemetry, and no company cloud in the loop.
  5. Quiet auto-updates. The app ships updates via Sparkle using binary deltas, so it stays current without nagging you for attention.

How it compares

The clearest contrast the post draws is against Electron. By going native with Rust and GPUI, the app claims performance that web-based agent tools struggle to match, especially when scrolling through long histories. The provider-neutral approach also sets it apart from single-vendor clients that lock you into one agent’s ecosystem. Instead of picking a camp, you route several agents through one interface.

The local-first stance is the other differentiator. Many agent platforms route your sessions and identifiers through their own servers. This app keeps all of that on your machine.

Availability

The post frames this as a working, distributable app: signed, notarized, and auto-updating on macOS. It didn’t spell out pricing or a formal release channel in the shared content, so anyone interested should check the original source for download and cost details. The heavy emphasis on notarization and Sparkle updates suggests it’s built for real daily use, not just a demo.

Why it matters

The number of coding agents keeps growing, and most developers now bounce between several. That fragmentation is a real workflow tax. An app that treats agents as interchangeable backends, checkpoints your code alongside the conversation, and runs fast without phoning home addresses three of the biggest complaints about the current crop of tools at once.

The git-checkpoint idea is the piece I’d watch. Tying code rollbacks to conversation rollbacks turns “undo” into something you can actually trust when an agent goes off the rails. If that works as described, it could become table stakes for the whole category.

A few caveats worth noting. It’s Mac-only for now, and being a solo Show HN launch, it’s early. Long-term maintenance and how many agents it supports out of the box are open questions. Still, the technical choices are deliberate and the priorities (speed, ownership, control) line up with what a lot of developers keep asking for.

You can find the full breakdown and try it yourself at the original source.

Scroll to Top