Back to the Finder

Omnara

Open-source browser app. Agents run on your computer, on your own server or in the vendor's cloud.

Product websiteomnara.com Compare with others Missing or wrong data?

No reviewed screenshot available.
Desktop app
Not listed
Browser
Yes
Phone
Phone browser
Command line
Yes
Agents
No
Your subscription
No
Agents run
On your computer, on your own server and in the vendor's cloud
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
No
Team
Shared sessions, roles and SSO
Self-hosting
Yes
Licence
Apache-2.0
Price from
Free
How it charges
Free plan, usage-based, per machine or compute and bring your own key
Paid plans from
Contact sales

Receipts

Checked
· oldest answer 2026-11-07
Findings
38 published · 27 cross-checked by a second agent · read them all
Sources
30 public pages on 3 sites: github.com, docs.omnara.com, omnara.com
Screenshot
None accepted yet
Method
Same rules for all 103 researched ADEs. How we check · Report wrong data

What it does

Where you use it

Current Omnara exposes web, CLI and API; current native mobile clients are not established. Current source ships a Node CLI and mobile-adaptive browser dashboard but no native phone app. The documented native execution-daemon targets are macOS and Linux.

Source and scope for Where you use it

Agents it runs

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.

Source and scope for Agents it runs

Accounts and subscriptions

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.

Source and scope for Accounts and subscriptions

Where agents run

Control plane persists independently of user/BYO or managed execution machines.

Source and scope for Where agents run

How work is kept apart

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.

Source and scope for How work is kept apart

Parallel work

Product subagents run concurrently within configured caps.

Source and scope for Parallel work

Scheduled runs

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.

Source and scope for Scheduled runs

Git and pull requests

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.

Source and scope for Git and pull requests

Licence and source

Omnara describes the full platform as Apache-2.0 open source.

Source and scope for Licence and source

Price

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.

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: macOSUnknown
Desktop OS: WindowsUnknown
Desktop OS: LinuxUnknown
Web clientYes
Phone access: Native iOSNo
Phone access: Native AndroidNo
Phone access: Phone browserYes
CLIYes cross-checked
Coding agents: Claude CodeNo
Coding agents: CodexNo
Coding agents: Cursor AgentNo
Coding agents: Gemini CLINo
Coding agents: OpenCodeNo
Coding agents: PiNo
Coding agents: GrokNo
Coding agents: AiderNo
Coding agents: AntigravityNo
Use my subscriptionNo
Where agents run: On your computerYes cross-checked
Where agents run: On your own serverYes cross-checked
Where agents run: In the vendor's cloudYes cross-checked
Workspace isolation: Git worktreeYes
Workspace isolation: ContainerYes cross-checked
Workspace isolation: VM or microVMYes cross-checked
Parallel runsYes cross-checked
CoordinatorYes cross-checked
Native issue trackingNo
Unattended triggersYes cross-checked
Shared promptingYes cross-checked
Team rolesYes cross-checked
SSOYes cross-checked
Pull request workflowYes cross-checked
Review interfaceNo
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-outUnknown
Free accessYes cross-checked
Starting price: FreeYes. Free
Starting price: Up to $20/monthNo. Free
Starting price: $21–40/monthNo. Free
Starting price: $41–100/monthNo. Free
Starting price: Over $100/monthNo. Free
Starting price: Contact for pricingNo. Free
Pricing model: Free, no paid planNo
Pricing model: Free planYes
Pricing model: SubscriptionNo
Pricing model: Per seatNo
Pricing model: Usage-basedYes
Pricing model: Per machine or computeYes
Pricing model: Bring your own keyYes
Pricing model: One-time purchaseNo
Paid plans from: No paid planNo. Contact sales
Paid plans from: $10 or less/monthNo. Contact sales
Paid plans from: $11–20/monthNo. Contact sales
Paid plans from: $21–40/monthNo. Contact sales
Paid plans from: $41–100/monthNo. Contact sales
Paid plans from: Over $100/monthNo. Contact sales
Paid plans from: Contact salesYes. Contact sales
Lifecycle status: ActiveUnknown
Lifecycle status: SunsettingUnknown
Keeps going with laptop closedYes cross-checked
Open-source licenseYes. Apache-2.0 cross-checked
Any desktop appUnknown
Paid plan up to $20/monthNo. Contact sales
Paid plan up to $40/monthNo. Contact sales
Any phone clientYes

Filter receipts

Web client: Yes

Web client

Typed value: Yes.

Current Omnara exposes web, CLI and API; current native mobile clients are not established. Current source ships a Node CLI and mobile-adaptive browser dashboard but no native phone app. The documented native execution-daemon targets are macOS and Linux.

  • Browser: Dashboard launches and inspects agents.
  • Cli: omnara CLI launches, lists, waits and cancels.
  • Task actions: Configure/launch agents, send inputs, stop and archive through dashboard/CLI.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

  2. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

Phone access: Native iOS: No

Phone access: Native iOS

Typed value: No.

