Desktop App

The Omnigent desktop app gives you the full web UI in a native window, plus OS-level features a browser can't provide: notifications when your agent needs attention, a dock badge showing how many sessions are waiting, and multiple independent windows.

Download macOS App

Omnigent native desktop app showing the session chat and file workspace

Why use it over the browser?

OS notifications. Get notified when an agent finishes, asks for input, or a runner disconnects. Notifications show the first few lines of the agent's message and only fire for sessions you're not actively viewing.
Dock badge. See at a glance how many sessions need your attention, without switching to the app.
Multiple windows. Open additional windows with Cmd+N to watch multiple sessions or servers side by side.

Everything else (sessions, file editor, inline comments, collaboration) works exactly the same as the web UI.

Embedded browser

The desktop app includes an embedded browser pane your agent can drive directly. Five framework-owned tools are always available to every agent — you don't declare them in your agent YAML:

Tool	What it does
`browser_navigate`	Opens or navigates the pane to a URL, auto-opening the pane if it isn't open yet.
`browser_snapshot`	Captures an accessibility-tree snapshot: a `snapshot_id`, the current URL and title, and a YAML-shaped tree of interactive elements, each tagged with a `[ref=N]` id.
`browser_click`	Clicks an element by `ref` (preferred) or CSS `selector`. Pass the `snapshot_id` alongside a `ref` so a stale snapshot is rejected with a precise error.
`browser_type`	Focuses an input and types `text` into it, identified by `ref` or `selector`.
`browser_screenshot`	Captures a PNG of the pane for visual inspection. Prefer `browser_snapshot` when picking elements to act on — screenshots carry no refs.

Refs from a snapshot are far more stable than CSS selectors against generated class names and Shadow DOM, so the usual flow is: browser_navigate, then browser_snapshot to see what's on the page, then browser_click / browser_type using the refs it returned.

Because the browser runs inside the desktop window, these tools require the Omnigent desktop app to be running with the session open. If no desktop window is subscribed, the action fails cleanly with browser action timed out — is the session open in the Omnigent desktop app? rather than hanging.

Prerequisites

A running server. The server stores your sessions and serves the UI the desktop app connects to; run it locally with omni server start or point the app at a deployed URL.
At least one runner. A runner is the process that actually executes your agent. If you have cloud sandbox hosts set up, you'll be able to launch them from the app. Otherwise, register your machine by running omni host from your CLI.

Install

Platform	Format	Status
macOS	`.dmg`	Download
Linux	`.AppImage` or `.deb`	Download .deb · Download .AppImage
Windows	Installer (`.exe`)	Download

Get started

Omnigent desktop app first-launch setup screen

Launch the app. On first launch, you'll see a setup screen.
Enter your server URL. http://localhost:6767 if running locally, or your deployed server URL (e.g. https://your-app.onrender.com).
Start working. The app connects and shows the same UI you'd see in a browser.

Omnigent desktop app showing an agent conversation alongside the session workspace

The app remembers your server URL for future launches. To change it later, go to Server > Change Server.

Work with multiple servers

Each window connects to one server. To work with multiple servers at the same time:

Go to Server > New Window on Different Server
Enter the URL of the second server

Notifications and badge counts are combined across all connected servers.

Omnigent desktop app setup screen prompting for the server URL to connect to

Open a session from a link

The desktop app registers the omnigent:// URL scheme, so a link can open a specific session on a specific server the way a web link opens a page. The link names the server by host and the session by its conversation id:

omnigent://localhost:6767/c/conv_abc
omnigent://my-workspace.cloud.databricks.com/c/conv_xyz

The link carries no http/https — the app infers it the same way the setup screen does: http for a loopback host (localhost, 127.0.0.1), https for a remote host. A Databricks workspace mount is discovered automatically, so you don't include it in the link. Only /c/<session_id> links are recognized; other paths are ignored.

Clicking a link behaves like opening a page for a known site:

If a window is already connected to that server, the app reuses it and navigates to the session in place.
If you've connected to that server before but have no window open for it, the app opens it in a new window.
If you've never connected to that server, the app asks you to confirm first, since connecting to a server grants it privileges like notifications and registering this machine as a runner. Cancel is the default; only open links from servers you trust. Once you allow it, the server is remembered so future links open without a prompt.