46 of 51 criteria have a sourced finding; 41 were also cross-checked by a second agent. Every comparison that includes Omnara links here for scope, limitations, atomic answers and sources.
Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.
Client access: The scoped current frontend distribution ships a web dashboard, CLI and SDK, with no native iOS/Android app. Dashboard launches and inspects agents. The web agent sidebar and conversation navigation adapt to mobile viewports. omnara CLI launches, lists, waits and cancels. Configure/launch agents, send inputs, stop and archive through dashboard/CLI. Questions and approvals can be routed to Slack or Discord threads, and event webhooks push selected agent events to your URL; no native push, email or browser notifications are documented or found in the web frontend. Not established: desktop os, editor extensions, cross device continuity.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: desktop_os, editor_extensions, cross_device_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
9 atomic answers
Desktop os [unknown] Desktop os: no explicit product-scoped answer found in the checked first-party material.
Mobile apps [unsupported] The scoped current frontend distribution ships a web dashboard, CLI and SDK, with no native iOS/Android app. Sources: omnara:gap39-client-source.
Notifications [partial] Questions and approvals can be routed to Slack or Discord threads, and event webhooks push selected agent events to your URL; no native push, email or browser notifications are documented or found in the web frontend. Sources: omnara:b10-interactions, omnara:b10-webhooks, omnara:b10-code-frontend.
Cross device continuity [unknown] Cross device continuity: no explicit product-scoped answer found in the checked first-party material.
Omnara uses its own model/tool agent loop with configurable model providers. The scoped kernel has no coding-CLI session adapters for the nine compared external harnesses. Omnara runs its own agent loop on workers; each agent is a durable API object whose event log in Postgres is its state.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
5 atomic answers
Harnesses [unsupported] The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration. Sources: omnara:gap39-loop.
Session integration [supported] Omnara runs its own agent loop on workers; each agent is a durable API object whose event log in Postgres is its state. Sources: omnara:b10-concepts, omnara:b10-failure, omnara:b10-readme.
Bring API credentials or use managed model credits; native agent subscription reuse is not documented. The scoped provider implementation has API credentials, not a native coding-agent subscription login adapter. Omnara Cloud needs an Omnara sign-in; a self-hosted instance needs only an account on that instance, with your own model provider and machines.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: account_switching. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
7 atomic answers
Agent subscriptions [unsupported] Provider configuration and the execution kernel use model API credentials; native agent-subscription OAuth/session reuse is not implemented in the scoped adapter set. Sources: omnara:gap39-loop.
Account switching [unknown] Account switching: no explicit product-scoped answer found in the checked first-party material.
Vendor account requirement [supported] Omnara Cloud needs an Omnara sign-in; a self-hosted instance needs only an account on that instance, with your own model provider and machines. Sources: omnara:b10-readme.
Create agent config and grants, then use dashboard/API/CLI; own machine and full self-host recipes exist. A user-owned GitHub App (guided setup for GitHub.com) supplies PR tools and HTTPS Git/gh credentials on github.com; other Git hosts are not documented.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: no_git, local_git_without_remote, hosted_git.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: no_git, local_git_without_remote. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
No git [unknown] No git: no explicit product-scoped answer found in the checked first-party material.
Local git without remote [unknown] Local git without remote: no explicit product-scoped answer found in the checked first-party material.
Hosted git [partial] A user-owned GitHub App (guided setup for GitHub.com) supplies PR tools and HTTPS Git/gh credentials on github.com; other Git hosts are not documented. Sources: omnara:b10-github.
Product CLI, REST API, TypeScript SDK and event webhooks operate durable agents. The API is exposed as an OAuth-protected MCP server at app.omnara.com/mcp; the API server code mounts the same /mcp handler for self-hosted deployments.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: mcp_server, stability.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: stability. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Mcp server [supported] The API is exposed as an OAuth-protected MCP server at app.omnara.com/mcp; the API server code mounts the same /mcp handler for self-hosted deployments. Sources: omnara:b10-auth, omnara:b10-code-mcp.
Client implementation: Pinned source 313ac70: frontend/apps/web is a React and Vite single-page app served by the web process; no native or Electron client exists. Bounded inspection of the repository (package manifests, frontend/apps, web manifest and service-worker search) found no desktop, mobile, hybrid or PWA client.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Omnara ships no desktop or mobile client at 313ac70: access is the web app, CLI and SDK only.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
4 atomic answers
Desktop implementation [unsupported] No desktop client: bounded inspection of 313ac70 found only the web app under frontend/apps and no Electron, Tauri, Wails or other desktop packaging in any package.json or go.mod; the organization's other public repositories contain no client app. Sources: omnara:c165-code-clients.
Mobile implementation [unsupported] No native or hybrid mobile app: no React Native, Expo or Capacitor project exists at 313ac70; phones use the same React web app, which adapts its sidebar to mobile viewports. Sources: omnara:c165-code-clients.
Hybrids [unsupported] No hybrid packaging: no webview wrapper, web app manifest or service worker exists at 313ac70, so the web app is not packaged as a PWA or desktop/mobile shell. Sources: omnara:c165-code-clients.
Implementation evidence [supported] Pinned source 313ac70: frontend/apps/web is a React and Vite single-page app served by the web process; no native or Electron client exists. Sources: omnara:b10-code-frontend, omnara:b10-architecture.
Agent conversations accept dashboard/API prompts and integration subscriptions. Agents launch from the dashboard, the omnara CLI, the REST API or the TypeScript SDK.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: local_creation, external_import, authoritative_tracker, sync, supported_edits, external_roundtrips.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: external_import, authoritative_tracker, sync, supported_edits, external_roundtrips. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
9 atomic answers
Local creation [supported] Agents launch from the dashboard, the omnara CLI, the REST API or the TypeScript SDK. Sources: omnara:b10-readme.
Durable task plans: There is no task-plan object; agent configs are immutable and profile updates keep a version history, which versions agent instructions rather than a task plan. A running agent takes steering messages at its next model call, and its config (model, tools, permissions, instructions) can be swapped through the API without restarting the conversation. Every step is saved to Postgres, so agents resume from the last saved step after worker crashes, deploys and restarts. Not established: plans, acceptance criteria, editors, implementation links.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: plans, acceptance_criteria, editors, implementation_links. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
7 atomic answers
Plans [unknown] Plans: no explicit product-scoped answer found in the checked first-party material.
Acceptance criteria [unknown] Acceptance criteria: no explicit product-scoped answer found in the checked first-party material.
Editors [unknown] Editors: no explicit product-scoped answer found in the checked first-party material.
Revisions [partial] There is no task-plan object; agent configs are immutable and profile updates keep a version history, which versions agent instructions rather than a task plan. Sources: omnara:b10-config.
Implementation links [unknown] Implementation links: no explicit product-scoped answer found in the checked first-party material.
Amendment [supported] A running agent takes steering messages at its next model call, and its config (model, tools, permissions, instructions) can be swapped through the API without restarting the conversation. Sources: omnara:b10-input.
Restart persistence [supported] Every step is saved to Postgres, so agents resume from the last saved step after worker crashes, deploys and restarts. Sources: omnara:b10-failure.
Hierarchy, dependencies and evolving scope: Agents can spawn subagents that nest up to max_depth (default 1, at most 8); this is an agent hierarchy, not an epic or task hierarchy. Not established: epics, blockers, readiness, enforcement, state propagation, task to epic, identity retention, workflow constraints.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: epics, blockers, readiness, enforcement, state_propagation, task_to_epic, identity_retention, workflow_constraints. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
9 atomic answers
Epics [unknown] Epics: no explicit product-scoped answer found in the checked first-party material.
Hierarchy [partial] Agents can spawn subagents that nest up to max_depth (default 1, at most 8); this is an agent hierarchy, not an epic or task hierarchy. Sources: omnara:b10-config.
Blockers [unknown] Blockers: no explicit product-scoped answer found in the checked first-party material.
Readiness [unknown] Readiness: no explicit product-scoped answer found in the checked first-party material.
Enforcement [unknown] Enforcement: no explicit product-scoped answer found in the checked first-party material.
State propagation [unknown] State propagation: no explicit product-scoped answer found in the checked first-party material.
Task to epic [unknown] Task to epic: no explicit product-scoped answer found in the checked first-party material.
Identity retention [unknown] Identity retention: no explicit product-scoped answer found in the checked first-party material.
Workflow constraints [unknown] Workflow constraints: no explicit product-scoped answer found in the checked first-party material.
External tools and versioned knowledge packages supply agent context. Inputs accept images, PDFs, text files, spreadsheets and Office documents, stored as artifacts.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: code_search, indexing, multimodal_inputs, citations, conflict_detection, review_enforcement.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: code_search, indexing, citations, conflict_detection, review_enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Code search [unknown] Code search: no explicit product-scoped answer found in the checked first-party material.
Indexing [unknown] Indexing: no explicit product-scoped answer found in the checked first-party material.
The scoped native database and API manage durable agent conversations and trigger configurations. Bounded inspection of persisted models, HTTP routes and web pages found no independent native issue/backlog work-item store.
Scope
Surfaces: api, cloud, self-hosted · Version: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
17 atomic answers
Create [unsupported] There is no product-owned issue/backlog CRUD in the inspected native routes and stores. Sources: omnara:gap39-agent-store.
Edit [unknown] Edit: no explicit product-scoped answer found in the checked first-party material.
Discuss [unknown] Discuss: no explicit product-scoped answer found in the checked first-party material.
Prioritize [unknown] Prioritize: no explicit product-scoped answer found in the checked first-party material.
Label [unknown] Label: no explicit product-scoped answer found in the checked first-party material.
Assign [unknown] Assign: no explicit product-scoped answer found in the checked first-party material.
Search [unknown] Search: no explicit product-scoped answer found in the checked first-party material.
Filter [unknown] Filter: no explicit product-scoped answer found in the checked first-party material.
Archive [unknown] Archive: no explicit product-scoped answer found in the checked first-party material.
Reopen [unknown] Reopen: no explicit product-scoped answer found in the checked first-party material.
Project epic views [unknown] Project epic views: no explicit product-scoped answer found in the checked first-party material.
Idea parking [unknown] Idea parking: no explicit product-scoped answer found in the checked first-party material.
Explicit dispatch [unknown] Explicit dispatch: no explicit product-scoped answer found in the checked first-party material.
Task session separation [unsupported] Agent conversations are the work records; schedules are trigger configurations, not a separate issue/task backlog. Sources: omnara:gap39-agent-store.
Metadata [unknown] Metadata: no explicit product-scoped answer found in the checked first-party material.
Durable states [unknown] Durable states: no explicit product-scoped answer found in the checked first-party material.
External tracker requirement [unknown] External tracker requirement: no explicit product-scoped answer found in the checked first-party material.
Agent-native issue operations: An agent creates child agents with spawn_agent and reads, messages, stops and lists them; these are agent children, not issue records. Not established: shared ids, read, create, update, claim, assign, state changes, dependencies, results, human visibility, attribution, permissions, conflicts.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: shared_ids, read, create, update, claim, assign, state_changes, dependencies, results, human_visibility, attribution, permissions, conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
14 atomic answers
Shared ids [unknown] Shared ids: no explicit product-scoped answer found in the checked first-party material.
Read [unknown] Read: no explicit product-scoped answer found in the checked first-party material.
Create [unknown] Create: no explicit product-scoped answer found in the checked first-party material.
Update [unknown] Update: no explicit product-scoped answer found in the checked first-party material.
Claim [unknown] Claim: no explicit product-scoped answer found in the checked first-party material.
Assign [unknown] Assign: no explicit product-scoped answer found in the checked first-party material.
State changes [unknown] State changes: no explicit product-scoped answer found in the checked first-party material.
Dependencies [unknown] Dependencies: no explicit product-scoped answer found in the checked first-party material.
Children [partial] An agent creates child agents with spawn_agent and reads, messages, stops and lists them; these are agent children, not issue records. Sources: omnara:b10-config.
Results [unknown] Results: no explicit product-scoped answer found in the checked first-party material.
Human visibility [unknown] Human visibility: no explicit product-scoped answer found in the checked first-party material.
Attribution [unknown] Attribution: no explicit product-scoped answer found in the checked first-party material.
Permissions [unknown] Permissions: no explicit product-scoped answer found in the checked first-party material.
Conflicts [unknown] Conflicts: no explicit product-scoped answer found in the checked first-party material.
Product dispatches subagents and leases execution steps to workers. No human or agent work-claim feature is documented; internally each worker holds a renewable lease on one agent so only one worker runs its next step.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: human_assignment, claims, queues.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: human_assignment, queues. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
7 atomic answers
Human assignment [unknown] Human assignment: no explicit product-scoped answer found in the checked first-party material.
Claims [partial] No human or agent work-claim feature is documented; internally each worker holds a renewable lease on one agent so only one worker runs its next step. Sources: omnara:b10-failure.
Queues [unknown] Queues: no explicit product-scoped answer found in the checked first-party material.
Omnara control-plane cron schedules (cron plus timezone) and provider events (Slack, Discord, GitHub) start agents without an open client; each occurrence launches a fresh agent thread. Overlap handling is not documented.
Scope
Surfaces: api, cloud, self-hosted · Version: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-10
Not established by this source pass: overlaps. Automatic retry of a skipped occurrence is not documented. Not tested.
Recurring tasks [supported] Integration schedules use cron plus timezone and launch a fresh agent in a new thread for each occurrence. Sources: omnara:src2-om-schedules.
Scheduler location [supported] Schedules are Omnara cron triggers configured on an integration in the dashboard or via the cron-triggers API, so the Omnara control plane fires them. Sources: omnara:src2-om-schedules.
Overlaps [unknown] Overlaps: no explicit product-scoped answer found in the checked first-party material.
Retries [partial] A disconnected integration skips an occurrence with a visible failure and later occurrences run after reconnection; automatic retry of a skipped occurrence is not documented. Sources: omnara:src2-om-schedules.
Client independence [supported] Scheduled and provider-event launches (Slack/Discord mentions, GitHub PR open or mention) start agents from the control plane without an open client. Sources: omnara:src2-om-schedules, omnara:src2-om-gh-launch.
Queued/steering inputs, stop and permission interactions control work. Pending questions and approvals can be delivered to Slack or Discord and appear in webhook events; the dashboard remains the fallback. No native push or email alerts are documented.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: pause, notifications, escalation, chat_terminal_parity.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: pause, escalation, chat_terminal_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Pause [unknown] Pause: no explicit product-scoped answer found in the checked first-party material.
Notifications [partial] Pending questions and approvals can be delivered to Slack or Discord and appear in webhook events; the dashboard remains the fallback. No native push or email alerts are documented. Sources: omnara:b10-interactions, omnara:b10-webhooks.
Escalation [unknown] Escalation: no explicit product-scoped answer found in the checked first-party material.
Visible errors [supported] Failed model turns end with the error in agent history; an offline machine returns a retryable machine_unreachable result. Sources: omnara:nov07-agents-failure-handling.
Chat terminal parity [unknown] Chat terminal parity: no explicit product-scoped answer found in the checked first-party material.
Control plane persists independently of user/BYO or managed execution machines. An agent can use several machines at once and move between them; if a laptop goes offline it can continue in a sandbox and sync work back with git. Pool machines are deleted on release, pool deletion or a configurable idle period (minimum 5 minutes, 0 disables); BYO machines are user-managed. History survives deletion.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: hybrid, resources, region, expiry.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: resources, region. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Hybrid [supported] An agent can use several machines at once and move between them; if a laptop goes offline it can continue in a sandbox and sync work back with git. Sources: omnara:b10-readme.
Resources [unknown] Resources: no explicit product-scoped answer found in the checked first-party material.
Region [unknown] Region: no explicit product-scoped answer found in the checked first-party material.
Expiry [supported] Pool machines are deleted on release, pool deletion or a configurable idle period (minimum 5 minutes, 0 disables); BYO machines are user-managed. History survives deletion. Sources: omnara:b10-machines, omnara:b10-pools.
Machine pools can use container sandbox providers (Daytona, Agent37, Modal) or microVM and full-VM providers. Subagents share the parent's attached machines; an official example instructs them to use separate Git worktrees. secret_env_overlay injects project-granted secrets into agent processes; OMNARA_ names are reserved and revoked secrets are omitted from later processes.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: checkout, branch, os_sandbox, filesystem, process, network, secrets, security_boundary.
Worktree separation in the official example is agent instruction text, not a documented platform isolation setting.
Container and VM isolation come from third-party sandbox providers chosen for the machine pool; not tested.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: checkout, branch, os_sandbox, filesystem, process, network, security_boundary. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
12 atomic answers
Checkout [unknown] Checkout: no explicit product-scoped answer found in the checked first-party material.
Branch [unknown] Branch: no explicit product-scoped answer found in the checked first-party material.
Container [supported] Machine pools can use container sandbox providers: Daytona (containers) and Agent37 and Modal (gVisor containers). Sources: omnara:src2-om-providers.
Vm [supported] Machine pools can use microVM providers (Blaxel default pool, E2B, boxd, CreateOS, Superserve, Unikraft) or full-VM providers (Arker, Freestyle, Tenki). Sources: omnara:src2-om-providers.
Os sandbox [unknown] Os sandbox: no explicit product-scoped answer found in the checked first-party material.
Filesystem [unknown] Filesystem: no explicit product-scoped answer found in the checked first-party material.
Process [unknown] Process: no explicit product-scoped answer found in the checked first-party material.
Network [unknown] Network: no explicit product-scoped answer found in the checked first-party material.
Secrets [supported] secret_env_overlay injects project-granted secrets into agent processes; OMNARA_ names are reserved and revoked secrets are omitted from later processes. Sources: omnara:b10-config.
Durable event state survives workers and machine loss with explicit unknown external outcomes. Commands keep running on the machine when a worker dies and the agent gets the result; when the machine goes offline the agent cannot reach the process until the daemon reconnects, and waiting calls return a retryable unreachable result after 30 seconds. The Postgres event log is the agent's state; any worker reconstructs and continues an agent from it without rerunning finished tools.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: transcript_reload, process_reconnect, state_reconstruction, context_loss, multi_day_continuity.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: transcript_reload, context_loss, multi_day_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Transcript reload [unknown] Transcript reload: no explicit product-scoped answer found in the checked first-party material.
Process reconnect [partial] Commands keep running on the machine when a worker dies and the agent gets the result; when the machine goes offline the agent cannot reach the process until the daemon reconnects, and waiting calls return a retryable unreachable result after 30 seconds. Sources: omnara:b10-failure, omnara:b10-machines.
State reconstruction [supported] The Postgres event log is the agent's state; any worker reconstructs and continues an agent from it without rerunning finished tools. Sources: omnara:b10-failure.
Context loss [unknown] Context loss: no explicit product-scoped answer found in the checked first-party material.
Managed pools include development tools; custom images/snapshots and startup scripts are configurable. Pool machines keep files, installed dependencies and running processes across turns, including suspend and resume; sharing caches between machines is not documented.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: caches, ports, duplicate_installs, collisions, automatic_repair.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: ports, duplicate_installs, collisions, automatic_repair. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Dependencies [supported] Managed Ubuntu with language/build/database/browser tools preinstalled. Sources: omnara:nov07-machines-pools.
Caches [partial] Pool machines keep files, installed dependencies and running processes across turns, including suspend and resume; sharing caches between machines is not documented. Sources: omnara:b10-pools.
Model retries/timeouts/context limits and subagent depth caps are explicit. Commands must be accepted within five minutes; offline machines are reported after 30 seconds; model calls retry up to eight times; deploys drain for 20 seconds; approvals wait indefinitely.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: turn_limits, spend_limits, timeouts.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: turn_limits, spend_limits. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Spend limits [unknown] Spend limits: no explicit product-scoped answer found in the checked first-party material.
Timeouts [supported] Commands must be accepted within five minutes; offline machines are reported after 30 seconds; model calls retry up to eight times; deploys drain for 20 seconds; approvals wait indefinitely. Sources: omnara:b10-failure.
Agent activity distinguishes waiting, background processes, idle and archived; history records errors. Each agent's timeline records inputs, model outputs with tool calls and tool results with outcomes, viewable in the dashboard and through the events API and stream. Usage endpoints return model calls, tokens and cost by model per agent (optionally with subagents), profile, project and organization, plus timeseries; self-hosted history is queryable in Postgres.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: traces, usage_export, task_stats, agent_stats, project_stats, time_stats, performance_method, responsiveness.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: task_stats, agent_stats, project_stats, time_stats, performance_method, responsiveness. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Traces [supported] Each agent's timeline records inputs, model outputs with tool calls and tool results with outcomes, viewable in the dashboard and through the events API and stream. Sources: omnara:b10-readme, omnara:b10-streaming.
Usage export [supported] Usage endpoints return model calls, tokens and cost by model per agent (optionally with subagents), profile, project and organization, plus timeseries; self-hosted history is queryable in Postgres. Sources: omnara:b10-code-openapi, omnara:b10-readme.
Task stats [unknown] Task stats: no explicit product-scoped answer found in the checked first-party material.
Agent stats [unknown] Agent stats: no explicit product-scoped answer found in the checked first-party material.
Project stats [unknown] Project stats: no explicit product-scoped answer found in the checked first-party material.
Time stats [unknown] Time stats: no explicit product-scoped answer found in the checked first-party material.
Per-task API and compute cost: Managed machines cost $0.0414 per GiB of memory per hour online plus $0.20016 per GiB per 30 days retained; idle machines sleep; BYO machines are free. Per-agent usage reports give provider-reported USD cost and input, cached and output tokens by model, optionally including subagents, with drill-down from organization to project, agent profile and agent; usage is retrievable as JSON through the API, but the web usage views have no file download. Not established: epic cost, harness aggregation, billed vs estimated, subscription allowance, provider reconciliation, refresh delay, alerts.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: epic_cost, harness_aggregation, billed_vs_estimated, subscription_allowance, provider_reconciliation, refresh_delay, alerts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
14 atomic answers
Task cost [supported] Each agent (one task conversation) has a usage report with provider-reported USD cost by configured model, from GET /orgs/{orgID}/projects/{projectID}/agents/{agentID}/usage and the agent sidebar usage panel. Sources: omnara:b10-code-openapi, omnara:c165-code-usage-web.
Session cost [supported] An Omnara agent is the conversation, so the per-agent usage report is the session cost; it can be limited to a time window with since/until. Sources: omnara:b10-code-openapi.
Child cost [partial] An agent's usage can include its subagents at every depth (include_subagents; the sidebar toggle is on by default). A separate per-child breakdown inside the parent report was not established. Sources: omnara:b10-code-openapi, omnara:c165-code-usage-web.
Epic cost [unknown] Epic cost: no explicit product-scoped answer found in the checked first-party material.
Harness aggregation [unknown] Harness aggregation: no explicit product-scoped answer found in the checked first-party material.
Billed vs estimated [unknown] Billed vs estimated: no explicit product-scoped answer found in the checked first-party material.
Tokens [supported] Usage reports give input tokens (uncached, cache-read, cache-write) and output tokens including reasoning tokens, in totals and per model. Sources: omnara:b10-code-openapi.
Subscription allowance [unknown] Subscription allowance: no explicit product-scoped answer found in the checked first-party material.
Provider reconciliation [unknown] Provider reconciliation: no explicit product-scoped answer found in the checked first-party material.
Compute cost [supported] Managed machines cost $0.0414 per GiB of memory per hour online plus $0.20016 per GiB per 30 days retained; idle machines sleep; BYO machines are free. Sources: omnara:b10-pricing.
Refresh delay [unknown] Refresh delay: no explicit product-scoped answer found in the checked first-party material.
Alerts [unknown] Alerts: no explicit product-scoped answer found in the checked first-party material.
Export [partial] Usage is retrievable as JSON through the usage and timeseries API endpoints; the web usage views offer no CSV or file download. Sources: omnara:b10-code-openapi, omnara:c165-code-usage-web.
Drilldown [supported] Usage drills from organization to project, agent profile and single agent, each with per-model rows; the organization timeseries can be grouped by model or profile. Sources: omnara:b10-code-openapi, omnara:c165-code-usage-web.
Authorized project operators can send input to the same durable agent. Agents run on Omnara workers and wait in Postgres for approvals, so the launching person need not stay online.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: discussion, comments, presence, conflicts, plan_restrictions, owner_online.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: discussion, comments, presence, conflicts, plan_restrictions. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Plan restrictions [unknown] Plan restrictions: no explicit product-scoped answer found in the checked first-party material.
Owner online [supported] Agents run on Omnara workers and wait in Postgres for approvals, so the launching person need not stay online. Sources: omnara:b10-readme, omnara:b10-failure.
Per-tool allow/ask/deny policy creates durable permission interactions. GitHub credentials are read-only unless 'Let agents push code' is enabled, can be limited to listed repositories, stay subject to GitHub rules and cannot change .github/workflows.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: command, network, secret, delivery, approver_identity, revoke, tunnels, safer_modes.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: command, network, secret, approver_identity, revoke, tunnels, safer_modes. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
14 atomic answers
Command [unknown] Command: no explicit product-scoped answer found in the checked first-party material.
Network [unknown] Network: no explicit product-scoped answer found in the checked first-party material.
Secret [unknown] Secret: no explicit product-scoped answer found in the checked first-party material.
Delivery [supported] GitHub credentials are read-only unless 'Let agents push code' is enabled, can be limited to listed repositories, stay subject to GitHub rules and cannot change .github/workflows. Sources: omnara:b10-github.
Approver identity [unknown] Approver identity: no explicit product-scoped answer found in the checked first-party material.
Durable event timeline records attributed inputs, config changes and tool outcomes. The public API exposes agent events and turns read-only, with no edit or delete operation, and archiving keeps history; self-hosted operators control their own Postgres, and no integrity model is documented.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: discussion, decisions, cross_user_persistence, cross_session_persistence, export, mutability, retention, integrity.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: discussion, decisions, cross_user_persistence, cross_session_persistence, export, retention, integrity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Discussion [unknown] Discussion: no explicit product-scoped answer found in the checked first-party material.
Decisions [unknown] Decisions: no explicit product-scoped answer found in the checked first-party material.
Cross user persistence [unknown] Cross user persistence: no explicit product-scoped answer found in the checked first-party material.
Cross session persistence [unknown] Cross session persistence: no explicit product-scoped answer found in the checked first-party material.
Export [unknown] Export: no explicit product-scoped answer found in the checked first-party material.
Mutability [partial] The public API exposes agent events and turns read-only, with no edit or delete operation, and archiving keeps history; self-hosted operators control their own Postgres, and no integrity model is documented. Sources: omnara:b10-code-openapi, omnara:b10-archive.
Retention [unknown] Retention: no explicit product-scoped answer found in the checked first-party material.
Integrity [unknown] Integrity: no explicit product-scoped answer found in the checked first-party material.
Review experience and guidance: On GitHub PRs agents post discussion and inline review comments, replies and reviews and resolve threads; human PR discussion and review comments steer the agent. Not established: pending reviews, change understanding, evidence navigation, request changes, shipping guidance, effort, missed evidence, keyboard, narrow screen, context switching, roles, retained context.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: pending_reviews, change_understanding, evidence_navigation, request_changes, shipping_guidance, effort, missed_evidence, keyboard, narrow_screen, context_switching, roles, retained_context. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
13 atomic answers
Pending reviews [unknown] Pending reviews: no explicit product-scoped answer found in the checked first-party material.
Change understanding [unknown] Change understanding: no explicit product-scoped answer found in the checked first-party material.
Evidence navigation [unknown] Evidence navigation: no explicit product-scoped answer found in the checked first-party material.
Comments [supported] On GitHub PRs agents post discussion and inline review comments, replies and reviews and resolve threads; human PR discussion and review comments steer the agent. Sources: omnara:b10-github.
Request changes [unknown] Request changes: no explicit product-scoped answer found in the checked first-party material.
Shipping guidance [unknown] Shipping guidance: no explicit product-scoped answer found in the checked first-party material.
Effort [unknown] Effort: no explicit product-scoped answer found in the checked first-party material.
Missed evidence [unknown] Missed evidence: no explicit product-scoped answer found in the checked first-party material.
Keyboard [unknown] Keyboard: no explicit product-scoped answer found in the checked first-party material.
Narrow screen [unknown] Narrow screen: no explicit product-scoped answer found in the checked first-party material.
Context switching [unknown] Context switching: no explicit product-scoped answer found in the checked first-party material.
Roles [unknown] Roles: no explicit product-scoped answer found in the checked first-party material.
Retained context [unknown] Retained context: no explicit product-scoped answer found in the checked first-party material.
Colleague takeover and continuity: Any project operator can send attributed inputs, resolve approvals and stop work on a running agent; formal ownership transfer is not documented. Every input is attributed to its authenticated caller or a named external actor, and another operator reads the agent's full saved event timeline. Not established: same task, decisions, artifacts, permissions, runtime context, owner disconnect, ownership, context loss, harness transfer.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: same_task, decisions, artifacts, permissions, runtime_context, owner_disconnect, ownership, context_loss, harness_transfer. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
12 atomic answers
Ongoing takeover [partial] Any project operator can send attributed inputs, resolve approvals and stop work on a running agent; formal ownership transfer is not documented. Sources: omnara:b10-members, omnara:b10-input.
Same task [unknown] Same task: no explicit product-scoped answer found in the checked first-party material.
Session history [supported] A second project operator reads the same agent's full ordered timeline (inputs, model outputs, tool results) through GET /events or the live stream, and reconnecting with Last-Event-ID catches up every saved event. Sources: omnara:b10-streaming, omnara:b10-members.
Decisions [unknown] Decisions: no explicit product-scoped answer found in the checked first-party material.
Artifacts [unknown] Artifacts: no explicit product-scoped answer found in the checked first-party material.
Permissions [unknown] Permissions: no explicit product-scoped answer found in the checked first-party material.
Runtime context [unknown] Runtime context: no explicit product-scoped answer found in the checked first-party material.
Owner disconnect [unknown] Owner disconnect: no explicit product-scoped answer found in the checked first-party material.
Ownership [unknown] Ownership: no explicit product-scoped answer found in the checked first-party material.
Attribution [supported] Every input is attributed to whoever authenticated the request; a relaying backend can name an external actor on inputs, interaction resolutions and stops. Sources: omnara:b10-input.
Context loss [unknown] Context loss: no explicit product-scoped answer found in the checked first-party material.
Harness transfer [unknown] Harness transfer: no explicit product-scoped answer found in the checked first-party material.
Durable artifacts attach immutable downloadable content to agent events. The scoped artifact/conversation UI does not include a code-diff review interface.
Scope
Surfaces: api, cloud, self-hosted · Version: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
Not separately cross-checked
Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
13 atomic answers
Diffs [unsupported] The inspected artifact cards and agent conversation components do not provide proposed-code diff review. Sources: omnara:gap39-review.
Revision links [unknown] Not established for revision links in the official sources checked on 2026-11-07: artifact digests bind file bytes, not a code revision; see context.roadmapReview for search and access gaps.
Through the GitHub App integration, an agent assigned to a pull request can read its diff, comments and reviews, post conversation and inline comments, submit COMMENT reviews, and push commits when 'Let agents push code' is enabled. Opening new pull requests, rebasing and conflict handling are not documented.
Scope
Surfaces: cloud, self-hosted · Version: cluster-v0.2.19 (docs at 89a8ec9) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-10 (12 days old)
Agent cross-check
2026-11-10
No installed-product test was run.
Docs read at release tag cluster-v0.2.19; GitHub integration docs changed on main after that tag.
PR tools submit COMMENT reviews only; they cannot approve or request changes.
9 atomic answers
Branches [unknown] Branches: no explicit product-scoped answer found in the checked first-party material.
Worktrees [unknown] Worktrees: no explicit product-scoped answer found in the checked first-party material.
Commits [partial] With push enabled on the integration, agents get write Git credentials and push with ordinary git commands; credentials default to read-only. Commit authoring itself is agent-driven, not a product workflow. Sources: omnara:src2-om-gh-git.
Pull requests [partial] Agents operate on one assigned PR (read, comment, review) and can be launched by PR-open or mention events. Creating a new PR is not documented. Sources: omnara:src2-om-gh-tools, omnara:src2-om-gh-launch.
Comments [supported] Agents post PR conversation comments, inline diff comments and replies, and receive forwarded PR comments and reviews. Sources: omnara:src2-om-gh-tools, omnara:src2-om-gh-launch.
Ci response [unknown] Ci response: no explicit product-scoped answer found in the checked first-party material.
Rebase [unknown] Rebase: no explicit product-scoped answer found in the checked first-party material.
Conflicts [unknown] Conflicts: no explicit product-scoped answer found in the checked first-party material.
Product state [unknown] Product state: no explicit product-scoped answer found in the checked first-party material.
Omnara describes the full platform as Apache-2.0 open source. Checked at omnara-ai/omnara 313ac70, the commit tagged omnarad-v0.2.27 and cluster-v0.2.27 (2026-11-20); Apache 2.0 LICENSE. The README says the API, CLI, SDK and config format are the same on Omnara Cloud and self-hosted, and self-hosted operators can provide default models and sandboxes as Cloud does; full hosted-service parity is not otherwise established.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: hosted_extensions. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Server license [supported] Self-host platform under Apache 2.0. Sources: omnara:nov07-intro.
Hosted extensions [unknown] Hosted extensions: no explicit product-scoped answer found in the checked first-party material.
Source visibility [supported] Public application repository. Sources: omnara:nov07-intro.
Source revision [supported] Checked at omnara-ai/omnara 313ac70, the commit tagged omnarad-v0.2.27 and cluster-v0.2.27 (2026-11-20); Apache 2.0 LICENSE. Sources: omnara:b10-license, omnara:b10-releases.
Hosted parity [partial] The README says the API, CLI, SDK and config format are the same on Omnara Cloud and self-hosted, and self-hosted operators can provide default models and sandboxes as Cloud does; full hosted-service parity is not otherwise established. Sources: omnara:b10-readme.
Full control plane can run on own database/storage/compute. The full platform self-hosts with Docker Compose and needs no Omnara account; the same CLI, SDK and API point at your own instance. Self-hosted history lives in your own Postgres; on Cloud, events, turns and artifacts are readable through the API. No bulk export or import format is documented.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: import, cancellation, account_independence, history_portability.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: import, cancellation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Cancellation [unknown] Cancellation: no explicit product-scoped answer found in the checked first-party material.
Account independence [supported] The full platform self-hosts with Docker Compose and needs no Omnara account; the same CLI, SDK and API point at your own instance. Sources: omnara:b10-readme.
History portability [partial] Self-hosted history lives in your own Postgres; on Cloud, events, turns and artifacts are readable through the API. No bulk export or import format is documented. Sources: omnara:b10-readme, omnara:b10-streaming.
Self-hosting controls data stores; machine deletion does not delete agent history/artifacts. Workers send model calls to the provider configured for the project (BYO OpenAI, Anthropic, OpenRouter, Bedrock, LiteLLM, Ollama or compatible endpoints, or Omnara-managed models on Cloud); separate vendor and provider data policies were not read in this pass.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: prompts, deletion, training, residency, subprocessors, telemetry_disclosure, telemetry_defaults, telemetry_controls, consent_prompt, provider_separation.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: prompts, deletion, training, residency, subprocessors, telemetry_disclosure, telemetry_defaults, telemetry_controls, consent_prompt. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
Deletion [unknown] Deletion: no explicit product-scoped answer found in the checked first-party material.
Training [unknown] Training: no explicit product-scoped answer found in the checked first-party material.
Residency [unknown] Residency: no explicit product-scoped answer found in the checked first-party material.
Subprocessors [unknown] Subprocessors: no explicit product-scoped answer found in the checked first-party material.
Telemetry disclosure [unknown] Telemetry disclosure: no explicit product-scoped answer found in the checked first-party material.
Telemetry defaults [unknown] Telemetry defaults: no explicit product-scoped answer found in the checked first-party material.
Telemetry controls [unknown] Telemetry controls: no explicit product-scoped answer found in the checked first-party material.
Consent prompt [unknown] Consent prompt: no explicit product-scoped answer found in the checked first-party material.
Provider separation [partial] Workers send model calls to the provider configured for the project (BYO OpenAI, Anthropic, OpenRouter, Bedrock, LiteLLM, Ollama or compatible endpoints, or Omnara-managed models on Cloud); separate vendor and provider data policies were not read in this pass. Sources: omnara:b10-readme, omnara:b10-pricing.
Platform has $0 fee; managed model/machine usage is separate. Managed-resource credits carry a 5% service fee. Enterprise deployment, integration and support services require contact, without a public monthly price.
Scope
Surfaces: api, cloud, self-hosted · Version: Omnara pricing retrieved 2026-11-12 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by these source passes: interval, seat_minimum, trial, taxes.
Included usage [supported] Bring own model keys/machines for free. Sources: omnara:nov07-price.
Credits [supported] Managed models and machines are paid with credits that carry a 5% service fee; accepted startups can receive credits. Sources: omnara:nov12-pricing.
Trial [unknown] Trial: no explicit product-scoped answer found in the checked first-party material.
Overages [supported] Managed models and machines are metered; purchased resource credits carry a 5% service fee. Sources: omnara:gap39-pricing.
Taxes [unknown] Taxes: no explicit product-scoped answer found in the checked first-party material.
Model cost [supported] Managed models at provider token rates, plus the 5% service fee on credits. Sources: omnara:nov12-pricing.
Compute cost [supported] $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention. Sources: omnara:nov07-price.
Scenario cost and controls: No platform fee and no per-seat fees on Omnara Cloud self-serve; self-hosting is free. Enterprise pricing is by contact. Not established: one person, two people, five people, task assumptions, concurrency, tokens, compute hours, variable cost, included cost, unknown cost.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: one_person, two_people, five_people, task_assumptions, concurrency, tokens, compute_hours, variable_cost, included_cost, unknown_cost. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
11 atomic answers
One person [unknown] One person: no explicit product-scoped answer found in the checked first-party material.
Two people [unknown] Two people: no explicit product-scoped answer found in the checked first-party material.
Five people [unknown] Five people: no explicit product-scoped answer found in the checked first-party material.
Task assumptions [unknown] Task assumptions: no explicit product-scoped answer found in the checked first-party material.
Concurrency [unknown] Concurrency: no explicit product-scoped answer found in the checked first-party material.
Tokens [unknown] Tokens: no explicit product-scoped answer found in the checked first-party material.
Compute hours [unknown] Compute hours: no explicit product-scoped answer found in the checked first-party material.
Fixed cost [supported] No platform fee and no per-seat fees on Omnara Cloud self-serve; self-hosting is free. Enterprise pricing is by contact. Sources: omnara:b10-pricing.
Variable cost [unknown] Variable cost: no explicit product-scoped answer found in the checked first-party material.
Included cost [unknown] Included cost: no explicit product-scoped answer found in the checked first-party material.
Unknown cost [unknown] Unknown cost: no explicit product-scoped answer found in the checked first-party material.
Full platform is free with own models/machines and no card. Accepted startups get credits for models and machines (amount not stated); purchased credits carry a 5% service fee. No card is required to start.
Scope
Surfaces: api, cloud, self-hosted · Version: Earlier findings: Docs at 01ecca98c6dc9d1f0b30472dd0b868c4b9ec9987; omnarad v0.2.17; 2026-11-22 inherited-lead additions: omnara-ai/omnara 313ac70 docs and source (= omnarad-v0.2.27 and cluster-v0.2.27, 2026-11-20; read 2026-11-22) and omnara.com/pricing read 2026-11-22 · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-22
Not established by this source pass: trial, credits_trial, paid_only, early_access, usage_caps, paid_evaluation.
Unknown after the 2026-11-22 inherited-lead recheck of first-party docs, releases and public code: trial, paid_only, early_access, usage_caps, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
Documentation, release and public-code recheck only (2026-11-22); no configured product fixture was run.
10 atomic answers
Ongoing free [supported] Self-serve full platform $0 and free self-hosting. Sources: omnara:nov07-price.
Trial [unknown] Trial: no explicit product-scoped answer found in the checked first-party material.
Credits trial [partial] Accepted startups get credits for models and machines (amount not stated); purchased credits carry a 5% service fee. No card is required to start. Sources: omnara:b10-pricing.
The current distribution exposes a Node.js CLI, browser dashboard and SDK. The daemon has complete macOS/Linux build targets, and the README documents those hosts. The scoped frontend workspace ships no native iOS/Android app. Browser agent navigation adapts to mobile through AgentSidebar isMobile logic.
Slack and Discord integrations can supply an interaction handler that presents an agent's questions and approvals in the assigned conversation; the dashboard remains available if provider delivery fails.
Kind
documented
Locator
Select capabilities independently; Route questions and approvals
The only frontend app is a React web app built with Vite; no service-worker or push-notification API use was found in frontend sources (searched PushManager, serviceWorker, Notification.requestPermission).
YAML/JSON config selects provider/model/tools, versioned profiles and skills. Product subagents have model overrides, messaging, parent return, depth/instance caps and shared machines. Project memory stores retain current files without history.
API keys and custom compatible endpoints including local vLLM; project model grants and token/time limits. Presets OpenAI/Anthropic/OpenRouter are model providers, not CLI harnesses.
Omnara owns the model/tool execution loop and resolves model API endpoints. Bounded inspection of the kernel and provider configuration found no integration of Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity coding-harness sessions. Model endpoints use supplied API credentials; no agent-subscription login adapter is implemented.
Kind
source-inspected
Locator
AgentExecutor ModelResolver/ToolExecutor; internal/modelprotocol and docs/organization/model-providers.mdx
Omnara Cloud needs a sign-in at app.omnara.com; self-hosting runs with Docker Compose and a local sign-up. Workers run the agent loop and every step is saved in Postgres. The CLI, dashboard, REST API and SDK launch agents. An agent can use several machines and, if a laptop goes offline, continue in a sandbox and sync back with git. Workers call the project's configured model providers (OpenAI, Anthropic, OpenRouter, Bedrock, LiteLLM, Ollama or compatible endpoints). The dashboard shows tool calls; self-hosted history stays in your own Postgres. The FAQ says the API, CLI, SDK and config format are the same on Cloud and self-hosted, and Apache 2.0 applies.
Kind
documented
Locator
Quickstart (Omnara Cloud, Self-host); How it works; Features; FAQ
Every step is saved to Postgres so another worker resumes from the last saved step; a worker holds a lease on one agent, renewed about every 30 seconds, and a worker that lost its lease cannot save. Model errors are retried up to eight times; deploys give work 20 seconds to drain; commands keep running when the worker dies; a command not accepted within five minutes fails and an offline machine is reported unreachable after 30 seconds; approvals wait indefinitely.
Kind
documented
Locator
Failure table; How recovery works; Model calls; Approvals, questions, and machines
Omnara runs the agent loop and runtime for each configured agent; users interact by reading or streaming its event log, sending inputs and resolving questions and approvals.
Full platform $0 with no seat fees. Own models/machines free; managed models provider rates; managed runtime $0.0414/GiB-hour and retention $0.20016/GiB/30 days. No card. SOC2 Type II observation period in progress.
Own laptop/VM or provider sandbox executes commands via outbound daemon. Agent state belongs to control plane. Offline execution host returns retryable errors and need not preserve a live command result.
A user-owned GitHub App (guided registration for GitHub.com) gives agents PR tools (read, discussion and review comments, replies, start/submit/discard review, resolve threads) and HTTPS Git/gh credentials on github.com. Credentials are read-only unless 'Let agents push code' is enabled and can be limited to repository_ids; pushes stay subject to GitHub rules and cannot change .github/workflows. Human PR discussion, review input and new commits steer the agent; PR-open, mention launches and steering comments require repository write access.
Kind
documented
Locator
Connect your GitHub App; PR tools; Git credentials
At 313ac70 the only client app is the React/Vite web app in frontend/apps/web; the other workspace packages are the omnara CLI, a React hooks library and the TypeScript SDK. No package.json or go.mod declares Electron, Tauri, Capacitor, React Native, Expo or Wails, the web app's index.html links no web app manifest, public/ holds only a favicon and logos, and no service worker is registered. Phone use is through the same web app, whose sidebar switches layout through the use-mobile hook (isMobile). The organization's other public repositories (codex, homebrew-core, harness-equivalence, omnara-terminal-bench, listed 2026-11-22) contain no client application.
Kind
source-inspected
Locator
frontend/apps (only web); frontend/pnpm-workspace.yaml; packages cli, react, sdk; frontend/apps/web/index.html and public/; hooks/use-mobile.ts; search of every package.json and go.mod for electron, tauri, capacitor, react-native, expo, wails; search of frontend for serviceWorker, PushManager, manifest.json, webmanifest
Queued/steering inputs can be reordered/canceled/promoted; config changes take effect on next model call. Inputs attribute authenticated users or project actors.
Configs are immutable and a changed source gets a new config ID; profile updates advance a generation and keep previous versions in history. secret_env_overlay injects project secrets into agent processes, OMNARA_ names are reserved, and revoked secrets are omitted. Subagents spawned with spawn_agent are full agents managed with read_agent, send_agent_message, stop_agent and list_agents, nesting up to max_depth (default 1, at most 8).
Kind
documented
Locator
Immutable configs; secret_env_overlay; Subagents; Advance a profile to a new config
Inputs can attach images, PDFs, text files, spreadsheets and Office documents; steering messages arrive at the next model call; a running agent's config (model, tools, permissions, instructions) can be changed through the API without restarting; every input is attributed to the authenticated caller or a named actor.
Kind
documented
Locator
Attach files and images; Queued vs steering; Change the config mid-conversation; Actors and attribution
The scoped persisted work records and UI/API routes manage agent conversations, profiles, events, integrations and schedules. Inspection of the database query models, HTTP routes and web pages found no independent product-owned issue/backlog CRUD and work-item state model.
Kind
source-inspected
Locator
Agent record queries; internal/httpapi routes; frontend/apps/web/src/routes
Postgres event state survives worker crashes; another worker resumes saved steps without automatic tool rerun. Model calls retry up to eight times; interrupted external tools have unknown outcomes. Approval state persists.
A configured profile can launch an agent when a pull request is opened, when the bot is mentioned, or both; PR comments, reviews and synchronize commits are forwarded to the agent.
Slack/Discord mentions and GitHub PR events launch agents; integration schedules (cron + timezone, also via the cron-triggers API) launch a fresh agent per occurrence. The schedule shows queued/processing/completed/failed; a disconnected integration skips an occurrence with a visible failure.
Kind
documented
Locator
docs/integrations/overview.mdx lines 175-259 (Launch from provider events; Start a new thread on a schedule), commit 89a8ec9 (tag cluster-v0.2.19)
Managed Ubuntu machines include dev tools; own provider image/snapshot supported. Files/processes survive idle suspension until deletion. Project grants and pool maximum capacity are hard limits.
BYO machines are user-managed; pool machines are created on demand and deleted when released or after a configured idle period. When a machine goes offline a process may continue, but the agent cannot interact with it until the daemon reconnects; waiting tool calls return a retryable error after a grace period.
A pool machine keeps files, installed dependencies and running processes across turns, including across provider suspend/resume. It is deleted on delete_machine, pool deletion or after the idle period (at least 5 minutes, 0 disables); conversation, events and artifacts remain.
Kind
documented
Locator
What persists; idle deletion (delete_after_idle_minutes)
Official example agent instruction tells the parent to give each self helper sharing its machine its own checkout via `git worktree add` and to work only there; worktree use is instruction text in this example config.
Machine pools can use twelve sandbox providers; the table lists Daytona as containers and Agent37/Modal as gVisor containers, and Blaxel, boxd, CreateOS, E2B, Superserve, Unikraft as microVMs and Arker, Freestyle, Tenki as full VMs. Hosted organizations start with a managed Blaxel microVM pool.
Each agent's timeline lists ordered events (inputs, model outputs with requested tool calls, tool results with succeeded/failed/denied/canceled outcomes) by turn, readable through GET /events or a live stream.
Event and turn paths expose only GET operations; there is no API to edit or delete agent events. Usage endpoints return model calls, tokens and cost totals by model for an agent (optionally including subagents), profile, project and organization, plus day/week/month timeseries.
Kind
source-inspected
Locator
paths /agents/{agentID}/events, /turns, /usage; /orgs/{orgID}/usage and /usage/timeseries; UsageReport schema
Omnara Cloud has a $0 platform fee and no per-seat fees; managed models bill at provider token rates and managed machines at $0.0414 per GiB of memory per hour online plus $0.20016 per GiB per 30 days retained, with idle machines auto-sleeping. BYO keys and machines are free, self-hosting is free, no credit card is required, and credits carry a 5% service fee. Accepted startups get credits for models and machines (amount not stated); Enterprise is by contact.
The web app has organization and project usage pages with a date-range menu and timeseries panel, usage on agent profile pages, and a per-agent usage panel in the agent sidebar with an include-subagents toggle (on by default) that shows provider-reported cost and per-model rows. The usage components contain no CSV or file download (searched csv, export, download, blob).
Org owner/admin/member and project admin/developer/operator/viewer have explicit permissions. Operators can launch, send input, resolve interactions and stop shared agents.
The scoped agent UI renders event timelines and downloadable artifact cards. Inspection of the conversation/artifact components found no proposed-code-change or code-diff review interface; GitHub tools and external pull requests are separate.
A GitHub-launched agent gets tools scoped to its assigned pull request: read details/diff/files/comments/reviews, post conversation and inline diff comments, reply, and build and submit a COMMENT review (it cannot approve or request changes).
Agents can get HTTPS Git credentials from the GitHub App integration; they are read-only unless 'Let agents push code' is enabled, in which case agents can push with ordinary git commands, subject to GitHub repository rules.
Cloud has a $0 platform fee and no seat fees; optional managed models and machine runtime/retention are consumption-billed, with a 5% service fee on purchased managed-resource credits. Enterprise deployment, integrations, SSO setup and support require contact; no public monthly Enterprise price or subscription/one-time software licence plan is listed.
No platform or per-seat fee; Omnara-managed models at provider token rates; credits for Omnara-managed models and machines carry a 5% service fee; managed runtime $0.0414 per GiB-hour online plus $0.20016 per GiB per 30 days retained; Enterprise via contact; accepted startups receive model and machine credits (amount not stated).