Current Omnara exposes web, CLI and API; current native mobile clients are not established. Current source ships a Node CLI and mobile-adaptive browser dashboard but no native phone app. The documented native execution-daemon targets are macOS and Linux.

  • Mobile apps: The scoped current frontend distribution ships a web dashboard, CLI and SDK, with no native iOS/Android app.
  • Mobile browser: The web agent sidebar and conversation navigation adapt to mobile viewports.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara current clients

    Finding: 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.

Phone access: Native Android: No

Phone access: Native Android

Typed value: No.

Current Omnara exposes web, CLI and API; current native mobile clients are not established. Current source ships a Node CLI and mobile-adaptive browser dashboard but no native phone app. The documented native execution-daemon targets are macOS and Linux.

  • Mobile apps: The scoped current frontend distribution ships a web dashboard, CLI and SDK, with no native iOS/Android app.
  • Mobile browser: The web agent sidebar and conversation navigation adapt to mobile viewports.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara current clients

    Finding: 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.

Phone access: Phone browser: Yes

Phone access: Phone browser

Typed value: Yes.

Current Omnara exposes web, CLI and API; current native mobile clients are not established. Current source ships a Node CLI and mobile-adaptive browser dashboard but no native phone app. The documented native execution-daemon targets are macOS and Linux.

  • Mobile apps: The scoped current frontend distribution ships a web dashboard, CLI and SDK, with no native iOS/Android app.
  • Mobile browser: The web agent sidebar and conversation navigation adapt to mobile viewports.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara current clients

    Finding: 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.

CLI: Yes cross-checked

CLI

Typed value: Yes.

Product CLI, REST API, TypeScript SDK and event webhooks operate durable agents.

  • Cli: omnara CLI.
  • Api: REST API.
  • Sdk: TypeScript @omnara/sdk.
  • Webhooks: Project/profile/agent-scoped event subscriptions.
  • Operations: Launch/send/inspect/wait/cancel/archive plus resource management.
  • Authentication: API uses bearer authentication; project permissions gate operations.
  • Not established by this source pass: mcp_server, stability.
  1. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

  2. Omnara events/webhooks

    Finding: Event webhooks watch agent/profile/project, optionally sign payloads and retry up to ten minutes; deliveries may duplicate or arrive out of order.

  3. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

Coding agents: Claude Code: No

Coding agents: Claude Code

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Coding agents: Codex: No

Coding agents: Codex

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Coding agents: Cursor Agent: No

Coding agents: Cursor Agent

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Coding agents: Gemini CLI: No

Coding agents: Gemini CLI

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Coding agents: OpenCode: No

Coding agents: OpenCode

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Coding agents: Pi: No

Coding agents: Pi

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Coding agents: Grok: No

Coding agents: Grok

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Coding agents: Aider: No

Coding agents: Aider

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Coding agents: Antigravity: No

Coding agents: Antigravity

Typed value: No.

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.

  • Harnesses: The scoped runtime uses the Omnara model/tool loop, without Claude Code, Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok, Aider or Antigravity harness integration.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Use my subscription: No

Use my subscription

Typed value: No.

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.

  • Agent subscriptions: Provider configuration and the execution kernel use model API credentials; native agent-subscription OAuth/session reuse is not implemented in the scoped adapter set.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agent execution kernel

    Finding: 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.

Where agents run: On your computer: Yes cross-checked

Where agents run: On your computer

Typed value: Yes.

Control plane persists independently of user/BYO or managed execution machines.

  • Local: Own laptop runs omnarad command execution.
  • Byo remote: Own VM/VPC/server can connect outbound.
  • Self hosted: Full control plane can be hosted on own infrastructure.
  • Managed cloud: Managed pools provision sandbox-provider machines.
  • Provisioning: Own daemon registration or on-demand pool allocation.
  • Payer: Own resources or managed usage charges.
  • Client disconnect: Agent event state lives in control plane; client disconnect does not stop remote worker processing.
  • Other device continuation: Dashboard/API can inspect durable conversation separately from execution machine.
  • Not established by this source pass: hybrid, resources, region, expiry.
  1. Omnara machines/overview

    Finding: 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.

  2. Omnara machines/pools

    Finding: 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.

  3. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

Where agents run: On your own server: Yes cross-checked

Where agents run: On your own server

Typed value: Yes.

Control plane persists independently of user/BYO or managed execution machines.

  • Local: Own laptop runs omnarad command execution.
  • Byo remote: Own VM/VPC/server can connect outbound.
  • Self hosted: Full control plane can be hosted on own infrastructure.
  • Managed cloud: Managed pools provision sandbox-provider machines.
  • Provisioning: Own daemon registration or on-demand pool allocation.
  • Payer: Own resources or managed usage charges.
  • Client disconnect: Agent event state lives in control plane; client disconnect does not stop remote worker processing.
  • Other device continuation: Dashboard/API can inspect durable conversation separately from execution machine.
  • Not established by this source pass: hybrid, resources, region, expiry.
  1. Omnara machines/overview

    Finding: 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.

  2. Omnara machines/pools

    Finding: 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.

  3. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

Where agents run: In the vendor's cloud: Yes cross-checked

Where agents run: In the vendor's cloud

Typed value: Yes.

