Back to the Finder

Omnigent

Open-source desktop app for Mac, Windows and Linux. Agents run on your computer or on your own server.

Product websiteomnigent.ai Compare with others Missing or wrong data?

Omnigent product interface, supplied by its publisher
Desktop app
Mac, Windows and Linux
Browser
Yes
Phone
IPhone, Android and phone browser
Command line
Yes
Agents
Claude Code, Codex, Cursor Agent, OpenCode, Pi, Grok and Antigravity
Your subscription
Works with your own plan
Agents run
On your computer and on your own server
Laptop closed
Keeps going
Isolation
Worktree, Container and VM
Parallel agents
Yes
Scheduled runs
Yes
Coordinator agent
Yes
Built-in issues
No
Pull requests
Yes
Review screen
Yes
Team
Shared sessions, roles and SSO
Self-hosting
Yes
Licence
Apache-2.0
Price from
Free
How it charges
No paid plan and bring your own key
Paid plans from
Not listed

Receipts

Checked
· oldest answer 2026-11-07
Findings
45 published · 19 cross-checked by a second agent · read them all
Sources
23 public pages on 2 sites: omnigent.ai, github.com
Screenshot
github.com, retrieved · first party repository · shows appearance, not capability
Method
Same rules for all 103 researched ADEs. How we check · Report wrong data

What it does

Where you use it

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

Source and scope for Where you use it

Agents it runs

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

Source and scope for Agents it runs

Accounts and subscriptions

Use native Claude/ChatGPT subscriptions, API credentials or compatible gateways.

Source and scope for Accounts and subscriptions

Where agents run

Separate server and hosts enable local or user-controlled remote execution. Managed sandbox launchers are configured on the user-operated server using its own provider credentials; no product-vendor runtime service is provisioned by this release.

Source and scope for Where agents run

How work is kept apart

Git worktrees, remote sandbox containers and optional OS policies are separate isolation mechanisms. The optional microsandbox provider additionally gives each host a hardware-isolated microVM on supported macOS/Linux hosts.

Source and scope for How work is kept apart

Parallel work

Polly runs several coding agents in parallel.

Source and scope for Parallel work

Scheduled runs

Persistent recurring automations launch agent sessions from server.

Source and scope for Scheduled runs

Git and pull requests

GitHub PR association, review and merge controls are documented.

Source and scope for Git and pull requests

Licence and source

Omnigent application repository is Apache-2.0.

Source and scope for Licence and source

Price

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

Source and scope for Price

JSON for agentsMarkdown for agents

Report wrong dataSuggest a missing ADE

Typed filters

Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.

Typed filter values
FilterValue
Desktop OS: macOSYes cross-checked
Desktop OS: WindowsYes cross-checked
Desktop OS: LinuxYes cross-checked
Web clientYes cross-checked
Phone access: Native iOSYes cross-checked
Phone access: Native AndroidYes cross-checked
Phone access: Phone browserYes cross-checked
CLIYes cross-checked
Coding agents: Claude CodeYes cross-checked
Coding agents: CodexYes cross-checked
Coding agents: Cursor AgentYes cross-checked
Coding agents: Gemini CLIUnknown
Coding agents: OpenCodeYes cross-checked
Coding agents: PiYes cross-checked
Coding agents: GrokYes cross-checked
Coding agents: AiderUnknown
Coding agents: AntigravityYes cross-checked
Use my subscriptionYes cross-checked
Where agents run: On your computerYes
Where agents run: On your own serverYes
Where agents run: In the vendor's cloudNo
Workspace isolation: Git worktreeYes
Workspace isolation: ContainerYes
Workspace isolation: VM or microVMYes
Parallel runsYes cross-checked
CoordinatorYes cross-checked
Native issue trackingNo
Unattended triggersYes
Shared promptingYes cross-checked
Team rolesYes cross-checked
SSOYes cross-checked
Pull request workflowYes cross-checked
Review interfaceYes cross-checked
Product license: Apache-2.0Yes. Apache-2.0 cross-checked
Product license: MITNo. Apache-2.0 cross-checked
Product license: GPL-3.0No. Apache-2.0 cross-checked
Product license: GPL-3.0-or-laterNo. Apache-2.0 cross-checked
Product license: AGPL-3.0No. Apache-2.0 cross-checked
Product license: AGPL-3.0-or-laterNo. Apache-2.0 cross-checked
Product license: Elastic License 2.0No. Apache-2.0 cross-checked
Product license: Custom termsNo. Apache-2.0 cross-checked
Product license: ProprietaryNo. Apache-2.0 cross-checked
Self-hostingYes cross-checked
Telemetry opt-outYes cross-checked
Free accessYes cross-checked
Starting price: FreeYes. Free cross-checked
Starting price: Up to $20/monthNo. Free cross-checked
Starting price: $21–40/monthNo. Free cross-checked
Starting price: $41–100/monthNo. Free cross-checked
Starting price: Over $100/monthNo. Free cross-checked
Starting price: Contact for pricingNo. Free cross-checked
Pricing model: Free, no paid planYes cross-checked
Pricing model: Free planNo
Pricing model: SubscriptionNo
Pricing model: Per seatNo
Pricing model: Usage-basedNo
Pricing model: Per machine or computeNo
Pricing model: Bring your own keyYes cross-checked
Pricing model: One-time purchaseNo
Paid plans from: No paid planUnknown
Paid plans from: $10 or less/monthUnknown
Paid plans from: $11–20/monthUnknown
Paid plans from: $21–40/monthUnknown
Paid plans from: $41–100/monthUnknown
Paid plans from: Over $100/monthUnknown
Paid plans from: Contact salesUnknown
Lifecycle status: ActiveUnknown
Lifecycle status: SunsettingUnknown
Keeps going with laptop closedYes
Open-source licenseYes. Apache-2.0 cross-checked
Any desktop appYes cross-checked
Paid plan up to $20/monthUnknown
Paid plan up to $40/monthUnknown
Any phone clientYes cross-checked

Filter receipts

Desktop OS: macOS: Yes cross-checked

Desktop OS: macOS

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Desktop OS: Windows: Yes cross-checked

Desktop OS: Windows

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Desktop OS: Linux: Yes cross-checked

Desktop OS: Linux

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Web client: Yes cross-checked

Web client

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Phone access: Native iOS: Yes cross-checked

Phone access: Native iOS

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Phone access: Native Android: Yes cross-checked

Phone access: Native Android

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Phone access: Phone browser: Yes cross-checked

Phone access: Phone browser

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

CLI: Yes cross-checked

CLI

Typed value: Yes.

Product CLI and REST API manage sessions, hosts and scheduled tasks.

  • Cli: omni/omnigent CLI.
  • Api: REST API for sessions, policies and automations.
  • Operations: Launch/attach/fork/export/import sessions and manage scheduler.
  • Authentication: Server auth accounts/OIDC and session ownership gate API operations.
  • Not established by this source pass: sdk, mcp_server, webhooks, stability.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

  3. Omnigent Scheduled tasks

    Finding: Recurring scheduled agent sessions use persistent task definitions, a server scheduler and a REST API. Minimum interval is ten minutes on connected hosts or continued sessions and one hour for new sandbox sessions. Overlapping fires of a task are skipped; no automatic retry or missed-fire replay.

Coding agents: Claude Code: Yes cross-checked

Coding agents: Claude Code

