ClankerThe runtime for autonomous agents

Define agents once, run them across providers, compose them into systems, and host them with durable events, rules, tasks, and registries.

Get started

Runtime

Host

One runtime, multiple providers

Use the same agent model with local handlers, Codex, or Claude. Provider capabilities stay explicit instead of being flattened to a lowest common denominator.

Composition without a second framework

Call agents recursively or combine them as chains, routers, and teams. Runs share the same event, validation, approval, cancellation, and deadline machinery.

Reactive by default

A typed event bus, rules engine, and distributed task pad turn agent output into durable, inspectable workflows without application-specific orchestration glue.

Run it as a service

The Clanker host wires the runtime, registry, bus, rules, pad, MCP tools, HTTP API, async messages, and SSE progress into one deployable process.

Portable agents and registries

Define provider-neutral agents, publish versioned definitions, verify content digests, pull them into a host, and bind the execution provider at the destination.

Session portability included

sesh is one Clanker capability: move live conversations between Codex and Claude Code through a provider-neutral canonical message format.

What Clanker owns

text

Agent definition + run context
              │
              ▼
       Clanker runtime ──────▶ Local / Codex / Claude
              │
              ├──────────────▶ normalized events
              ├──────────────▶ runtime tools and child agents
              └──────────────▶ bus → rules → pad → executors

Clanker owns agent definitions, execution, provider adapters, normalized events, runtime tools, composition, and reference persistence. The embedding platform still owns credentials, external triggers, network policy, and VM isolation.

Start with a single offline agent in Getting started, then move outward to the runtime, reactive core, and host.