Control plane persists independently of user/BYO or managed execution machines.

  • Local: Own laptop runs omnarad command execution.
  • Byo remote: Own VM/VPC/server can connect outbound.
  • Self hosted: Full control plane can be hosted on own infrastructure.
  • Managed cloud: Managed pools provision sandbox-provider machines.
  • Provisioning: Own daemon registration or on-demand pool allocation.
  • Payer: Own resources or managed usage charges.
  • Client disconnect: Agent event state lives in control plane; client disconnect does not stop remote worker processing.
  • Other device continuation: Dashboard/API can inspect durable conversation separately from execution machine.
  • Not established by this source pass: hybrid, resources, region, expiry.
  1. Omnara machines/overview

    Finding: 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.

  2. Omnara machines/pools

    Finding: 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.

  3. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

Workspace isolation: Git worktree: Yes

Workspace isolation: Git worktree

Typed value: Yes.

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.

  • Worktree: Official example agent instruction tells self-subagents on the shared machine to create their own git worktree; no platform-managed worktree setting was established.
  • Code separation: Subagents share the parent's attached machines; separate checkouts depend on agent instructions such as the example's git worktree step.
  • 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.
  1. Omnara examples/slack-coding-agent/agent.yaml

    Finding: 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.

Workspace isolation: Container: Yes cross-checked

Workspace isolation: Container

Typed value: Yes.

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.

  • Container: Machine pools can use container sandbox providers: Daytona (containers) and Agent37 and Modal (gVisor containers).
  • Vm: Machine pools can use microVM providers (Blaxel default pool, E2B, boxd, CreateOS, Superserve, Unikraft) or full-VM providers (Arker, Freestyle, Tenki).
  • 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.
  1. Omnara sandbox providers

    Finding: 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.

Workspace isolation: VM or microVM: Yes cross-checked

Workspace isolation: VM or microVM

Typed value: Yes.

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.

  • Container: Machine pools can use container sandbox providers: Daytona (containers) and Agent37 and Modal (gVisor containers).
  • Vm: Machine pools can use microVM providers (Blaxel default pool, E2B, boxd, CreateOS, Superserve, Unikraft) or full-VM providers (Arker, Freestyle, Tenki).
  • 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.
  1. Omnara sandbox providers

    Finding: 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.

Parallel runs: Yes cross-checked

Parallel runs

Typed value: Yes.

Product subagents run concurrently within configured caps.

  • Concurrent sessions: Agents may spawn multiple active subagents.
  • Quotas: max_subagents and per-key max_instances.
  • Status visibility: Activity reports working_subagents and running_processes.
  • Not established by this source pass: concurrent_tasks, observed_concurrency.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

Coordinator: Yes cross-checked

Coordinator

Typed value: Yes.

Product-owned agents delegate, message/read children and receive their results.

  • Roles: Named profile/self helper declarations.
  • Model harness effort: Per-helper provider/model/reasoning/token overrides.
  • Messages: send_agent_message and read_agent tools.
  • Results return: Final answer/question/failure returns to parent timeline.
  • Orchestration owner: Omnara spawn_agent/read_agent/send_agent_message/stop_agent/list_agents.
  • Activation: Declaring subagents adds missing tools; explicit disabled tools remain disabled.
  • Live progress: Read child timeline on demand.
  • Retained results: Children have parent_agent_id and inspectable event history.
  • Followup: Parent can message existing subagent.
  • Invocation: spawn_agent task parameter starts clean-context helper.
  • Not established by this source pass: cross_harness, authentication.
  1. Omnara agents/configuration

    Finding: 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.

Native issue tracking: No

Native issue tracking

Typed value: No.

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.

  • Create: There is no product-owned issue/backlog CRUD in the inspected native routes and stores.
  • Task session separation: Agent conversations are the work records; schedules are trigger configurations, not a separate issue/task backlog.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara persisted agent records

    Finding: 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.

Unattended triggers: Yes cross-checked

Unattended triggers

Typed value: Yes.

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.

  • Recurring tasks: Integration schedules use cron plus timezone and launch a fresh agent in a new thread for each occurrence.
  • Scheduler location: 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.
  • Retries: 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.
  • Client independence: Scheduled and provider-event launches (Slack/Discord mentions, GitHub PR open or mention) start agents from the control plane without an open client.
  • Not established by this source pass: overlaps. Automatic retry of a skipped occurrence is not documented. Not tested.
  1. Omnara incoming PR work

    Finding: 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.

  2. Omnara integration launches and schedules

    Finding: 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.

Shared prompting: Yes cross-checked

Shared prompting

Typed value: Yes.

Authorized project operators can send input to the same durable agent.

  • Visibility: Read role can inspect agents.
  • Coprompting: Project operator/developer/admin may send agent inputs.
  • Ordering: Queued inputs can be reordered or switched to steering.
  • Attribution: Each input records authenticated user or external actor identity.
  • Permissions: Project permission matrix separates read/operate/manage/access.
  • Not established by this source pass: discussion, comments, presence, conflicts, plan_restrictions, owner_online.
  1. Omnara organization/members

    Finding: Org owner/admin/member and project admin/developer/operator/viewer have explicit permissions. Operators can launch, send input, resolve interactions and stop shared agents.

  2. Omnara events/sending-input

    Finding: Queued/steering inputs can be reordered/canceled/promoted; config changes take effect on next model call. Inputs attribute authenticated users or project actors.