Typed value: Yes.

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi and Grok Build documented. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.
  • Custom adapters: Community ACP harness integration is supported.
  • Session integration: Native TUI mode mirrors vendor CLI; Direct mode uses integrated model/tool execution.
  • Mixed harness operation: Polly delegates Claude/Codex/Pi workers and cross-vendor reviewers.
  • Not established by this source pass: model_providers.
  • Antigravity is community-supported and requires the native runtime and configured credentials; direct and terminal modes differ.
  1. Omnigent Harness support

    Finding: Claude Code/Codex fully supported; Cursor/OpenCode/Pi maintained; Grok via ACP. Direct and native-TUI modes differ; plain model providers do not establish harness support.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

Coding agents: Codex: Yes cross-checked

Coding agents: Codex

Typed value: Yes.

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi and Grok Build documented. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.
  • Custom adapters: Community ACP harness integration is supported.
  • Session integration: Native TUI mode mirrors vendor CLI; Direct mode uses integrated model/tool execution.
  • Mixed harness operation: Polly delegates Claude/Codex/Pi workers and cross-vendor reviewers.
  • Not established by this source pass: model_providers.
  • Antigravity is community-supported and requires the native runtime and configured credentials; direct and terminal modes differ.
  1. Omnigent Harness support

    Finding: Claude Code/Codex fully supported; Cursor/OpenCode/Pi maintained; Grok via ACP. Direct and native-TUI modes differ; plain model providers do not establish harness support.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

Coding agents: Cursor Agent: Yes cross-checked

Coding agents: Cursor Agent

Typed value: Yes.

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi and Grok Build documented. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.
  • Custom adapters: Community ACP harness integration is supported.
  • Session integration: Native TUI mode mirrors vendor CLI; Direct mode uses integrated model/tool execution.
  • Mixed harness operation: Polly delegates Claude/Codex/Pi workers and cross-vendor reviewers.
  • Not established by this source pass: model_providers.
  • Antigravity is community-supported and requires the native runtime and configured credentials; direct and terminal modes differ.
  1. Omnigent Harness support

    Finding: Claude Code/Codex fully supported; Cursor/OpenCode/Pi maintained; Grok via ACP. Direct and native-TUI modes differ; plain model providers do not establish harness support.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

Coding agents: OpenCode: Yes cross-checked

Coding agents: OpenCode

Typed value: Yes.

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi and Grok Build documented. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.
  • Custom adapters: Community ACP harness integration is supported.
  • Session integration: Native TUI mode mirrors vendor CLI; Direct mode uses integrated model/tool execution.
  • Mixed harness operation: Polly delegates Claude/Codex/Pi workers and cross-vendor reviewers.
  • Not established by this source pass: model_providers.
  • Antigravity is community-supported and requires the native runtime and configured credentials; direct and terminal modes differ.
  1. Omnigent Harness support

    Finding: Claude Code/Codex fully supported; Cursor/OpenCode/Pi maintained; Grok via ACP. Direct and native-TUI modes differ; plain model providers do not establish harness support.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

Coding agents: Pi: Yes cross-checked

Coding agents: Pi

Typed value: Yes.

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi and Grok Build documented. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.
  • Custom adapters: Community ACP harness integration is supported.
  • Session integration: Native TUI mode mirrors vendor CLI; Direct mode uses integrated model/tool execution.
  • Mixed harness operation: Polly delegates Claude/Codex/Pi workers and cross-vendor reviewers.
  • Not established by this source pass: model_providers.
  • Antigravity is community-supported and requires the native runtime and configured credentials; direct and terminal modes differ.
  1. Omnigent Harness support

    Finding: Claude Code/Codex fully supported; Cursor/OpenCode/Pi maintained; Grok via ACP. Direct and native-TUI modes differ; plain model providers do not establish harness support.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

Coding agents: Grok: Yes cross-checked

Coding agents: Grok

Typed value: Yes.

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi and Grok Build documented. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.
  • Custom adapters: Community ACP harness integration is supported.
  • Session integration: Native TUI mode mirrors vendor CLI; Direct mode uses integrated model/tool execution.
  • Mixed harness operation: Polly delegates Claude/Codex/Pi workers and cross-vendor reviewers.
  • Not established by this source pass: model_providers.
  • Antigravity is community-supported and requires the native runtime and configured credentials; direct and terminal modes differ.
  1. Omnigent Harness support

    Finding: Claude Code/Codex fully supported; Cursor/OpenCode/Pi maintained; Grok via ACP. Direct and native-TUI modes differ; plain model providers do not establish harness support.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

Coding agents: Antigravity: Yes cross-checked

Coding agents: Antigravity

Typed value: Yes.

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  • Harnesses: Claude Code, Codex, Cursor, OpenCode, Pi and Grok Build documented. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.
  • Not established by this source pass: model_providers.
  • Antigravity is community-supported and requires the native runtime and configured credentials; direct and terminal modes differ.
  1. Omnigent Antigravity support at v0.21.0

    Finding: Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  2. Omnigent Antigravity support at v0.21.0

    Finding: Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

Use my subscription: Yes cross-checked

Use my subscription

Typed value: Yes.

Use native Claude/ChatGPT subscriptions, API credentials or compatible gateways.

  • Agent subscriptions: Claude Pro/Max and ChatGPT plan via official claude/codex CLI login.
  • Api accounts: Own Anthropic/OpenAI/provider keys.
  • Local models: Ollama/vLLM compatible gateway route.
  • Account switching: Setup manages credentials grouped by agent; defaults per agent.
  • Provider restrictions: Harness modes/providers differ; native CLI owns its login and config.
  • Not established by this source pass: vendor_credits, vendor_account_requirement.
  1. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Where agents run: On your computer: Yes

Where agents run: On your computer

Typed value: Yes.

Separate server and hosts enable local or user-controlled remote execution. Managed sandbox launchers are configured on the user-operated server using its own provider credentials; no product-vendor runtime service is provisioned by this release.

  • Local: Local server/host launch.
  • Byo remote: Run host on VPS/dev box; macOS/Linux desktop SSH enrollment starts background outbound host.
  • Self hosted: Docker/server deployment on own infrastructure.
  • Provisioning: Own host or configured third-party sandbox provider.
  • Client disconnect: Remote host continues outbound connection after setup SSH closes.
  • Other device continuation: Reach server from desktop/browser/phone while remote runner works.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

Where agents run: On your own server: Yes

Where agents run: On your own server

Typed value: Yes.

Separate server and hosts enable local or user-controlled remote execution. Managed sandbox launchers are configured on the user-operated server using its own provider credentials; no product-vendor runtime service is provisioned by this release.

  • Local: Local server/host launch.
  • Byo remote: Run host on VPS/dev box; macOS/Linux desktop SSH enrollment starts background outbound host.
  • Self hosted: Docker/server deployment on own infrastructure.
  • Provisioning: Own host or configured third-party sandbox provider.
  • Client disconnect: Remote host continues outbound connection after setup SSH closes.
  • Other device continuation: Reach server from desktop/browser/phone while remote runner works.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

Where agents run: In the vendor's cloud: No

Where agents run: In the vendor's cloud

Typed value: No.

Separate server and hosts enable local or user-controlled remote execution. Managed sandbox launchers are configured on the user-operated server using its own provider credentials; no product-vendor runtime service is provisioned by this release.

  • Managed cloud: The scoped managed-host provider factory runs under the user-operated server configuration and its own provider credentials, without an Omnigent-vendor runtime service.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent managed host providers

    Finding: The scoped server registers the microsandbox provider and constructs its launcher from the server configuration. Runtime providers and credentials belong to the user-operated server, rather than an Omnigent-hosted execution service.

