How OpenGeni runs your agents.
The runtime architecture, the compute targets a session can run on, a Helm quick start and the HTTP surface you build against.
The event log is the truth. The bus is just the wire.
Clients talk only to the API. Durable execution coordinates the work and every session is written down — so a crash or a deploy doesn't lose it.
Miss live events and the API backfills them in order. Nothing is inferred after the fact — sessions replay exactly as they happened.
Streaming is a convenience layer, not the record. That separation is why the hot path stays cheap and the history stays honest.
Model calls, tools, sandbox commands, repo edits — each runs once and is written down, so a restart never re-charges or re-sends.
under the hood · Postgres, Temporal, NATS, S3, the OpenAI Agents SDK and MCP — boring, proven pieces, none of them hidden from you.
Pick where every session runs. A managed sandbox, or your own machine.
A fresh isolated environment we create and tear down, or a machine you already own — with your repos and files mounted in. Choose per session.
Bring your own runtime.
Any backend that satisfies the SandboxClient contract works: create, resume, delete, and materialize resources. Add yours next to the ones we ship.
- Surface
- createSandboxClient(settings)
- Resources
- Manifest with gitRepo + s3Mount entries
- State
- deserialize / serialize SandboxSessionState
Plus anything else that implements the contract.
Secure by default. Nothing leaks in unless you say so.
No host environment enters the sandbox by default. Opt into a profile — Azure, GitHub — or allowlist variables explicitly. Model keys stay with the worker.
Tuned for infra work out of the box.
Terraform, Checkov, Azure CLI, GitHub CLI and shell utilities included. Swap in your own image any time.
One stack. Every cloud.
Where agents run is a compliance question, not a preference. Pick a profile, point it at your cloud — the stack you develop against is the one that ships.
- product access mode
local · configured · managed - billing mode
disabled · stripe - sandbox backend
docker · modal · local · none - secrets
Secret · ExternalSecret · Key Vault / Secrets Manager - availability
rolling · PDB · topology spread · HPA opt-in
Sessions are just an endpoint. No magic SDK required.
Drive the runtime over plain HTTP. The app we ship is just another client.
Routes shown without the /v1 path prefix for clarity. The shipped API mounts everything except /healthz under /v1.
Built in the open.
Apache-2.0, with contribution and security guides in place. Next up: agents and environments as first-class resources, webhooks, and more sandbox backends.