Architecture explorer
Every box below is a real process and every arrow a real call. Select one to see what it does, the port it listens on, the trust boundary it enforces, and the source lines that back the claim. The runtime manager and the harness open into component views.
System map
Swipe sideways to pan the diagram. Tap a component for details.
Click a component for what it does, its port, the trust boundary it enforces, and the code. Runtime manager and harness open into component views.
- Trusted host code
- Untrusted guest code
- The microVM wall
- A gate: what a caller must present
Sequences
Step through each one, or press play. Scenario buttons switch to the failure and refusal paths.
1. POST /v1/runs
The SDK sends { agentName, input }. The route requires the runs:execute scope.
1. ExecTool
tool_name, args (Struct), run_id, step_id, vm_id, timeout, idempotency_key run_id:step_id:attempt, tenant_id.
engine/step_executor.go:405engine/step_executor.go:417v1/runtime.proto:469
1. CONNECT api.github.com:443
The workload uses HTTPS_PROXY=http://127.0.0.1:3128 as usual.
1. POST /v1/runtime/schedule
AgentSpec: image, isolation, limits, egress, secrets, and optional idleTimeoutSecs.
server/main.go:787handlers/runtime.go:1730handlers/runtime.go:754
Sandbox states
Swipe sideways to pan. Tap a state or an arrow.