Workspace isolation: Git worktree: Yes

Workspace isolation: Git worktree

Typed value: Yes.

Git worktrees, remote sandbox containers and optional OS policies are separate isolation mechanisms. The optional microsandbox provider additionally gives each host a hardware-isolated microVM on supported macOS/Linux hosts.

  • Worktree: Polly worker tasks each get Git worktree.
  • Container: Cloud sandbox host described as isolated remote container.
  • Os sandbox: Linux bwrap or macOS Seatbelt policy.
  • Filesystem: Policy read/write path allowances.
  • Network: Sandbox allow_network config.
  • Security boundary: Default co-driven local sessions are non-sandboxed and share host access; use explicit sandbox policies/remote containers.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

  3. Omnigent Policy reference

    Finding: Declarative policies allow/deny/ask actions; max tool calls, cost caps and thresholds. OS sandbox uses Linux bwrap/macOS seatbelt; plain sessions are not sandboxed by default. Generic agent-start DENY/ASK does not block launch.

Workspace isolation: Container: Yes

Workspace isolation: Container

Typed value: Yes.

Git worktrees, remote sandbox containers and optional OS policies are separate isolation mechanisms. The optional microsandbox provider additionally gives each host a hardware-isolated microVM on supported macOS/Linux hosts.

  • Worktree: Polly worker tasks each get Git worktree.
  • Container: Cloud sandbox host described as isolated remote container.
  • Os sandbox: Linux bwrap or macOS Seatbelt policy.
  • Filesystem: Policy read/write path allowances.
  • Network: Sandbox allow_network config.
  • Security boundary: Default co-driven local sessions are non-sandboxed and share host access; use explicit sandbox policies/remote containers.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

  3. Omnigent Policy reference

    Finding: Declarative policies allow/deny/ask actions; max tool calls, cost caps and thresholds. OS sandbox uses Linux bwrap/macOS seatbelt; plain sessions are not sandboxed by default. Generic agent-start DENY/ASK does not block launch.

Workspace isolation: VM or microVM: Yes

Workspace isolation: VM or microVM

Typed value: Yes.

Git worktrees, remote sandbox containers and optional OS policies are separate isolation mechanisms. The optional microsandbox provider additionally gives each host a hardware-isolated microVM on supported macOS/Linux hosts.

  • Vm: The optional microsandbox provider boots each host in a libkrun microVM, with server-managed and CLI bootstrap modes. Requires Apple Silicon macOS or Linux KVM; the runtime is beta.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent microsandbox deployment

    Finding: The optional microsandbox provider boots each Omnigent host in its own hardware-isolated microVM using libkrun. It is fully local/self-hosted, supports Apple Silicon macOS and Linux with KVM, and uses a beta pinned runtime. Server-managed sessions and CLI sandbox create are documented.

  2. Omnigent managed host providers

    Finding: The scoped server registers the microsandbox provider and constructs its launcher from the server configuration. Runtime providers and credentials belong to the user-operated server, rather than an Omnigent-hosted execution service.

Parallel runs: Yes cross-checked

Parallel runs

Typed value: Yes.

Polly runs several coding agents in parallel.

  • Concurrent sessions: Claude/Codex workers operate simultaneously.
  • Concurrent tasks: Each worker handles scoped subtask/worktree.
  • Status visibility: Agents panel shows working/idle/finished.
  • Not established by this source pass: quotas, observed_concurrency.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

Coordinator: Yes cross-checked

Coordinator

Typed value: Yes.

Shipped Polly orchestrator delegates inspectable mixed-harness children.

  • Roles: Polly tech lead, coding workers and reviewers.
  • Model harness effort: Workers can use Claude Code, Codex or Pi; custom YAML controls agents.
  • Messages: Open child view and send message to steer.
  • Results return: Polly picks up child results and routes review.
  • Cross harness: Mixed Claude/Codex/Pi.
  • Orchestration owner: Product-shipped Polly workflow.
  • Live progress: Agent panel shows child state, conversation/files/terminal.
  • Retained results: Server persists sessions and tool history.
  • Invocation: omni polly or select Polly agent.
  • Not established by this source pass: activation, authentication, followup.
  1. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

  2. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Native issue tracking: No

Native issue tracking

Typed value: No.

The scoped native UI and database have agent sessions, project grouping and scheduled automation definitions. Bounded inspection found no independent native issue/backlog/to-do work-item list; scheduled trigger definitions and run statuses are separate.

  • Create: Native stores/routes expose sessions, projects and schedules rather than issue/backlog work-item creation.
  • Task session separation: The native work record is a session; the separate task store contains scheduled trigger definitions, not backlog work items.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent native work and schedule records

    Finding: The scoped /tasks interface persists scheduled trigger definitions and run history; ordinary agent work is stored as sessions grouped into projects. Inspection of native stores, routes and Tasks UI found no independent backlog/to-do/issue work-item CRUD with open/in-progress/done states. Scheduled job state is not issue state.

Unattended triggers: Yes

Unattended triggers

Typed value: Yes.

Persistent recurring automations launch agent sessions from server.

  • Schedules: Minimum ten-minute interval on connected hosts or continued sessions; one hour for new sandbox sessions.
  • Recurring tasks: Saved scheduled task definition.
  • Scheduler location: Server scheduler; selected execution host must be available.
  • Overlaps: Overlapping fires of the same task are skipped while the previous firing is still dispatching.
  • Not established by this source pass: events, completion_conditions, retries, client_independence.
  1. Omnigent Scheduled tasks

    Finding: Recurring scheduled agent sessions use persistent task definitions, a server scheduler and a REST API. Minimum interval is ten minutes on connected hosts or continued sessions and one hour for new sandbox sessions. Overlapping fires of a task are skipped; no automatic retry or missed-fire replay.

Shared prompting: Yes cross-checked

Shared prompting

Typed value: Yes.

Edit collaborators co-prompt the same live session.

  • Visibility: Live messages/tool/file changes stream to connected viewers.
  • Coprompting: Edit users send messages that execute on owner host.
  • Conflicts: Owner alone changes agent/MCP/permission mode.
  • Attribution: Multi-author messages include account labels; persisted authors unchanged.
  • Permissions: Read/Edit/Owner access matrix.
  • Not established by this source pass: discussion, comments, presence, ordering, plan_restrictions, owner_online.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

Team roles: Yes cross-checked

Team roles

Typed value: Yes.

Admin/user management, OIDC SSO and Read/Edit/Owner boundaries are documented.

  • Organization roles: Admin manages Members/Policies/Sharing; signed-in users manage own account.
  • Task roles: Read/Edit/Owner session access.
  • Membership: Built-in invite links or IdP sign-in.
  • Sso: OIDC or trusted-header SSO; Google/GitHub/Okta/Microsoft.
  • Unauthorized access: Edit collaborator raw shell endpoint returns 403; owner/admin required.
  • Revocation: Member removal/password reset revokes documented account access.
  • Not established by this source pass: project_roles, provisioning, plan_scope.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  2. Omnigent Auth and SSO

    Finding: Invite-only built-in accounts or OIDC/header SSO. Admin manages membership/policies/sharing; owner/Edit/Read permissions scope sessions. First admin setup must be completed by operator.

SSO: Yes cross-checked

SSO

Typed value: Yes.

