Implemented
Host APIs, Studio, CLI, runner registry, assignments, signed user-node task/reply/approval paths, artifact publishing, memory, and deterministic distributed smoke coverage.
Pre-release federated runtime
Run coding agents as a governed graph.
Entangle is a self-hosted runtime for observable coding-agent organizations. Agents and human users are graph nodes with identities; runners can live on different machines; messages are signed; work moves through git-backed references.
Deterministic proof
The strongest automated path uses fake OpenCode/model endpoints so the runtime can be verified without paid LLM credentials.
Manual validation
Real OpenCode/provider usage, physical multi-machine deployment, and real PR workflows are available for operator testing but remain the next hardening pass.
Product thesis
A distributed AI engineering organization, not a chatbot wrapper.
Entangle keeps topology, identity, policy, execution, artifacts, memory, and observation as explicit runtime boundaries. It is designed so a compact workstation deployment and a multi-machine deployment use the same product model.
The graph is the runtime
Nodes, edges, identities, policies, runner placement, and artifact routes are operational state, not a diagram beside the system.
Every actor has identity
Host, runner, agent node, user node, git principal, and operator roles stay separate so authority and audit remain legible.
Messages coordinate work
Nostr carries signed control, observation, and node-to-node events. Large work products move through artifact backends.
Git carries durable output
Agents publish source changes, reports, wiki updates, and handoff artifacts as refs with history and restore semantics.
Runtime surfaces
The important parts are already visible.
The repository now has a working deterministic proof of the federated model. The remaining work is hardening, real-provider validation, and production packaging, not a change in product identity.
Host
The control plane for graph state, package admission, runner trust, runtime assignments, projection, audit, and APIs.
Runners
Generic processes that join, advertise capability, accept assignments, and run agent, user-interface, or service nodes.
User nodes
Human participants with their own graph identity, inbox, replies, approvals, and artifact review path.
Studio and CLI
Operator surfaces over the same Host projection, with Studio visual and CLI scriptable.
Current proof
Run it locally without making the architecture local-only.
The compact developer profile can run Host, relay, runners, user-client runtime, git backend, Studio, and CLI on one machine. That is a deployment convenience: the runtime path still communicates through explicit APIs, signed events, and artifact references.
Run the developer proofNotes
Field notes from the runtime.
RuntimeOperations
Run the proof
The clearest way to understand Entangle is to run the deterministic proof and inspect the graph, runners, user node, messages, and artifacts.
Apr 26, 2026
VisionRuntime
The team is the runtime
Entangle models a coding organization as a graph of agent nodes, user nodes, runners, policies, messages, memory, and artifacts.
Apr 26, 2026
ArchitectureFederation
Why federation, not orchestration
Entangle keeps Host, runners, user nodes, agent runtimes, and artifacts on explicit boundaries instead of hiding every actor behind one controller.
Apr 26, 2026
Run a coding-agent organization as a graph.
Boot Entangle, open Studio, and watch distributed agents, users, runners, signed messages, approvals, and git-backed artifacts move through one governed graph.