Federated runtime

The runtime for federated agent organizations.

Agent orchestration keeps work behind one controller. Entangle lets agents and users live as signed nodes across machines, coordinate over Nostr, exchange git-backed artifacts, and remain governable from one graph.

The model

Six surfaces for a distributed organization.

Entangle keeps the distributed organization legible. You can see who exists, where they run, what they can do, what they produced, and which signed event moved the work forward.

Host

The graph authority for desired state, runner trust, assignments, policy, projection, audit, and operator APIs.

Distributed runners

Generic workers can run on different machines, advertise capability, receive assignments, and start the right node runtime.

User nodes

Human participants are graph actors with stable identity, signed tasks, signed approvals, conversation, and review.

Nostr coordination

Signed messages let nodes coordinate without exposing every runner to direct inbound connections.

Git artifacts

Code, reports, source changes, and knowledge outputs move through durable git-backed references.

Projection

The Host turns signed observations from distributed runtimes into one live operating view for Studio and CLI.

Strengths

Built for governed, distributed AI work.

Entangle is designed for organizations where work crosses agents, users, repositories, approvals, and machines.

Federation over orchestration

Entangle does not hide every agent behind one central dispatcher. It lets an organization of independent actors coordinate through signed protocol boundaries.

Distributed execution

Runners can sit on different machines and still receive assignments through signed control messages and relay-based coordination.

Human accountability

Users participate as graph nodes and sign task, reply, approval, and review actions with their own identity.

Durable work products

Artifacts move through git, so output has history, references, diff, restore, and review semantics built in.

Engine freedom

OpenCode and other agent engines sit behind adapters. Entangle stays the federated operating layer around them.

Live observability

Studio and CLI show the same Host projection: nodes, runners, sessions, turns, approvals, artifacts, memory, and events.

Deployment shapes

Keep the organization federated wherever it runs.

Entangle keeps the same architecture wherever the parts live. Put everything on a workstation for a compact deployment, or place Host, runners, relay, and git services across your own infrastructure.

Workstation shape

Host, runners, relay, git backend, Studio, and CLI on one workstation for a compact operating environment.

Federated shape

Host on one machine, runners joining from others, shared relay and git services, and signed events as the coordination boundary.

Self-hosted operations

Production identity, audit retention, recovery, policy, and team operations on the same federated runtime model.

Run a federated AI organization.

Boot Entangle, open Studio, and watch distributed agents, users, runners, signed messages, approvals, and git-backed artifacts move through one governed graph.