Admin/user management, OIDC SSO and Read/Edit/Owner boundaries are documented.

  • Organization roles: Admin manages Members/Policies/Sharing; signed-in users manage own account.
  • Task roles: Read/Edit/Owner session access.
  • Membership: Built-in invite links or IdP sign-in.
  • Sso: OIDC or trusted-header SSO; Google/GitHub/Okta/Microsoft.
  • Unauthorized access: Edit collaborator raw shell endpoint returns 403; owner/admin required.
  • Revocation: Member removal/password reset revokes documented account access.
  • Not established by this source pass: project_roles, provisioning, plan_scope.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  2. Omnigent Auth and SSO

    Finding: Invite-only built-in accounts or OIDC/header SSO. Admin manages membership/policies/sharing; owner/Edit/Read permissions scope sessions. First admin setup must be completed by operator.

Pull request workflow: Yes cross-checked

Pull request workflow

Typed value: Yes.

GitHub PR association, review and merge controls are documented.

  • Branches: Composer chooses worktree branch and base.
  • Worktrees: Fresh/random worktree launch options.
  • Pull requests: Session tracks GitHub PRs and provides management UI.
  • Comments: Read/reply/start inline review conversations.
  • Product state: Checks/request state/merge actions; stale/incomplete data flagged.
  • Not established by this source pass: commits, ci_response, rebase, conflicts.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pull request workflow

    Finding: Session PR associations persist server-side; description, checks, comments, changed files and diffs stay on and are served by the host provider integration. Incomplete data is flagged; linked request summaries remain when host offline; head/base revisions are validated before diffs are returned.

Review interface: Yes cross-checked

Review interface

Typed value: Yes.

Changes and PR UI support diff review and inline GitHub conversations.

  • Change understanding: File diffs/line counts and linked PR details.
  • Evidence navigation: Session PR panel links request and change diffs.
  • Comments: Inline GitHub review threads can be read/replied/created.
  • Request changes: Review conversations can direct follow-up agent changes.
  • Not established by this source pass: pending_reviews, shipping_guidance, effort, missed_evidence, keyboard, narrow_screen, context_switching, roles, retained_context.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pull request workflow

    Finding: Session PR associations persist server-side; description, checks, comments, changed files and diffs stay on and are served by the host provider integration. Incomplete data is flagged; linked request summaries remain when host offline; head/base revisions are validated before diffs are returned.

Product license: Apache-2.0: Yes. Apache-2.0 cross-checked

Product license: Apache-2.0

Typed value: Yes. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Product license: MIT: No. Apache-2.0 cross-checked

Product license: MIT

Typed value: No. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Product license: GPL-3.0: No. Apache-2.0 cross-checked

Product license: GPL-3.0

Typed value: No. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Product license: GPL-3.0-or-later: No. Apache-2.0 cross-checked

Product license: GPL-3.0-or-later

Typed value: No. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Product license: AGPL-3.0: No. Apache-2.0 cross-checked

Product license: AGPL-3.0

Typed value: No. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Product license: AGPL-3.0-or-later: No. Apache-2.0 cross-checked

Product license: AGPL-3.0-or-later

Typed value: No. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Product license: Elastic License 2.0: No. Apache-2.0 cross-checked

Product license: Elastic License 2.0

Typed value: No. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Product license: Custom terms: No. Apache-2.0 cross-checked

Product license: Custom terms

Typed value: No. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Product license: Proprietary: No. Apache-2.0 cross-checked

Product license: Proprietary

Typed value: No. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Self-hosting: Yes cross-checked

Self-hosting

Typed value: Yes.

Full server/host is self-hostable and sessions export/import JSONL.

  • Self hosting: Docker or own-server deployment.
  • Export: Web/CLI full session JSONL export.
  • Import: omnigent session import accepts exported JSONL.
  • Formats: JSONL and YAML agent bundles; SQLite/Postgres history.
  • History portability: Export includes raw committed items in chronological order.
  • Not established by this source pass: vendor_dependencies, cancellation, account_independence.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

Telemetry opt-out: Yes cross-checked

Telemetry opt-out

Typed value: Yes.

Anonymous telemetry defaults on and has explicit opt-outs; session storage belongs to own server.

  • Code data: Vendor says telemetry excludes file contents/tool arguments.
  • Prompts: Vendor says telemetry excludes prompts/message content.
  • Credentials: Vendor says telemetry excludes credentials.
  • Logs: Conversations/tools persisted in own database.
  • Telemetry disclosure: Server anonymous usage collection.
  • Telemetry defaults: Enabled from v0.6.0.
  • Telemetry controls: OMNIGENT_ANALYTICS=0, DO_NOT_TRACK=1 or telemetry:false.
  • Not established by this source pass: artifacts, retention, deletion, training, residency, subprocessors, consent_prompt, provider_separation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Usage telemetry

    Finding: Anonymous server usage telemetry defaults on; opt out with OMNIGENT_ANALYTICS=0, DO_NOT_TRACK=1 or telemetry:false. Prompts/files/credentials excluded according to vendor.

Free access: Yes cross-checked

Free access

Typed value: Yes.

Apache application is freely installable/self-hostable; providers and infrastructure cost separately.

  • Ongoing free: Free source/application use under Apache-2.0.
  • Self host cost: User provides server/compute and model credentials.
  • Free scenarios: Local/own-server app, Polly and shared sessions available from public distribution.
  • Not established by this source pass: trial, credits_trial, paid_only, early_access, card_required, usage_caps, paid_evaluation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Starting price: Free: Yes. Free cross-checked

Starting price: Free

Typed value: Yes. Free.

Apache application is freely installable/self-hostable; providers and infrastructure cost separately.

  • Ongoing free: Free source/application use under Apache-2.0.
  • Self host cost: User provides server/compute and model credentials.
  • Free scenarios: Local/own-server app, Polly and shared sessions available from public distribution.
  • Not established by this source pass: trial, credits_trial, paid_only, early_access, card_required, usage_caps, paid_evaluation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Starting price: Up to $20/month: No. Free cross-checked

Starting price: Up to $20/month

Typed value: No. Free.

Apache application is freely installable/self-hostable; providers and infrastructure cost separately.

  • Ongoing free: Free source/application use under Apache-2.0.
  • Self host cost: User provides server/compute and model credentials.
  • Free scenarios: Local/own-server app, Polly and shared sessions available from public distribution.
  • Not established by this source pass: trial, credits_trial, paid_only, early_access, card_required, usage_caps, paid_evaluation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Starting price: $21–40/month: No. Free cross-checked

Starting price: $21–40/month

Typed value: No. Free.

Apache application is freely installable/self-hostable; providers and infrastructure cost separately.

  • Ongoing free: Free source/application use under Apache-2.0.
  • Self host cost: User provides server/compute and model credentials.
  • Free scenarios: Local/own-server app, Polly and shared sessions available from public distribution.
  • Not established by this source pass: trial, credits_trial, paid_only, early_access, card_required, usage_caps, paid_evaluation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Starting price: $41–100/month: No. Free cross-checked

Starting price: $41–100/month

Typed value: No. Free.

Apache application is freely installable/self-hostable; providers and infrastructure cost separately.

  • Ongoing free: Free source/application use under Apache-2.0.
  • Self host cost: User provides server/compute and model credentials.
  • Free scenarios: Local/own-server app, Polly and shared sessions available from public distribution.
  • Not established by this source pass: trial, credits_trial, paid_only, early_access, card_required, usage_caps, paid_evaluation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Starting price: Over $100/month: No. Free cross-checked