Team roles: Yes cross-checked

Team roles

Typed value: Yes.

Organization/project roles are documented; SSO is documented for self-hosted deployments and the Enterprise offering.

  • Organization roles: owner/admin/member.
  • Project roles: admin/developer/operator/viewer with explicit permission matrix.
  • Membership: Email-addressed invitations and membership management.
  • Revocation: Remove project role/grants or organization membership within documented ownership constraints.
  • Not established by this source pass: task_roles, provisioning, unauthorized_access, plan_scope.
  • SSO connectors are self-hosted deployment environment settings; SSO for self-serve Omnara Cloud organizations was not established.
  1. Omnara organization/members

    Finding: Org owner/admin/member and project admin/developer/operator/viewer have explicit permissions. Operators can launch, send input, resolve interactions and stop shared agents.

SSO: Yes cross-checked

SSO

Typed value: Yes.

Organization/project roles are documented; SSO is documented for self-hosted deployments and the Enterprise offering.

  • Organization roles: owner/admin/member.
  • Project roles: admin/developer/operator/viewer with explicit permission matrix.
  • Membership: Email-addressed invitations and membership management.
  • Sso: Self-hosted deployments configure OIDC login connectors (Google, Keycloak, Okta, Auth0, Azure, ZITADEL); Enterprise lists SSO setup. Self-serve Omnara Cloud SSO not established.
  • Revocation: Remove project role/grants or organization membership within documented ownership constraints.
  • Not established by this source pass: task_roles, provisioning, unauthorized_access, plan_scope.
  • SSO connectors are self-hosted deployment environment settings; SSO for self-serve Omnara Cloud organizations was not established.
  1. Omnara self-hosting/configuration

    Finding: OIDC login connectors include Google, Keycloak, Okta, Auth0, Azure and ZITADEL. Self-host configuration defines service/model/machine settings.

  2. Omnara pricing

    Finding: 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.

Pull request workflow: Yes cross-checked

Pull request workflow

Typed value: Yes.

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.

  • Commits: 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.
  • Pull requests: 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.
  • Comments: Agents post PR conversation comments, inline diff comments and replies, and receive forwarded PR comments and reviews.
  • 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.
  1. Omnara GitHub integration PR tools

    Finding: 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).

  2. Omnara GitHub Git credentials

    Finding: 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.

Review interface: No

Review interface

Typed value: No.

Durable artifacts attach immutable downloadable content to agent events. The scoped artifact/conversation UI does not include a code-diff review interface.

  • Diffs: The inspected artifact cards and agent conversation components do not provide proposed-code diff review.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara artifact interface

    Finding: 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.

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

Product license: Apache-2.0

Typed value: Yes. Apache-2.0.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

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

Product license: MIT

Typed value: No. Apache-2.0.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under 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.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under 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.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under 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.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under 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.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under 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.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

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

Product license: Custom terms

Typed value: No. Apache-2.0.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

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

Product license: Proprietary

Typed value: No. Apache-2.0.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

Self-hosting: Yes cross-checked

Self-hosting

Typed value: Yes.

Full control plane can run on own database/storage/compute.

  • Self hosting: Compose deployment runs API/workers/maintenance/frontend on own infrastructure.
  • Vendor dependencies: Own Postgres/Redis/S3-compatible storage and persistent memory filesystem.
  • Export: Download immutable artifact bytes and access event logs.
  • Formats: YAML/JSON configs and durable event/artifact API.
  • Not established by this source pass: import, cancellation, account_independence, history_portability.
  1. Omnara events/artifacts

    Finding: Immutable artifact IDs and digests reference uploaded media; downloadable timeline cards remain after execution-machine removal.

  2. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

Free access: Yes cross-checked

Free access

Typed value: Yes.

Full platform is free with own models/machines and no card.

  • Ongoing free: Self-serve full platform $0 and free self-hosting.
  • Self host cost: Software free; infrastructure/model costs separate.
  • Free scenarios: Own machines/models can use full platform without seat/platform fee.
  • Card required: No credit card required.
  • Not established by this source pass: trial, credits_trial, paid_only, early_access, usage_caps, paid_evaluation.
  1. Omnara pricing

    Finding: 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.

Starting price: Free: Yes. Free

Starting price: Free

Typed value: Yes. Free.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

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

Starting price: Up to $20/month

Typed value: No. Free.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

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

Starting price: $21–40/month

Typed value: No. Free.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

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

Starting price: $41–100/month

Typed value: No. Free.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Starting price: Over $100/month: No. Free

Starting price: Over $100/month

Typed value: No. Free.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Starting price: Contact for pricing: No. Free

Starting price: Contact for pricing

Typed value: No. Free.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Pricing model: Free, no paid plan: No

Pricing model: Free, no paid plan

Typed value: No.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Pricing model: Free plan: Yes

Pricing model: Free plan

