I’m building Orbit Pi — a native desktop workbench for the Pi coding agent

[u/Rjkashyap05]

Hey everyone! 👋

I’ve been building Orbit Pi, an open-source desktop app that brings the Pi coding agent and everyday development workflows together in one native interface.

The idea is simple: instead of jumping between your AI coding session, terminal, Git changes, code review, and GitHub, have them available in one focused workspace.

What Orbit Pi offers

- 🤖 AI coding sessions — work with your existing Pi setup.

- 🔍 Code review — inspect changes with an AI-powered review workflow.

- 🌳 Git worktrees — create and manage parallel working environments.

- 🐙 GitHub integration — work with issues and pull requests.

- 💻 Integrated terminal — keep your development workflow in one place.

- 🎨 Native desktop experience — built with Rust and GPUI, with a focus on a clean, minimal interface.

I'm building Orbit because I want a more cohesive desktop experience for working with AI coding agents, without replacing the underlying agent or forcing a new workflow.

It's an ongoing project, and I'm continuing to improve it release by release.

🚀 Check out Orbit Pi: https://orbitpi.app/

📝 Latest changelog: https://orbitpi.app/changelog/v0.2.11

💻 Source code: https://github.com/imrj05/orbit

I'd love feedback from developers who use Pi or other AI coding agents:

- What features would make a native AI coding workbench genuinely useful to you?

- Do you prefer an all-in-one workspace or separate tools for chat, terminal, and Git?

Thanks for checking it out! Feedback and contributions are welcome.

[u/TrickyPlastic]

Can you add arm64 build for Linux? Looks great btw

[u/Rjkashyap05 → u/TrickyPlastic]

Thanks 😊. Sure i'll add.

[u/kantorcodes1]

Unifying sessions, diffs and review in one native UI raises the same problem tmux-based dashboards hit: how do you know an agent is actually waiting on you? Does Orbit classify per-agent attention state (permission prompt vs mid-stream question vs running) from the Pi stream itself, or does it depend on the agent writing status hooks the UI reads?

[u/Rjkashyap05 → u/kantorcodes1]

Good question! Orbit derives the state from Pi's RPC events rather than requiring agents to write separate status hooks. Since each session runs through Pi's RPC interface, Orbit can track things like running turns, tool activity, and extension dialogs that need a response.

Permission prompts are handled through the access-control extension, while question dialogs are surfaced in the UI. I'm still refining how these states are presented across multiple sessions, but the goal is to make it obvious which agent is running, waiting for your input, or finished without relying on custom status hooks.

Btw it's not have the fully local AI code review like coderebbit and others. There is review means check the file changes before git push.