Starting price: Over $100/month

Typed value: No. Free.

Apache application is freely installable/self-hostable; providers and infrastructure cost separately.

  • Ongoing free: Free source/application use under Apache-2.0.
  • Self host cost: User provides server/compute and model credentials.
  • Free scenarios: Local/own-server app, Polly and shared sessions available from public distribution.
  • Not established by this source pass: trial, credits_trial, paid_only, early_access, card_required, usage_caps, paid_evaluation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Starting price: Contact for pricing: No. Free cross-checked

Starting price: Contact for pricing

Typed value: No. Free.

Apache application is freely installable/self-hostable; providers and infrastructure cost separately.

  • Ongoing free: Free source/application use under Apache-2.0.
  • Self host cost: User provides server/compute and model credentials.
  • Free scenarios: Local/own-server app, Polly and shared sessions available from public distribution.
  • Not established by this source pass: trial, credits_trial, paid_only, early_access, card_required, usage_caps, paid_evaluation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Pricing model: Free, no paid plan: Yes cross-checked

Pricing model: Free, no paid plan

Typed value: Yes.

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent homepage

    Finding: Says Omnigent is open source under Apache 2.0. The page shows no price, plan or pricing page.

  2. omnigent-ai/omnigent LICENSE (Apache-2.0)

    Finding: The Apache License 2.0 grants a perpetual, worldwide, no-charge, royalty-free copyright license to use and reproduce the code.

Pricing model: Free plan: No

Pricing model: Free plan

Typed value: No.

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • Model cost: Models are reached through your own first-party API key or Claude/ChatGPT subscription, so the provider bills for usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent README

    Finding: Says Omnigent works with any model, using a first-party vendor API key or an existing Claude Pro/Max or ChatGPT subscription. It also offers cost-budget policies.

  2. Omnigent homepage

    Finding: Says Omnigent is open source under Apache 2.0. The page shows no price, plan or pricing page.

  3. omnigent-ai/omnigent LICENSE (Apache-2.0)

    Finding: The Apache License 2.0 grants a perpetual, worldwide, no-charge, royalty-free copyright license to use and reproduce the code.

Pricing model: Subscription: No

Pricing model: Subscription

Typed value: No.

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • Model cost: Models are reached through your own first-party API key or Claude/ChatGPT subscription, so the provider bills for usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent README

    Finding: Says Omnigent works with any model, using a first-party vendor API key or an existing Claude Pro/Max or ChatGPT subscription. It also offers cost-budget policies.

  2. Omnigent homepage

    Finding: Says Omnigent is open source under Apache 2.0. The page shows no price, plan or pricing page.

  3. omnigent-ai/omnigent LICENSE (Apache-2.0)

    Finding: The Apache License 2.0 grants a perpetual, worldwide, no-charge, royalty-free copyright license to use and reproduce the code.

Pricing model: Per seat: No

Pricing model: Per seat

Typed value: No.

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • Model cost: Models are reached through your own first-party API key or Claude/ChatGPT subscription, so the provider bills for usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent README

    Finding: Says Omnigent works with any model, using a first-party vendor API key or an existing Claude Pro/Max or ChatGPT subscription. It also offers cost-budget policies.

  2. Omnigent homepage

    Finding: Says Omnigent is open source under Apache 2.0. The page shows no price, plan or pricing page.

  3. omnigent-ai/omnigent LICENSE (Apache-2.0)

    Finding: The Apache License 2.0 grants a perpetual, worldwide, no-charge, royalty-free copyright license to use and reproduce the code.

Pricing model: Usage-based: No

Pricing model: Usage-based

Typed value: No.

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • Model cost: Models are reached through your own first-party API key or Claude/ChatGPT subscription, so the provider bills for usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent README

    Finding: Says Omnigent works with any model, using a first-party vendor API key or an existing Claude Pro/Max or ChatGPT subscription. It also offers cost-budget policies.

  2. Omnigent homepage

    Finding: Says Omnigent is open source under Apache 2.0. The page shows no price, plan or pricing page.

  3. omnigent-ai/omnigent LICENSE (Apache-2.0)

    Finding: The Apache License 2.0 grants a perpetual, worldwide, no-charge, royalty-free copyright license to use and reproduce the code.

Pricing model: Per machine or compute: No

Pricing model: Per machine or compute

Typed value: No.

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • Model cost: Models are reached through your own first-party API key or Claude/ChatGPT subscription, so the provider bills for usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent README

    Finding: Says Omnigent works with any model, using a first-party vendor API key or an existing Claude Pro/Max or ChatGPT subscription. It also offers cost-budget policies.

  2. Omnigent homepage

    Finding: Says Omnigent is open source under Apache 2.0. The page shows no price, plan or pricing page.

  3. omnigent-ai/omnigent LICENSE (Apache-2.0)

    Finding: The Apache License 2.0 grants a perpetual, worldwide, no-charge, royalty-free copyright license to use and reproduce the code.

Pricing model: Bring your own key: Yes cross-checked

Pricing model: Bring your own key

Typed value: Yes.

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • Model cost: Models are reached through your own first-party API key or Claude/ChatGPT subscription, so the provider bills for usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent README

    Finding: Says Omnigent works with any model, using a first-party vendor API key or an existing Claude Pro/Max or ChatGPT subscription. It also offers cost-budget policies.

Pricing model: One-time purchase: No

Pricing model: One-time purchase

Typed value: No.

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • Model cost: Models are reached through your own first-party API key or Claude/ChatGPT subscription, so the provider bills for usage.
  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent README

    Finding: Says Omnigent works with any model, using a first-party vendor API key or an existing Claude Pro/Max or ChatGPT subscription. It also offers cost-budget policies.

  2. Omnigent homepage

    Finding: Says Omnigent is open source under Apache 2.0. The page shows no price, plan or pricing page.

  3. omnigent-ai/omnigent LICENSE (Apache-2.0)

    Finding: The Apache License 2.0 grants a perpetual, worldwide, no-charge, royalty-free copyright license to use and reproduce the code.

Keeps going with laptop closed: Yes

Keeps going with laptop closed

Typed value: Yes.

Separate server and hosts enable local or user-controlled remote execution. Managed sandbox launchers are configured on the user-operated server using its own provider credentials; no product-vendor runtime service is provisioned by this release.

  • Local: Local server/host launch.
  • Byo remote: Run host on VPS/dev box; macOS/Linux desktop SSH enrollment starts background outbound host.
  • Self hosted: Docker/server deployment on own infrastructure.
  • Provisioning: Own host or configured third-party sandbox provider.
  • Client disconnect: Remote host continues outbound connection after setup SSH closes.
  • Other device continuation: Reach server from desktop/browser/phone while remote runner works.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

Open-source license: Yes. Apache-2.0 cross-checked

Open-source license

Typed value: Yes. Apache-2.0.

Omnigent application repository is Apache-2.0.

  • Client license: Apache-2.0.
  • Server license: Apache-2.0.
  • Source visibility: Public application source.
  • Source revision: f726587bb0a9db9ee4eb23b2564fe9e1f5d69763.
  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

Any desktop app: Yes cross-checked

Any desktop app

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

Any phone client: Yes cross-checked

Any phone client