Typed value: Yes.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Pricing model: Subscription: No

Pricing model: Subscription

Typed value: No.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Pricing model: Per seat: No

Pricing model: Per seat

Typed value: No.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Pricing model: Usage-based: Yes

Pricing model: Usage-based

Typed value: Yes.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Pricing model: Per machine or compute: Yes

Pricing model: Per machine or compute

Typed value: Yes.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Pricing model: Bring your own key: Yes

Pricing model: Bring your own key

Typed value: Yes.

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.

  • Currency: USD.
  • Seats: No per-seat fees.
  • Workspace fees: Platform $0.
  • Included usage: Bring own model keys/machines for free.
  • Model cost: Managed models at provider token rates.
  • Compute cost: $0.0414/GiB/hour online plus $0.20016/GiB/30 days retention.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Pricing model: One-time purchase: No

Pricing model: One-time purchase

Typed value: No.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Paid plans from: No paid plan: No. Contact sales

Paid plans from: No paid plan

Typed value: No. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Paid plans from: $10 or less/month: No. Contact sales

Paid plans from: $10 or less/month

Typed value: No. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Paid plans from: $11–20/month: No. Contact sales

Paid plans from: $11–20/month

Typed value: No. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Paid plans from: $21–40/month: No. Contact sales

Paid plans from: $21–40/month

Typed value: No. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Paid plans from: $41–100/month: No. Contact sales

Paid plans from: $41–100/month

Typed value: No. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Paid plans from: Over $100/month: No. Contact sales

Paid plans from: Over $100/month

Typed value: No. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Paid plans from: Contact sales: Yes. Contact sales

Paid plans from: Contact sales

Typed value: Yes. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Keeps going with laptop closed: Yes cross-checked

Keeps going with laptop closed

Typed value: Yes.

Control plane persists independently of user/BYO or managed execution machines.

  • Local: Own laptop runs omnarad command execution.
  • Byo remote: Own VM/VPC/server can connect outbound.
  • Self hosted: Full control plane can be hosted on own infrastructure.
  • Managed cloud: Managed pools provision sandbox-provider machines.
  • Provisioning: Own daemon registration or on-demand pool allocation.
  • Payer: Own resources or managed usage charges.
  • Client disconnect: Agent event state lives in control plane; client disconnect does not stop remote worker processing.
  • Other device continuation: Dashboard/API can inspect durable conversation separately from execution machine.
  • Not established by this source pass: hybrid, resources, region, expiry.
  1. Omnara machines/overview

    Finding: 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.

  2. Omnara machines/pools

    Finding: 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.

  3. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

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

Open-source license

Typed value: Yes. Apache-2.0.

Omnara describes the full platform as Apache-2.0 open source.

  • Client license: Apache 2.0.
  • Server license: Self-host platform under Apache 2.0.
  • Source visibility: Public application repository.
  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

Paid plan up to $20/month: No. Contact sales

Paid plan up to $20/month

Typed value: No. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Paid plan up to $40/month: No. Contact sales

Paid plan up to $40/month

Typed value: No. Contact sales.

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.

  • Overages: Managed models and machines are metered; purchased resource credits carry a 5% service fee.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

Any phone client: Yes

Any phone client

Typed value: Yes.

Current Omnara exposes web, CLI and API; current native mobile clients are not established. Current source ships a Node CLI and mobile-adaptive browser dashboard but no native phone app. The documented native execution-daemon targets are macOS and Linux.

  • Mobile apps: The scoped current frontend distribution ships a web dashboard, CLI and SDK, with no native iOS/Android app.
  • Mobile browser: The web agent sidebar and conversation navigation adapt to mobile viewports.
  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara current clients

    Finding: 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.

All public findings

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

omnara:ACC-01: Current Omnara exposes web, CLI and API; current native mobile clients are not established. Current source ships a Node CLI and mobile-adaptive browser dashboard but no native phone app. The documented native execution-daemon targets are macOS and Linux.

omnara:ACC-01

Current Omnara exposes web, CLI and API; current native mobile clients are not established. Current source ships a Node CLI and mobile-adaptive browser dashboard but no native phone app. The documented native execution-daemon targets are macOS and Linux.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

  2. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

  3. Omnara current clients

    Finding: 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.

omnara:ACC-02: 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:ACC-02

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.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara organization/model-providers

    Finding: 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.

  3. Omnara agent execution kernel

    Finding: 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.

omnara:ACC-03: 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:ACC-03

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.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara organization/model-providers

    Finding: 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.

  2. Omnara pricing

    Finding: 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.

  3. Omnara agent execution kernel

    Finding: 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.

omnara:ACC-04: Create agent config and grants, then use dashboard/API/CLI; own machine and full self-host recipes exist. cross-checked

omnara:ACC-04

Create agent config and grants, then use dashboard/API/CLI; own machine and full self-host recipes exist.

  • Not established by this source pass: no_git, local_git_without_remote, hosted_git.
  1. Omnara machines/overview

    Finding: 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.

  2. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

  3. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

omnara:ACC-05: Product CLI, REST API, TypeScript SDK and event webhooks operate durable agents. cross-checked

