Pre-release, but the runtime shape is real.
Entangle has moved past static architecture notes into runnable Host, runner, user-node, artifact, Studio, CLI, and deterministic agent-execution paths. The remaining work is mostly validation and hardening against real providers, real repositories, and real distributed infrastructure.
Current public release: v0.1.0-alpha.1.
Implemented
The core runtime exists in code.
- Host control plane with graph, package, principal, runner, assignment, projection, event, session, approval, artifact, memory, recovery, and source-change surfaces.
- Generic runner registration, trust/revoke, heartbeat, signed assignments, and deterministic process-runner smoke coverage.
- User Node runtime with stable identity, signed task launch, reply, approval, inbox/outbox, and a human-node client surface.
- OpenCode-oriented engine boundary with fake OpenCode and fake external HTTP paths for deterministic tests.
- Git-backed artifact publish/retrieve flows and source-change handoff records.
- Studio and CLI surfaces over the same Host projection.
Verified automatically
Deterministic checks cover the important path.
- Repository-wide verify task for lint/type/test coverage.
- Federated development strict preflight.
- Disposable runtime smoke for the federated developer profile.
- Fake OpenCode process-runner smoke for agent execution without external LLM APIs.
- User-node runtime demo and deterministic smoke paths.
- Product naming checks that reject obsolete local-only product framing.
Manual validation
These are not public completion claims yet.
- Real OpenCode connected to real LLM provider credentials.
- Real coding task producing a commit or PR in an operator-selected repository.
- Physical multi-machine proof with Host, runner, User Node, relay, and git service on different hosts.
- Long-running recovery, backup/restore, and operational retention exercises.
- Security review beyond the current pre-release trust model.
Next hardening passes
The plan from here is validation, not a product pivot.
Real-provider validation
Run OpenCode or another adapter against live credentials, capture failures, and harden provider setup, secrets, retries, and usage reporting.
Physical federation
Prove the same scenario across different machines and networks with no Host-runner shared filesystem assumptions.
PR workflow
Exercise real git remotes, source-change review, branch publication, and pull request creation from agent output.
Production packaging
Harden identity lifecycle, install/update paths, monitoring, backup/restore, and security disclosure process.
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.