Typed value: Yes.

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Desktop os: macOS .dmg, Linux .deb/AppImage, Windows .exe.
  • Mobile apps: Native iOS/Android server-connected apps.
  • Browser: Full web UI from server.
  • Mobile browser: Full touch-optimized browser UI.
  • Cli: omni/omnigent launch, host, attach and session commands.
  • Task actions: Chat, browse files, view changes and comment from phone.
  • Notifications: Desktop completion/input/disconnect; iOS foreground-only.
  • Cross device continuity: Same live session syncs terminal/browser/phone.
  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

All public findings

Findings may summarize a source. They are not presented as verbatim statements.

omnigent:ACC-01: Native desktop on three OSs, native phone apps, browser and CLI connect to product server. cross-checked

omnigent:ACC-01

Native desktop on three OSs, native phone apps, browser and CLI connect to product server.

  • Not established by this source pass: editor_extensions.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:ACC-02: Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling. cross-checked

omnigent:ACC-02

Named coding harnesses support direct/native modes with distinct support levels. Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  • Not established by this source pass: model_providers.
  • Antigravity is community-supported and requires the native runtime and configured credentials; direct and terminal modes differ.
  1. Omnigent Harness support

    Finding: Claude Code/Codex fully supported; Cursor/OpenCode/Pi maintained; Grok via ACP. Direct and native-TUI modes differ; plain model providers do not establish harness support.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

  3. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

  4. Omnigent Antigravity support at v0.21.0

    Finding: Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

  5. Omnigent Antigravity support at v0.21.0

    Finding: Omnigent v0.21.0 ships the antigravity-native harness, launched with omnigent antigravity or omnigent agy, with CLI/web setup and approval handling.

omnigent:ACC-03: Use native Claude/ChatGPT subscriptions, API credentials or compatible gateways. cross-checked

omnigent:ACC-03

Use native Claude/ChatGPT subscriptions, API credentials or compatible gateways.

  • Not established by this source pass: vendor_credits, vendor_account_requirement.
  1. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:ACC-04: Local setup or user-hosted server/runner deployment are documented.

omnigent:ACC-04

Local setup or user-hosted server/runner deployment are documented.

  • Not established by this source pass: no_git, local_git_without_remote, hosted_git.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  3. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:ACC-05: Product CLI and REST API manage sessions, hosts and scheduled tasks. cross-checked

omnigent:ACC-05

Product CLI and REST API manage sessions, hosts and scheduled tasks.

  • Not established by this source pass: sdk, mcp_server, webhooks, stability.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  3. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

  4. Omnigent Scheduled tasks

    Finding: Recurring scheduled agent sessions use persistent task definitions, a server scheduler and a REST API. Minimum interval is ten minutes on connected hosts or continued sessions and one hour for new sandbox sessions. Overlapping fires of a task are skipped; no automatic retry or missed-fire replay.

  5. Omnigent Policy reference

    Finding: Declarative policies allow/deny/ask actions; max tool calls, cost caps and thresholds. OS sandbox uses Linux bwrap/macOS seatbelt; plain sessions are not sandboxed by default. Generic agent-start DENY/ASK does not block launch.

omnigent:ACC-06: YAML agents use MCP/local functions/skills; owner controls live agent configuration.

omnigent:ACC-06

YAML agents use MCP/local functions/skills; owner controls live agent configuration.

  • Not established by this source pass: plugins.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  2. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:ACC-07: Native shells connect to server-served UI; desktop includes Electron browser.

omnigent:ACC-07

Native shells connect to server-served UI; desktop includes Electron browser.

  • Not established by this source pass: implementation_evidence.
  • Android client implementation is not described in the checked docs.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

omnigent:PLAN-01: New-chat prompt creates a persistent session; external links may prefill drafts. cross-checked

omnigent:PLAN-01

New-chat prompt creates a persistent session; external links may prefill drafts.

  • Not established by this source pass: local_creation, external_import, authoritative_tracker, sync, supported_edits, external_roundtrips.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:PLAN-02: Polly decomposes tasks; native Plan mode and persistent sessions retain planning context.

omnigent:PLAN-02

Polly decomposes tasks; native Plan mode and persistent sessions retain planning context.

  • Not established by this source pass: acceptance_criteria, editors, revisions, amendment.
  • No documented persistent link from a Polly plan to resulting PRs.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

omnigent:PLAN-03: Polly parent-child orchestration decomposes one task into parallel subtasks.

omnigent:PLAN-03

Polly parent-child orchestration decomposes one task into parallel subtasks.

  • Not established by this source pass: epics, readiness, enforcement, state_propagation, task_to_epic, identity_retention, workflow_constraints.
  1. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

omnigent:PLAN-04: Server stores skills/bundles/history and YAML defines shared tools/context.

omnigent:PLAN-04

Server stores skills/bundles/history and YAML defines shared tools/context.

  • Not established by this source pass: project_docs, provenance, correction, deletion, freshness.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:PLAN-05: Custom MCP tools and browser inspection supply external knowledge.

omnigent:PLAN-05

Custom MCP tools and browser inspection supply external knowledge.

  • Not established by this source pass: code_search, indexing, freshness, citations, conflict_detection, review_enforcement.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  3. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:PLAN-06: The scoped native UI and database have agent sessions, project grouping and scheduled automation definitions. Bounded inspection found no independent native issue/backlog/to-do work-item list; scheduled trigger definitions and run statuses are separate.

omnigent:PLAN-06

The scoped native UI and database have agent sessions, project grouping and scheduled automation definitions. Bounded inspection found no independent native issue/backlog/to-do work-item list; scheduled trigger definitions and run statuses are separate.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent native work and schedule records

    Finding: The scoped /tasks interface persists scheduled trigger definitions and run history; ordinary agent work is stored as sessions grouped into projects. Inspection of native stores, routes and Tasks UI found no independent backlog/to-do/issue work-item CRUD with open/in-progress/done states. Scheduled job state is not issue state.

omnigent:COORD-01: Polly runs several coding agents in parallel. cross-checked

omnigent:COORD-01

Polly runs several coding agents in parallel.

  • Not established by this source pass: quotas, observed_concurrency.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

omnigent:COORD-02: Polly routes implementation and review work to child agents.

omnigent:COORD-02

Polly routes implementation and review work to child agents.

  • Not established by this source pass: human_assignment, claims, queues, duplicate_prevention, ownership_enforcement.
  1. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

omnigent:COORD-03: Shipped Polly orchestrator delegates inspectable mixed-harness children. cross-checked

omnigent:COORD-03

Shipped Polly orchestrator delegates inspectable mixed-harness children.

  • Not established by this source pass: activation, authentication, followup.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

  3. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:COORD-04: Persistent recurring automations launch agent sessions from server.

omnigent:COORD-04

Persistent recurring automations launch agent sessions from server.

  • Not established by this source pass: events, completion_conditions, retries, client_independence.
  1. Omnigent Scheduled tasks

    Finding: Recurring scheduled agent sessions use persistent task definitions, a server scheduler and a REST API. Minimum interval is ten minutes on connected hosts or continued sessions and one hour for new sandbox sessions. Overlapping fires of a task are skipped; no automatic retry or missed-fire replay.

omnigent:COORD-05: Shared prompt/approval control and notifications are available across clients.

omnigent:COORD-05

Shared prompt/approval control and notifications are available across clients.

  • Not established by this source pass: pause, stop, resume, escalation, visible_errors, chat_terminal_parity.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Mobile

    Finding: Native iOS/Android shells and full mobile web UI connect to reachable server. iOS notifications foreground-only; org-preset server URLs available on Android but still future on iOS.

  3. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  4. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

