Prime Orbit turns Prime Agent into a focused desktop workspace. It combines projects, persistent conversations, streaming responses, tools, model configuration, MCP connections, background runs, and multi-window workflows in one interface.
Note
Prime Orbit is an independent community client and is not an official Prime Intellect product.
- Project-first workspace — keep projects and their conversations visible together, reorder them manually with drag and drop, search globally, archive old work, and see which agents are running or finished.
- Full Prime Agent conversations — stream answers, attach images and local files, choose models and reasoning levels, run tools, inspect context, and review Git changes.
- Prime Agent supervision — configure real heartbeats and scheduled jobs, inspect their next run, and pause, resume, cancel, or stop supervised work across sessions.
- Useful activity instead of protocol noise — tool calls and sub-agent activity are consolidated, repeated events are deduplicated, and large Python execution sequences can be grouped.
- Fast, lazy startup — Prime Orbit loads only the conversation you open. Other histories and agent processes are not eagerly restored.
- Resilient history — if the Prime Agent runtime is temporarily unavailable, the selected session can be reconstructed locally in read-only mode without duplicating the source transcript.
- Long-running work — agents can continue in the background, multiple windows share the same native runtime, and active sessions are released safely when no longer needed.
- One session catalog — top-level sessions created from the classic Prime Agent terminal appear lazily beside Orbit conversations when their project is linked.
- Providers and MCP — inspect configured providers, manage HTTP MCP servers globally or per project, and use OAuth or bearer-token environment variables without exposing secret values to the renderer.
- Signed in-app updates — check from Settings → About, download in the background, review release notes, and install only after explicit confirmation.
- Desktop polish — native file dialogs, custom context menus, keyboard navigation, light/dark/system themes, and complete English/French interface support.
Projects and conversations keep a stable, user-defined order. Expanding another project does not change the active conversation, while per-row status indicators make background work visible at a glance.
The conversation view separates the useful transcript from the execution timeline. Responses support Markdown, tool cards, grouped Python runs, session context, Git changes, and live agent state.
Prime Orbit detects provider authentication metadata without reading secret values. Custom HTTP MCP servers can be configured globally or for one project, with atomic writes and automatic backups.
Prime Agent's interactive /login, /logout, and OAuth MCP flows still run in its official terminal. Prime Orbit opens the correct terminal workflow and refreshes the public connection state afterward.
- Download the
.exeinstaller from the latest GitHub release. - Install and launch Prime Orbit.
- Open an existing project folder.
- Let the onboarding flow detect Prime Agent, or use Quick install to install it from the official repository.
- Configure a provider, create a conversation, and start working.
The 0.1.23 desktop build is validated on Windows 10/11 x64. Microsoft Edge WebView2 is normally already present on supported Windows installations.
Important
Prime Orbit 0.1.14 is the first updater-enabled release, so upgrades from 0.1.13 or earlier must be installed manually. Its updater payloads carry mandatory Tauri signatures, but the installers are not Authenticode-signed; Windows SmartScreen may still display an unknown-publisher warning. Verify the release SHA-256 manifest before running a manually downloaded installer.
For an existing or managed Prime Agent installation, Prime Orbit checks for:
- Node.js 22.8 or newer;
- npm;
- Git;
- Bash (Git Bash is supported on Windows).
The managed installer clones only the official Prime Agent repository and pins Prime Agent 0.8.0 to an exact verified tag and commit. Updates are prepared and verified in a fresh side-by-side runtime before Prime Orbit selects them, so a failed build cannot replace the working generation or collide with its locked Windows files.
Prime Orbit's development and Vite 8 build toolchain has a separate Node.js 22.12 minimum, declared in package.json and enforced by CI.
| Area | Included |
|---|---|
| Projects | Multiple local workspaces, stable manual order, typed deletion confirmation, archive/pin/search, direct Explorer access |
| Conversations | Persistent Prime Agent sessions, lazy loading, streaming, real steering/follow-up queues, official main-agent defaults, session naming and branches |
| Attachments | Native image thumbnails, opaque native file handles, drag and drop, bounded file handling without exposing source paths to the renderer |
| Tools | Tool cards, Python grouping, sub-agent activity, command palette, execution inspector |
| Git | Real per-file statistics, bounded diff previews, and protected Prime Agent prompts for commit/push and release workflows |
| Runtime | One native RPC process per conversation, terminal-session discovery, side-by-side managed generations, generation-scoped daemon sockets, background work, graceful stop and recovery |
| Supervision | Real heartbeats, schedules, queue steering/follow-up modes, and cross-session heartbeat management |
| Models | Provider catalogs, official global model/reasoning defaults, scoped selection, advisory RLM preferences, validated models.json, atomic save and backup |
| MCP | Built-in and custom HTTP servers, global/project scope, OAuth or bearer environment variable configuration |
| Reliability | Revisioned state, three-way multi-window merge, atomic persistence, runtime health checks, session fallback |
| Updates | Manual or startup checks, signed background downloads, multi-window progress, release notes, and guarded restart/install |
| Interface | English/French, light/dark/system themes, accessible dismissible menus, custom context menu |
- Prime Orbit does not enable application telemetry.
- Conversation transcripts remain owned by Prime Agent and are loaded from its RPC/session storage. Prime Orbit persists project metadata, preferences, drafts, and session references—not a competing transcript database.
- Provider secrets are not returned to the webview. For bearer authentication, Prime Orbit stores only the environment variable name.
- Configuration and workspace-state writes are atomic and revisioned. Managed JSON files receive backups before replacement.
- On Windows, Prime Orbit can recover an exact stale Prime Agent session lease only after proving that its recorded process is no longer alive. Live or unverifiable locks are preserved.
Warning
Prime Agent is not a sandbox. Its tools run with the permissions of your user account. Prime Orbit shows that permission boundary explicitly and does not present a UI profile as operating-system isolation.
Open Settings → Prime Agent and select Check again. Prime Orbit validates the real launch command instead of trusting a file path. If a source checkout is incomplete, rebuild it or use the managed installation.
Prime Orbit first tries the native RPC session. When possible, it then displays the selected JSONL history locally in read-only mode and keeps the original diagnostic visible. Use Retry loading after repairing Prime Agent; do not delete the conversation file.
Prime Agent versions affected by the Windows directory-rename behavior can leave a stale session lease after an interrupted process. Prime Orbit 0.1.8 and later safely quarantine only the exact stale lease after verifying its owner identity, then retry the normal RPC launch. Version 0.1.9 also normalizes the upstream Windows lease collision inside managed daemon workers.
Use Connections → Manage/Configure to open the official Prime Agent terminal flow. Complete /login or /mcp login <name>, then refresh connections and restart the active session when prompted.
React + TypeScript webview
│ typed Tauri commands and events
▼
Rust desktop backend
├─ project and revisioned UI-state persistence
├─ validated files, models, MCP, Git and diagnostics
├─ Prime Agent process broker and multi-window leases
└─ session recovery and read-only history fallback
│ JSON-RPC over stdio
▼
Prime Agent
The renderer never launches child processes directly. The Rust backend validates paths and inputs, owns each Prime Agent RPC process, fans events out to interested windows, and keeps runtime-only messages out of durable UI state.
- Node.js 22.12+
- npm
- Rust 1.88 or newer (the version declared and tested by the project)
- Tauri 2 system dependencies
- Git and Bash for the managed Prime Agent installation flow
npm install
npm run desktop:devnpm run test:unit
npm run check
cargo test --manifest-path src-tauri/Cargo.toml
cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warningsnpm run desktop:buildTauri writes platform bundles under src-tauri/target/release/bundle/.
Signed in-app updates use a separate release-only build and a draft-first GitHub workflow. See docs/UPDATER.md for the trust model, one-time key setup, bootstrap limitation, key rotation, and rollback policy.
Prime Orbit is an early desktop release. Version 0.1.23 ships Windows x64 NSIS and MSI installers through the signed stable update channel introduced in 0.1.14. macOS and Linux code paths exist, but official binaries have not yet been validated or published.
See CHANGELOG.md for release details.
Read CONTRIBUTING.md before proposing a change. Please report vulnerabilities through GitHub's private vulnerability-reporting flow as described in SECURITY.md, never in a public issue.
Prime Orbit is available under the MIT License. Prime Agent is a separate project distributed under its own license and terms.


