Hiroshi
██   ██  ███████  ██████    ██████   ██████  ██   ██  ███████
██   ██    ██     ██   ██  ██    ██ ██       ██   ██    ██
███████    ██     ██████   ██    ██  ██████  ███████    ██
██   ██    ██     ██   ██  ██    ██       ██ ██   ██    ██
██   ██  ███████  ██   ██   ██████   ██████  ██   ██  ███████
HNo Electron, no web view

One GPU native cockpit for every agent in the swarm.

Hiroshi renders the whole cockpit on the GPU with GPUIX: the transcript, the composer, the surfaces and the window chrome are one surface at 120 frames per second, entirely on your machine.

The Hiroshi cockpit: the conversation sidebar, the transcript and the composer
Why native

Native down to the frame

React on GPUI, the GPU accelerated framework behind Zed. Instant launch, smooth scrolling through years of transcript, no Electron.

One surface, no DOM

The transcript, the composer, the panels and the window chrome are a single GPU surface. There is no browser engine between you and the work.

The window is yours

No native titlebar. The chrome spans the whole window, and the titlebar drags it, maximizes it and restores it on every platform.

Every surface next to the work

A browser, a terminal, a file tree and a review panel in the right drawer, so the run and the code it touches sit side by side.

Local by architecture

The workspace, the transcripts and the configuration live on your disk. No account, no telemetry, no cloud between you and your agents.

Quietly current

The integration suite drives the real app on the GPU test renderer, and it runs on macOS and Windows on every push.

Get started

Clone it and run it.

The native addon ships prebuilt for macOS, Windows and Linux, so there is no Rust toolchain to install. The repository carries the rules the app is built under, the integration suite, and the changelog.

bash
$ git clone https://github.com/hiroshi-os/Hiroshi
$ cd Hiroshi
$ bun install
$ bun run dev
Questions

Is this another Electron app?

No. Hiroshi is React on GPUIX, the React reconciler over Zed's native GPUI engine. There is no browser engine and no web view: the transcript, the composer and the window chrome are painted on the GPU at 120 frames per second.

What do I need to run it?

Bun and a GPU. Metal on macOS, Direct3D on Windows, Vulkan on Linux. The native addon ships prebuilt for all three, so there is no Rust toolchain to install.

Where does my data live?

On your disk. The workspace, the transcripts and the configuration are local files. No account, no telemetry, no cloud between you and your agents.

Is it finished?

Not yet. The cockpit is there, the orchestration behind it is not. The 1.0.0 milestone tracks what is left, and the issues under it are open to anyone.