omnigent:COORD-06: Agents panel, project session grouping and attention badges expose running work.

omnigent:COORD-06

Agents panel, project session grouping and attention badges expose running work.

  • Not established by this source pass: fleet_fixture, dependencies, navigation_errors, fixture_mode.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  3. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

omnigent:COORD-07: Single agents, Polly presets and custom YAML define workflows.

omnigent:COORD-07

Single agents, Polly presets and custom YAML define workflows.

  • Not established by this source pass: growing_epic, retained_relationships, discoverability, auth_friction.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

  3. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

omnigent:RUN-01: Separate server and hosts enable local or user-controlled remote execution. Managed sandbox launchers are configured on the user-operated server using its own provider credentials; no product-vendor runtime service is provisioned by this release.

omnigent:RUN-01

Separate server and hosts enable local or user-controlled remote execution. Managed sandbox launchers are configured on the user-operated server using its own provider credentials; no product-vendor runtime service is provisioned by this release.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  3. Omnigent managed host providers

    Finding: The scoped server registers the microsandbox provider and constructs its launcher from the server configuration. Runtime providers and credentials belong to the user-operated server, rather than an Omnigent-hosted execution service.

omnigent:RUN-02: Git worktrees, remote sandbox containers and optional OS policies are separate isolation mechanisms. The optional microsandbox provider additionally gives each host a hardware-isolated microVM on supported macOS/Linux hosts.

omnigent:RUN-02

Git worktrees, remote sandbox containers and optional OS policies are separate isolation mechanisms. The optional microsandbox provider additionally gives each host a hardware-isolated microVM on supported macOS/Linux hosts.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  2. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

  3. Omnigent Policy reference

    Finding: Declarative policies allow/deny/ask actions; max tool calls, cost caps and thresholds. OS sandbox uses Linux bwrap/macOS seatbelt; plain sessions are not sandboxed by default. Generic agent-start DENY/ASK does not block launch.

  4. Omnigent microsandbox deployment

    Finding: The optional microsandbox provider boots each Omnigent host in its own hardware-isolated microVM using libkrun. It is fully local/self-hosted, supports Apple Silicon macOS and Linux with KVM, and uses a beta pinned runtime. Server-managed sessions and CLI sandbox create are documented.

  5. Omnigent managed host providers

    Finding: The scoped server registers the microsandbox provider and constructs its launcher from the server configuration. Runtime providers and credentials belong to the user-operated server, rather than an Omnigent-hosted execution service.

omnigent:RUN-03: Server persists sessions through restarts; forks copy history with independent compute binding. cross-checked

omnigent:RUN-03

Server persists sessions through restarts; forks copy history with independent compute binding.

  • Not established by this source pass: client_disconnect, worker_crash, expiry, process_reconnect, state_reconstruction, duplicate_actions, manual_repair, multi_day_continuity.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  3. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

omnigent:RUN-04: Cloud sandbox configuration and remote SSH host setup are documented.

omnigent:RUN-04

Cloud sandbox configuration and remote SSH host setup are documented.

  • Not established by this source pass: dependencies, caches, snapshots, ports, duplicate_installs, collisions, automatic_repair.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

omnigent:RUN-05: Configurable policies cap tool calls and spend with approvals.

omnigent:RUN-05

Configurable policies cap tool calls and spend with approvals.

  • Not established by this source pass: time_limits, token_limits, timeouts, retries, provider_failures.
  • cost_budget is a downgrade gate at its limit, not a hard spend stop.
  1. Omnigent Policy reference

    Finding: Declarative policies allow/deny/ask actions; max tool calls, cost caps and thresholds. OS sandbox uses Linux bwrap/macOS seatbelt; plain sessions are not sandboxed by default. Generic agent-start DENY/ASK does not block launch.

omnigent:RUN-06: Session state, output and incomplete Git data are visible.

omnigent:RUN-06

Session state, output and incomplete Git data are visible.

  • Not established by this source pass: traces, failure_reasons, usage_export, task_stats, agent_stats, project_stats, time_stats, performance_method, responsiveness.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  3. Omnigent Pull request workflow

    Finding: Session PR associations persist server-side; description, checks, comments, changed files and diffs stay on and are served by the host provider integration. Incomplete data is flagged; linked request summaries remain when host offline; head/base revisions are validated before diffs are returned.

omnigent:RUN-07: Spend policies use USD caps; broader billing reconciliation remains unestablished.

omnigent:RUN-07

Spend policies use USD caps; broader billing reconciliation remains unestablished.

  • Not established by this source pass: task_cost, child_cost, epic_cost, harness_aggregation, billed_vs_estimated, subscription_allowance, provider_reconciliation, compute_cost, refresh_delay, export, drilldown.
  1. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

  2. Omnigent Policy reference

    Finding: Declarative policies allow/deny/ask actions; max tool calls, cost caps and thresholds. OS sandbox uses Linux bwrap/macOS seatbelt; plain sessions are not sandboxed by default. Generic agent-start DENY/ASK does not block launch.

omnigent:TEAM-01: Edit collaborators co-prompt the same live session. cross-checked

omnigent:TEAM-01

Edit collaborators co-prompt the same live session.

  • Not established by this source pass: discussion, comments, presence, ordering, plan_restrictions, owner_online.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

omnigent:TEAM-02: Admin/user management, OIDC SSO and Read/Edit/Owner boundaries are documented. cross-checked

omnigent:TEAM-02

Admin/user management, OIDC SSO and Read/Edit/Owner boundaries are documented.

  • Not established by this source pass: project_roles, provisioning, plan_scope.
  1. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  2. Omnigent Auth and SSO

    Finding: Invite-only built-in accounts or OIDC/header SSO. Admin manages membership/policies/sharing; owner/Edit/Read permissions scope sessions. First admin setup must be completed by operator.

omnigent:TEAM-03: Policy/harness gates ask or deny tools; owner controls permission mode. cross-checked

omnigent:TEAM-03

Policy/harness gates ask or deny tools; owner controls permission mode.

  • Not established by this source pass: network, secret, delivery, lifetime, revoke, tunnels, defaults.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  3. Omnigent Policy reference

    Finding: Declarative policies allow/deny/ask actions; max tool calls, cost caps and thresholds. OS sandbox uses Linux bwrap/macOS seatbelt; plain sessions are not sandboxed by default. Generic agent-start DENY/ASK does not block launch.

omnigent:TEAM-04: Committed session events and authorship persist and export. cross-checked

omnigent:TEAM-04

Committed session events and authorship persist and export.

  • Not established by this source pass: approvals, edits, decisions, retention, integrity.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

  3. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

omnigent:TEAM-05: Changes and PR UI support diff review and inline GitHub conversations. cross-checked

omnigent:TEAM-05

Changes and PR UI support diff review and inline GitHub conversations.

  • Not established by this source pass: pending_reviews, shipping_guidance, effort, missed_evidence, keyboard, narrow_screen, context_switching, roles, retained_context.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pull request workflow

    Finding: Session PR associations persist server-side; description, checks, comments, changed files and diffs stay on and are served by the host provider integration. Incomplete data is flagged; linked request summaries remain when host offline; head/base revisions are validated before diffs are returned.

omnigent:TEAM-06: Teammates co-drive a shared session or fork full history independently.

omnigent:TEAM-06