omnara:ACC-05

Product CLI, REST API, TypeScript SDK and event webhooks operate durable agents.

  • Not established by this source pass: mcp_server, stability.
  1. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

  2. Omnara events/webhooks

    Finding: Event webhooks watch agent/profile/project, optionally sign payloads and retry up to ten minutes; deliveries may duplicate or arrive out of order.

  3. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

omnara:ACC-06: Agents can call MCP/custom tools and load versioned skills.

omnara:ACC-06

Agents can call MCP/custom tools and load versioned skills.

  • Not established by this source pass: plugins.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara tools/permissions

    Finding: Built-in/custom tools default allow; MCP default ask. Config declares allow/ask/deny per tool; updates required to change permission policy.

  3. Omnara tools/mcp

    Finding: Connect third-party MCP tools including bearer secrets and OAuth.

  4. Omnara tools/skills

    Finding: Versioned SKILL.md packages load on demand and are shared through explicit project grants; latest revision resolves at each model call.

omnara:PLAN-01: Agent conversations accept dashboard/API prompts and integration subscriptions. cross-checked

omnara:PLAN-01

Agent conversations accept dashboard/API prompts and integration subscriptions.

  • Not established by this source pass: local_creation, external_import, authoritative_tracker, sync, supported_edits, external_roundtrips.
  1. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

  2. Omnara events/sending-input

    Finding: Queued/steering inputs can be reordered/canceled/promoted; config changes take effect on next model call. Inputs attribute authenticated users or project actors.

omnara:PLAN-04: Agent configs, versioned skills and shared project memory retain context. cross-checked

omnara:PLAN-04

Agent configs, versioned skills and shared project memory retain context.

  • Not established by this source pass: project_docs.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara tools/skills

    Finding: Versioned SKILL.md packages load on demand and are shared through explicit project grants; latest revision resolves at each model call.

omnara:PLAN-05: External tools and versioned knowledge packages supply agent context. cross-checked

omnara:PLAN-05

External tools and versioned knowledge packages supply agent context.

  • Not established by this source pass: code_search, indexing, multimodal_inputs, citations, conflict_detection, review_enforcement.
  1. Omnara tools/mcp

    Finding: Connect third-party MCP tools including bearer secrets and OAuth.

  2. Omnara tools/skills

    Finding: Versioned SKILL.md packages load on demand and are shared through explicit project grants; latest revision resolves at each model call.

omnara:PLAN-06: 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.

omnara:PLAN-06

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.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara persisted agent records

    Finding: 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.

omnara:COORD-01: Product subagents run concurrently within configured caps. cross-checked

omnara:COORD-01

Product subagents run concurrently within configured caps.

  • Not established by this source pass: concurrent_tasks, observed_concurrency.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

omnara:COORD-02: Product dispatches subagents and leases execution steps to workers. cross-checked

omnara:COORD-02

Product dispatches subagents and leases execution steps to workers.

  • Not established by this source pass: human_assignment, claims, queues.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara agents/failure-handling

    Finding: 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.

omnara:COORD-03: Product-owned agents delegate, message/read children and receive their results. cross-checked

omnara:COORD-03

Product-owned agents delegate, message/read children and receive their results.

  • Not established by this source pass: cross_harness, authentication.
  1. Omnara agents/configuration

    Finding: 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.

omnara:COORD-04: 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. cross-checked

omnara:COORD-04

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.

  • Not established by this source pass: overlaps. Automatic retry of a skipped occurrence is not documented. Not tested.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

  3. Omnara incoming PR work

    Finding: 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.

  4. Omnara integration launches and schedules

    Finding: 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.

omnara:COORD-05: Queued/steering inputs, stop and permission interactions control work.

omnara:COORD-05

Queued/steering inputs, stop and permission interactions control work.

  • Not established by this source pass: pause, notifications, escalation, chat_terminal_parity.
  1. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

  2. Omnara agents/failure-handling

    Finding: 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.

  3. Omnara tools/permissions

    Finding: Built-in/custom tools default allow; MCP default ask. Config declares allow/ask/deny per tool; updates required to change permission policy.

  4. Omnara events/sending-input

    Finding: Queued/steering inputs can be reordered/canceled/promoted; config changes take effect on next model call. Inputs attribute authenticated users or project actors.

omnara:COORD-06: Instances dashboard filters agent activity and exposes child relationships. cross-checked

omnara:COORD-06

Instances dashboard filters agent activity and exposes child relationships.

  • Not established by this source pass: fleet_fixture, dependencies, navigation_errors, fixture_mode.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

omnara:COORD-07: Reusable profiles and mid-conversation configs customize agent behavior. cross-checked

omnara:COORD-07

Reusable profiles and mid-conversation configs customize agent behavior.

  • Not established by this source pass: quick_task, growing_epic, live_roles, discoverability, auth_friction.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara events/sending-input

    Finding: Queued/steering inputs can be reordered/canceled/promoted; config changes take effect on next model call. Inputs attribute authenticated users or project actors.

omnara:RUN-01: Control plane persists independently of user/BYO or managed execution machines. cross-checked

