Open source · MIT · Rust + gpui
Give your agents room to work. Bring every project, terminal, chat, git worktree and pull request into one window, and know who needs you next.
Install instructions · v0.38.0
v0.38.0 · macOS, Linux and WindowsYour tools. Already at home.
Made for parallel work
Change requests from review to merge, a session panel that traces every turn, a code editor, a real terminal and a clear signal when an agent needs you, in one native desktop app.
Open a GitHub pull request or a GitLab merge request from the right panel and finish it in the window. Comment on diff lines, approve or request changes, re-run failed checks, read a job's log and merge when the bar says ready. Hand a request or a review thread to an agent from one dialog.
The session panel beside a Claude Code chat holds Environment, Context, Connectors, Trace and the branch's change request. Trace draws one lane per agent and subagent on a shared time axis, and it follows background agents until they finish. Click a lane to scroll the transcript to that step.
Move between projects and branches without losing your place. Each worktree is a card with its own terminals and chats, and every terminal keeps running while you work in another. Type in the search field to narrow the list by branch, project or tab title.
libghostty-vt drives it, with GPU rendering, true colour and inline images. Split a tab any way you like, and drag a terminal or a chat into the other pane: it keeps running.
See who is running, who has finished and who needs input. Each worktree card shows its most urgent state, and the Sessions tab lists every agent session across your projects, most recent first, so work running elsewhere stays in view.
Run an agent in a chat tab, with its context meter, or in a plain terminal. In a chat, questions and plan approvals wait in a panel above the composer, and a file path in the agent's answer is a link that opens the file in the editor. Claude Code speaks its own protocol, so a chat reports what the agent really did.
Markdown renders live while an agent writes it. Sirio draws a README's HTML and Mermaid diagrams in place, and PlantUML diagrams with the plantuml on your PATH. Code opens with git marks in the gutter, find and replace, a breadcrumb and a drawer for Problems and a search across the worktree. Add a language server, which Sirio fetches for most languages, and the same tab answers go to definition and find references.
Let agents work together. sirioctl is on your PATH in every terminal Sirio opens, so one agent can launch another, send a task, read the result, open a pull request's files and drive the built-in browser.
Pick up where you left off. An agent in a terminal keeps running through Quit, a crash or an update, and Sirio reattaches it with its scrollback on the next launch. Sirio also saves layouts, tabs and chat conversations on your machine and restores them, and a Claude Code chat continues its own session. A chat you close waits under Closed, ready to reopen.
A card in the corner offers each new version and never takes the keyboard while you type. Restart to update installs it and relaunches. While agents are at work, Install without restarting keeps the new version for your next launch, so an update never stops them.
Yours to inspect. Yours to build.
From the first design decision to the latest commit, everything about Sirio is public: the MIT licence, the Rust code and the specs behind each choice.
Fork it or embed it under the MIT licence. Sirio's own code ships under it, and each third-party part keeps its own licence.
gpui from Zed draws the window, the Zig library libghostty-vt runs the terminal, and bezel supplies the UI components. The shell ships without Electron, and the only webview is the Browser tab.
Design specs, implementation plans and the notes for every release sit next to the code in docs/. When a behaviour looks odd, you can read the reasoning that produced it.
Bring your own agents
Use the CLIs you already know and the accounts you already have. Each agent runs its own way, side by side.
Sirio speaks its native protocol, so a chat carries the real permissions, plan approvals and context accounting.
Install Hooks in Settings adds a notify command to Codex's config that reports back to Sirio over the control socket.
Sirio detects it from its terminal title and foreground process, and Install Hooks in Settings adds a plugin to OpenCode's config that reports its session id.
Sirio recognises it by its title convention and installs nothing for it.
Sirio recognises it by the π: title it sets, and talks to it over the agent protocol in a chat tab.
A home on your desktop
Sirio feels at home on your operating system. macOS leads, and Linux and Windows follow.
Apple Silicon, a signed and notarized .dmg, a native menu-bar roster and notifications from Sirio itself once you allow them. Every release starts here.
One AppImage, x86_64. A StatusNotifierItem tray and desktop notifications.
A per-user installer, x86_64. Native tray roster, ConPTY-backed terminals.
Yes. Sirio is MIT-licensed and developed at https://github.com/ai-sirio/sirio. Issues and pull requests are welcome, and the specs in docs/ explain how each part should work.
No. Sirio is a Rust application on gpui, the GPU-accelerated UI framework from Zed. The terminal is libghostty-vt. The only webview is the optional Browser tab, a native surface that sits next to your terminal.
On your machine. Sirio stores sessions, layouts and settings in a local SQLite database, with no account system and no telemetry. On its own it goes online for the update check, for the list of installable agents, which it caches for a day, and for the usage figures, which it reads with your own provider credentials. The rest happens when you ask: a Markdown preview loads its remote images, the pull request view talks to GitHub or GitLab once you open it, a pull request's diff fetches its commits with git, and a PlantUML server receives a diagram only if you name one in Settings.
No. In a terminal you start the agent CLIs you already have installed and logged into. A chat runs Claude Code, OpenCode and Oh-My-Pi through their own CLIs, and Settings can install the adapters that Codex and Pi need. Sirio reads Claude Code and Codex usage with the logins those CLIs keep, and OpenCode Go and Ollama Cloud usage with a session cookie you paste in Settings. For pull and merge requests it uses the gh or glab you already signed in with, or a read-only token you paste once.
Run one command: curl -fsSL https://dl.sirioai.app/install.sh | sh on macOS and Linux, or irm https://dl.sirioai.app/install.ps1 | iex on Windows. It puts the app where your operating system expects it and asks for no elevated access. Every tagged release also publishes a .dmg, an AppImage and a Windows installer on GitHub.
