A desktop command center for orchestrating many kiro-cli sessions from one
window. Bugyo runs a fleet of AI coding agents in parallel — each isolated in
its own git worktree — over the Agent Client Protocol (ACP), with a
diff‑review‑and‑merge flow and a human‑in‑the‑loop approval model.
Named for the bugyō (奉行), a magistrate who directed and governed subordinates.
Bugyo is an independent, open‑source project. It orchestrates
kiro-clibut is not affiliated with or endorsed by its maintainers.
The interactive orchestration pattern started life as a terminal‑bound tmux
control loop — powerful, but hard to observe or steer. Bugyo turns that pattern
into a native, observable, steerable GUI — inspired by
Conductor and the OpenAI Codex app, built on
kiro-cli's ACP transport. It is fully self‑contained, storing its state under
~/.kiro/bugyo/.
- Backend: Rust (Tauri v2) — ACP client, workspace/git manager, orchestrator.
- Frontend: React + TypeScript (Vite).
- Transport: newline‑delimited JSON‑RPC to
kiro-cli acpover stdio.
Prerequisites: Rust, Bun,
kiro-cli on PATH, and the platform Tauri prerequisites.
bun install
bun run tauri devPrebuilt bundles for macOS (universal), Linux (.AppImage/.deb), and Windows
(.msi/.exe) are attached to each GitHub Release.
macOS builds are ad-hoc signed but not notarized, so on first launch Gatekeeper will warn that the app is from an "unidentified developer." This is expected for now. To open it:
- Download and open the
.dmg, then drag Bugyo toApplications. - Launch it once — macOS blocks it and shows the warning.
- Open System Settings → Privacy & Security, scroll to the message about Bugyo being blocked, and click Open Anyway. (On older macOS you can instead right-click the app → Open.)
Or, from a terminal, clear the download's quarantine flag and launch normally:
xattr -cr /Applications/Bugyo.app # clears all extended attributes, or:
xattr -dr com.apple.quarantine /Applications/Bugyo.app # only the quarantine flagThis is a deliberate Gatekeeper bypass — only do it for a build you trust. You
only need to do this once. A future release will be Developer ID signed and
notarized to remove this step — see
docs/macos-code-signing.md.
VISION.md— what we're building and whyPLAN.md— phased roadmapAGENTS.md— contributor/agent operating guide & standardsCONTRIBUTING.md— how to contributedocs/— ACP notes, worktree notes, decisions (ADRs)
Licensed under the Apache License 2.0. See NOTICE.