omnara:RUN-01

Control plane persists independently of user/BYO or managed execution machines.

  • Not established by this source pass: hybrid, resources, region, expiry.
  1. Omnara machines/overview

    Finding: 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.

  2. Omnara machines/pools

    Finding: 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.

  3. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

omnara:RUN-02: 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. cross-checked

omnara:RUN-02

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.

  • 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.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara machines/overview

    Finding: 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.

  3. Omnara examples/slack-coding-agent/agent.yaml

    Finding: 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.

  4. Omnara sandbox providers

    Finding: 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.

omnara:RUN-03: Durable event state survives workers and machine loss with explicit unknown external outcomes. cross-checked

omnara:RUN-03

Durable event state survives workers and machine loss with explicit unknown external outcomes.

  • Not established by this source pass: transcript_reload, process_reconnect, state_reconstruction, context_loss, multi_day_continuity.
  1. Omnara agents/failure-handling

    Finding: 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.

  2. Omnara machines/pools

    Finding: 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.

omnara:RUN-04: Managed pools include development tools; custom images/snapshots and startup scripts are configurable. cross-checked

omnara:RUN-04

Managed pools include development tools; custom images/snapshots and startup scripts are configurable.

  • Not established by this source pass: caches, ports, duplicate_installs, collisions, automatic_repair.
  1. Omnara machines/pools

    Finding: 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.

omnara:RUN-05: Model retries/timeouts/context limits and subagent depth caps are explicit. cross-checked

omnara:RUN-05

Model retries/timeouts/context limits and subagent depth caps are explicit.

  • Not established by this source pass: turn_limits, spend_limits, timeouts.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara agents/failure-handling

    Finding: 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.

  3. Omnara organization/model-providers

    Finding: 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:RUN-06: Agent activity distinguishes waiting, background processes, idle and archived; history records errors. cross-checked

omnara:RUN-06

Agent activity distinguishes waiting, background processes, idle and archived; history records errors.

  • Not established by this source pass: traces, usage_export, task_stats, agent_stats, project_stats, time_stats, performance_method, responsiveness.
  1. Omnara agents/overview

    Finding: Dashboard/CLI/API launch durable agent conversations; activity exposes running, waiting, idle, archived, processes and subagents. Wait requires no background work; stop retains conversation.

  2. Omnara agents/failure-handling

    Finding: 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.

  3. Omnara events/webhooks

    Finding: Event webhooks watch agent/profile/project, optionally sign payloads and retry up to ten minutes; deliveries may duplicate or arrive out of order.

omnara:RUN-08: Capacity caps and worker leases bound allocation and recovery.

omnara:RUN-08

Capacity caps and worker leases bound allocation and recovery.

  • Not established by this source pass: queues, host_awareness, check_reuse, check_deduplication, bounded_tests, cancellation, fairness.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara agents/failure-handling

    Finding: 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.

  3. Omnara machines/pools

    Finding: 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.

omnara:TEAM-01: Authorized project operators can send input to the same durable agent. cross-checked

omnara:TEAM-01

Authorized project operators can send input to the same durable agent.

  • Not established by this source pass: discussion, comments, presence, conflicts, plan_restrictions, owner_online.
  1. Omnara organization/members

    Finding: Org owner/admin/member and project admin/developer/operator/viewer have explicit permissions. Operators can launch, send input, resolve interactions and stop shared agents.

  2. Omnara events/sending-input

    Finding: Queued/steering inputs can be reordered/canceled/promoted; config changes take effect on next model call. Inputs attribute authenticated users or project actors.

omnara:TEAM-02: Organization/project roles are documented; SSO is documented for self-hosted deployments and the Enterprise offering. cross-checked

omnara:TEAM-02

Organization/project roles are documented; SSO is documented for self-hosted deployments and the Enterprise offering.

  • Not established by this source pass: task_roles, provisioning, unauthorized_access, plan_scope.
  • SSO connectors are self-hosted deployment environment settings; SSO for self-serve Omnara Cloud organizations was not established.
  1. Omnara organization/members

    Finding: Org owner/admin/member and project admin/developer/operator/viewer have explicit permissions. Operators can launch, send input, resolve interactions and stop shared agents.

  2. Omnara self-hosting/configuration

    Finding: OIDC login connectors include Google, Keycloak, Okta, Auth0, Azure and ZITADEL. Self-host configuration defines service/model/machine settings.

  3. Omnara pricing

    Finding: 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.

omnara:TEAM-03: Per-tool allow/ask/deny policy creates durable permission interactions. cross-checked

omnara:TEAM-03

Per-tool allow/ask/deny policy creates durable permission interactions.

  • Not established by this source pass: command, network, secret, delivery, approver_identity, revoke, tunnels, safer_modes.
  1. Omnara agents/failure-handling

    Finding: 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.

  2. Omnara tools/permissions

    Finding: Built-in/custom tools default allow; MCP default ask. Config declares allow/ask/deny per tool; updates required to change permission policy.

omnara:TEAM-04: Durable event timeline records attributed inputs, config changes and tool outcomes. cross-checked

omnara:TEAM-04

