All stories
Omnara Ecosystem Community reports

Omnara pitches an open-source Claude Managed Agents alternative, with E2B now in the mix

Omnara's October 21 launch discussion introduces a self-hostable managed agent platform. Its latest daemon release adds E2B pools, while the agent loop and history live outside the machines running commands.

Sources (4)

Why now Founder Kartik introduced the current managed-agent product on Hacker News on October 21, distinguishing it from Omnara's earlier remote-control app. That day's omnarad v0.2.9 release also adds an E2B machine-pool provider.

Omnara wants the agent to keep running when the laptop closes, without tying its model and execution environment to one provider. In an October 21 Hacker News launch discussion, founder Kartik presented the current product as an open-source alternative to Claude Managed Agents: an API that runs agents, stores their state and manages the machines they use.

This is a change from the earlier Omnara remote-control app for Claude Code and Codex. The founder describes a new product with its own agent loop, rather than a phone interface relaying a laptop’s existing harness. Its API, CLI, TypeScript SDK and dashboard expose that platform; compatible external MCP clients can also launch and manage Omnara agents.

The log stays separate from the machine

According to the project’s English documentation, agent state lives in an append-only Postgres event log. Stateless workers take turns processing model calls and tool calls. Machines run the separate omnarad daemon, which connects outbound, allowing command execution without opening inbound ports.

The practical pitch is that an agent can use a laptop and a cloud sandbox in the same session. In the founder’s example, it pushes work to GitHub and pulls it into a sandbox when the laptop goes offline. That is an author-described workflow, not evidence that arbitrary local files automatically synchronize or that AITrending has tested recovery.

There is also a dated implementation change: omnarad v0.2.9, released October 21, adds an E2B machine-pool provider. The same release fixes duplicated or escaped tool results and pool-lock behavior. Its macOS daemon binaries require macOS 13 or later. The daemon version should not be confused with a TypeScript SDK version.

Cloud quickstart or your own control plane

The pinned README’s cloud route requires Node.js 22 or newer. Sign in at app.omnara.com, save an agent.yaml selecting the provider, model and machine pool, then run:

npx omnara agents launch --file agent.yaml --name "Machine assistant" --message "Report this machine's operating system and free disk space."

For an application integration, the documented SDK is @omnara/sdk; a dashboard-created API key goes in OMNARA_TOKEN. The cloud quickstart supplies a default model provider and sandbox pool. A new self-hosted instance does not: operators must add a provider and model, connect a machine and explicitly share those resources with the project.

Self-hosting uses Docker Compose:

docker compose -f compose.yaml --profile app up -d

The local console opens on port 8000. The README explains how to point the CLI at that instance and use machine_name instead of the cloud pool. Cloud sandboxes need a publicly reachable deployment URL. Local defaults are explicitly insecure and require the production configuration guide before exposure.

Permission controls and costs still matter

Tool policies can allow a call, ask a person or block it, while model, machine and MCP credentials are shared with projects explicitly. The model provider is a separate choice from the Omnara harness; the platform documents compatible endpoints including OpenAI-style and Anthropic-style APIs.

The code is Apache-2.0 licensed. Omnara describes no platform fee with users’ own keys and machines, but model tokens, self-hosted infrastructure and managed sandbox usage still have costs. Durability, recovery and operational savings remain project claims, not independently measured results in this report. The concrete development is a newly presented managed-agent workflow with a versioned E2B addition, rather than a claim that every existing feature first shipped this week.