diri

Native macOS orchestrator for coding agents. Run Claude Code, Codex, Cursor, Gemini and plain shells in parallel — across git worktrees or on remote hosts — each with a live status (working / needs-you / done) and tmux-like persistence: closing the app never kills a session, and a daemon restart brings conversations back.

brew install --cask cristicretu/diri/diri

Or download the latest DMG from Releases, open it, and drag diri to Applications. Either way it is the same universal build (Apple silicon and Intel), signed and notarized. diri updates itself from there.

The tap has to be named in full — a bare diri resolves only against Homebrew's default taps. The cask lives in cristicretu/homebrew-diri rather than homebrew-cask, which requires a notability threshold diri does not meet yet.

macOS 15 or newer.

1. Add a project directory and create a session for Claude Code, Codex, another supported agent, or a plain shell.
2. Start several sessions, ideally in separate git worktrees when they edit the same repository.
3. Watch the sidebar instead of every terminal: it shows which agents are working, waiting for you, or done.
4. Quit and reopen diri. The daemon keeps each PTY alive and replays the session when you return.

The getting-started guide covers remote hosts, MCP orchestration, diagnostics, local data, and uninstalling.

• Many agents at once. Each session is a real terminal with a real PTY. Group them by project, split them across git worktrees, or run them on a remote host over ssh+tmux.
• Status you can trust. diri reads what an agent actually painted on its screen and tells you which ones are working, which are waiting on you, and which are done — so you can watch ten sessions without reading ten terminals.
• Sessions outlive the app. A background daemon owns the PTYs. Quit diri, reopen it, and everything is still there.
• Agents can orchestrate agents. An MCP server lets a running agent spawn another one, watch it, read its output, and answer its prompts.

First-class status detection and resume are Claude Code and Codex. Cursor and Gemini run with partial support, and anything else runs as a terminal with running/exited status.

Two processes, one wire protocol:

• diri — the desktop app: Rust + GPUI. Owns the window, sidebar, terminal renderer, command palette, and usage accounting. Lives in diri/.
• dirijord — a headless Swift daemon, launched by the app and outliving it. Owns PTYs and child agent processes, an offset-addressed output log per session (for detach and replay), a headless terminal emulator for status detection, the session registry and persistence, worktrees, and the control socket.

dirijor is a small CLI: the MCP shim injected into agents, the hook and notify forwarders, and status/doctor. dirijord-holder owns the PTY master so sessions survive a daemon restart.

A Rust port of the engine is in progress in diri/crates/diri-engine, so that diri can run on Linux and Windows. It is not shipped — the released app runs the Swift daemon above. See diri/PORT.md for what is done and what is left.

Agent support is data, not code. Each agent is one JSON file in Sources/DirijorCore/Resources/manifests/ describing how to spawn it, how to resume, which keys approve or deny a prompt, and the screen rules that decide whether it is working, waiting, or done. Copy the closest existing manifest and adjust it — no Swift or Rust required. This is the easiest way to contribute.

Needs both toolchains: Rust (pinned in diri/rust-toolchain.toml) and Swift 6 with the Xcode command-line tools. The first Rust build compiles GPUI from a pinned Zed revision and takes a while.

swift build && swift test                  # engine
(cd diri && cargo build)                   # app
(cd diri && cargo run -p diri-app)         # run the app from source

diri/scripts/package.sh                    # full bundle
diri/scripts/install-local.sh

Run the same core checks as CI with one command:

./scripts/check.sh

diri/PACKAGING.md covers signing and notarization, diri/UPDATING.md the updater and release flow, diri/NODE.md running agents on a remote VPS node.

The documentation index links user and engineering guides.

See CONTRIBUTING.md. Bug reports, fixes, docs, and new agent manifests are all welcome. New contributors can start with good first issue or help wanted.

Questions belong in Discussions, reproducible bugs in Issues, and vulnerabilities in private security reports. See the roadmap, support guide, privacy notice, and governance for project expectations.

Diri's original source is Apache 2.0. Builds also contain third-party software under its own licenses; see LICENSE, NOTICE, and the machine-checked dependency policy in license-policy.json.