Teammates co-drive a shared session or fork full history independently.

  • Not established by this source pass: decisions, artifacts, runtime_context, owner_disconnect, ownership, attribution, context_loss.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pair programming

    Finding: Read/Edit session shares; Edit teammates send prompts and answer approvals. Only owner changes agent/MCP/permission mode; raw shell owner/admin only. Fork copies history independently.

omnigent:SHIP-01: Files, diffs, conversation and browser screenshots are accessible.

omnigent:SHIP-01

Files, diffs, conversation and browser screenshots are accessible.

  • Not established by this source pass: recordings, test_outputs, reviewer_outputs, gallery, revision_links, child_findings, prompt_leakage.
  1. Omnigent Desktop app

    Finding: macOS/Linux/Windows desktop shells serve full UI. Native notifications, dock badge and embedded browser. On macOS and Linux (not Windows), SSH connection starts a remote background host, then disconnects SSH; host keeps outbound server connection.

  2. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  3. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

omnigent:SHIP-02: Polly routes worker changes to a different-vendor reviewer; policy gates are separately configured.

omnigent:SHIP-02

Polly routes worker changes to a different-vendor reviewer; policy gates are separately configured.

  • Not established by this source pass: tests, lint, types, ci, spec_checks, required_checks, failure_blocking, requirement_conflicts.
  1. Omnigent Polly tutorial

    Finding: Shipped Polly orchestrator breaks a task into sub-tasks delegated to different agents (Claude Code and Codex in the example) in parallel Git worktrees, with cross-vendor review of each PR. Agents panel shows live sub-agent status, conversations, files and terminals.

  2. Omnigent Policy reference

    Finding: Declarative policies allow/deny/ask actions; max tool calls, cost caps and thresholds. OS sandbox uses Linux bwrap/macOS seatbelt; plain sessions are not sandboxed by default. Generic agent-start DENY/ASK does not block launch.

omnigent:SHIP-03: GitHub PR association, review and merge controls are documented. cross-checked

omnigent:SHIP-03

GitHub PR association, review and merge controls are documented.

  • Not established by this source pass: commits, ci_response, rebase, conflicts.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pull request workflow

    Finding: Session PR associations persist server-side; description, checks, comments, changed files and diffs stay on and are served by the host provider integration. Incomplete data is flagged; linked request summaries remain when host offline; head/base revisions are validated before diffs are returned.

omnigent:SHIP-04: Product PR panel has merge controls; deployment authority remains unknown.

omnigent:SHIP-04

Product PR panel has merge controls; deployment authority remains unknown.

  • Not established by this source pass: approve, release, deploy, authority_enforcement.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pull request workflow

    Finding: Session PR associations persist server-side; description, checks, comments, changed files and diffs stay on and are served by the host provider integration. Incomplete data is flagged; linked request summaries remain when host offline; head/base revisions are validated before diffs are returned.

omnigent:SHIP-05: Server retains session PR associations even with execution host offline.

omnigent:SHIP-05

Server retains session PR associations even with execution host offline.

  • Not established by this source pass: commit_links, build_links, deployment_links, rollback, revert, stale_approval_invalidation.
  1. Omnigent Pull request workflow

    Finding: Session PR associations persist server-side; description, checks, comments, changed files and diffs stay on and are served by the host provider integration. Incomplete data is flagged; linked request summaries remain when host offline; head/base revisions are validated before diffs are returned.

omnigent:SHIP-06: Compact PR list exposes checks/merge state and inline review discussion.

omnigent:SHIP-06

Compact PR list exposes checks/merge state and inline review discussion.

  • Not established by this source pass: grouping, risk_size_filters, artifacts, request_changes, exact_revision_approval, dependency_queues, stale_approval_invalidation, check_deduplication.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Pull request workflow

    Finding: Session PR associations persist server-side; description, checks, comments, changed files and diffs stay on and are served by the host provider integration. Incomplete data is flagged; linked request summaries remain when host offline; head/base revisions are validated before diffs are returned.

omnigent:OWN-01: Omnigent application repository is Apache-2.0. cross-checked

omnigent:OWN-01

Omnigent application repository is Apache-2.0.

  • Not established by this source pass: hosted_extensions, hosted_parity.
  1. Omnigent Application license

    Finding: Application repository is Apache-2.0.

omnigent:OWN-02: Full server/host is self-hostable and sessions export/import JSONL. cross-checked

omnigent:OWN-02

Full server/host is self-hostable and sessions export/import JSONL.

  • Not established by this source pass: vendor_dependencies, cancellation, account_independence.
  1. Omnigent Web UI

    Finding: Sessions persist across server restarts; projects group sessions; worktree launch options, diffs/files/inline comments and JSONL session export/import exist. Projects are grouping, not a native issue tracker.

  2. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

omnigent:OWN-03: Anonymous telemetry defaults on and has explicit opt-outs; session storage belongs to own server. cross-checked

omnigent:OWN-03

Anonymous telemetry defaults on and has explicit opt-outs; session storage belongs to own server.

  • Not established by this source pass: artifacts, retention, deletion, training, residency, subprocessors, consent_prompt, provider_separation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Usage telemetry

    Finding: Anonymous server usage telemetry defaults on; opt out with OMNIGENT_ANALYTICS=0, DO_NOT_TRACK=1 or telemetry:false. Prompts/files/credentials excluded according to vendor.

omnigent:OWN-04: Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider. cross-checked

omnigent:OWN-04

Omnigent is Apache-2.0 open source with no paid plan or price published; you bring your own vendor API key or Claude/ChatGPT subscription, billed by that provider.

  • First-party pricing pages, terms and licences read 2026-11-10; no purchase, billing or authenticated account test.
  1. Omnigent README

    Finding: Says Omnigent works with any model, using a first-party vendor API key or an existing Claude Pro/Max or ChatGPT subscription. It also offers cost-budget policies.

  2. Omnigent homepage

    Finding: Says Omnigent is open source under Apache 2.0. The page shows no price, plan or pricing page.

  3. omnigent-ai/omnigent LICENSE (Apache-2.0)

    Finding: The Apache License 2.0 grants a perpetual, worldwide, no-charge, royalty-free copyright license to use and reproduce the code.

omnigent:OWN-06: v0.21.0 is released; public docs and issue support exist.

omnigent:OWN-06

v0.21.0 is released; public docs and issue support exist.

  • Not established by this source pass: access_restrictions, response_commitments, status_history, deprecation, export_options.
  1. Omnigent Omnigent README

    Finding: Claude Pro/Max and ChatGPT subscriptions via official CLIs, API keys and compatible gateways. YAML agents include MCP/local function/subagent tools. Policy stacks at session/agent/server scope; caps and approval gates.

  2. Omnigent v0.21.0 release

    Finding: 2026-11-05 release adds PR list/checks/merge UI, inline GitHub review conversations and SSH host connection.

omnigent:OWN-08: Apache application is freely installable/self-hostable; providers and infrastructure cost separately. cross-checked

omnigent:OWN-08

Apache application is freely installable/self-hostable; providers and infrastructure cost separately.

  • Not established by this source pass: trial, credits_trial, paid_only, early_access, card_required, usage_caps, paid_evaluation.
  1. Omnigent Shared server

    Finding: Self-hosted server persists sessions/artifacts/catalog in SQLite/Postgres; separate local/remote hosts execute agents. Cloud sandbox providers allow laptop-independent work.

  2. Omnigent Application license

    Finding: Application repository is Apache-2.0.