Durable event timeline records attributed inputs, config changes and tool outcomes.

  • Not established by this source pass: discussion, decisions, cross_user_persistence, cross_session_persistence, export, mutability, retention, integrity.
  1. Omnara agents/failure-handling

    Finding: 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.

  2. Omnara events/sending-input

    Finding: Queued/steering inputs can be reordered/canceled/promoted; config changes take effect on next model call. Inputs attribute authenticated users or project actors.

omnara:SHIP-01: Durable artifacts attach immutable downloadable content to agent events. The scoped artifact/conversation UI does not include a code-diff review interface.

omnara:SHIP-01

Durable artifacts attach immutable downloadable content to agent events. The scoped artifact/conversation UI does not include a code-diff review interface.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara machines/pools

    Finding: 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.

  2. Omnara events/artifacts

    Finding: Immutable artifact IDs and digests reference uploaded media; downloadable timeline cards remain after execution-machine removal.

  3. Omnara artifact interface

    Finding: 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.

omnara:SHIP-03: 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. cross-checked

omnara:SHIP-03

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.

  • 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.
  1. Omnara GitHub integration PR tools

    Finding: 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).

  2. Omnara GitHub Git credentials

    Finding: 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.

  3. Omnara incoming PR work

    Finding: 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.

  4. Omnara cluster v0.2.19 release

    Finding: cluster v0.2.19 is the latest release; the cited docs are read at its tag commit.

omnara:OWN-01: Omnara describes the full platform as Apache-2.0 open source. cross-checked

omnara:OWN-01

Omnara describes the full platform as Apache-2.0 open source.

  • Not established by this source pass: hosted_extensions, source_revision, hosted_parity.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

omnara:OWN-02: Full control plane can run on own database/storage/compute. cross-checked

omnara:OWN-02

Full control plane can run on own database/storage/compute.

  • Not established by this source pass: import, cancellation, account_independence, history_portability.
  1. Omnara agents/configuration

    Finding: 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.

  2. Omnara events/artifacts

    Finding: Immutable artifact IDs and digests reference uploaded media; downloadable timeline cards remain after execution-machine removal.

  3. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

omnara:OWN-03: Self-hosting controls data stores; machine deletion does not delete agent history/artifacts.

omnara:OWN-03

Self-hosting controls data stores; machine deletion does not delete agent history/artifacts.

  • Not established by this source pass: prompts, deletion, training, residency, subprocessors, telemetry_disclosure, telemetry_defaults, telemetry_controls, consent_prompt, provider_separation.
  1. Omnara machines/overview

    Finding: 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.

  2. Omnara machines/pools

    Finding: 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.

  3. Omnara organization/model-providers

    Finding: 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.

  4. Omnara tools/mcp

    Finding: Connect third-party MCP tools including bearer secrets and OAuth.

  5. Omnara events/artifacts

    Finding: Immutable artifact IDs and digests reference uploaded media; downloadable timeline cards remain after execution-machine removal.

  6. Omnara self-hosting/deployment

    Finding: Full API/worker/maintenance/frontend deployment uses own Postgres, Redis, S3-compatible bucket and memory filesystem; Docker Compose supports local/production.

  7. Omnara pricing

    Finding: 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.

omnara:OWN-04: 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.

omnara:OWN-04

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.

  • Only the named atomic answers are established by this source pass. Remaining atomic answers retain their documented gaps.
  1. Omnara pricing

    Finding: 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.

  2. Omnara pricing

    Finding: 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.

omnara:OWN-06: Current open-source daemon release and cloud/self-host access are documented.

omnara:OWN-06

Current open-source daemon release and cloud/self-host access are documented.

  • Not established by this source pass: release_stage, response_commitments, status_history, deprecation, export_options.
  1. Omnara introduction

    Finding: Web interface, CLI, REST API and TypeScript SDK; open-source self-hostable platform under Apache 2.0.

  2. Omnara pricing

    Finding: 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.

  3. Omnarad v0.2.17

    Finding: 2026-11-04 omnarad v0.2.17 (not a prerelease) adds agent status as GitHub checks on pull requests; macOS daemon binaries require macOS 13 or later.

omnara:OWN-07: SOC 2 Type II is in observation, not a completed audit claim. cross-checked

omnara:OWN-07

SOC 2 Type II is in observation, not a completed audit claim.

  • Not established by this source pass: iso_scope, iso_issuer, iso_validity, soc2_scope, soc2_period, report_access, verification_date.
  1. Omnara pricing

    Finding: 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.

omnara:OWN-08: Full platform is free with own models/machines and no card. cross-checked

omnara:OWN-08

Full platform is free with own models/machines and no card.

  • Not established by this source pass: trial, credits_trial, paid_only, early_access, usage_caps, paid_evaluation.
  1. Omnara pricing

    Finding: 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.

omnara:OWN-09: Managed usage units/rates are public; Enterprise is contact-priced. cross-checked

omnara:OWN-09

Managed usage units/rates are public; Enterprise is contact-priced.

  • Not established by this source pass: overages, compute_markup, minimum_commitment, cancellation.
  1. Omnara pricing

    Finding: 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.