Connect a repository
Planned: install the app and choose exactly which repositories may request runners.
Private pre-alpha · Open execution → verified software
Run every change on infrastructure you can inspect.
We are building ephemeral GitHub Actions runners for engineering teams and coding agents, with a durable lifecycle and bounded, provenanced evidence. Live execution is not generally available yet.
- 01QUEUEDRequest accepted
- 02PREPARINGClean execution created
- 03CONNECTEDRunner online
- 04EXECUTINGWorkflow in progress
- 05CLEANUPResources destroyed
BOUNDED RUN EVIDENCEPROVENANCED
CPUtime series
MEMpeak + average
DISKread + write
NETingress + egress
LIFECYCLE · AUTHORITATIVEGUEST DATA · UNTRUSTED
GitHub ActionsRustPostgreSQLOpenTelemetryOCI
Execution without the black box
Know what ran, what happened, and whether it was cleaned up.
BEFORE / OPAQUE
A conclusion without infrastructure context.
A red check leaves teams guessing between workflow failure, platform failure, capacity, and network conditions.
AFTER / ATTRIBUTABLE
A bounded evidence trail for every attempt.
Authoritative lifecycle and cleanup events sit beside bounded, guest-produced diagnostics under one support-safe run identifier.
Target private-alpha workflow
Keep the workflow. Replace the runner.
Change one label
Planned: point an existing GitHub Actions job at an OpenRunners profile while keeping the workflow.
Inspect the evidence
In validation: follow authoritative lifecycle and cleanup events beside explicitly untrusted guest diagnostics.
Humans and agents
The same operations across every interface.
Every interface is generated from the same active operation catalog; unavailable actions are not advertised.
CLI
Target: watch a run and retrieve bounded diagnostics from a terminal.
API
Implemented operations are typed and idempotent; the catalog remains intentionally small.
MCP
Target: give coding agents a constrained tool surface with exact run IDs.
SKILL
Target: teach agents the safe workflow and evidence vocabulary.
Guardrails first
Isolation is a lifecycle, not a checkbox.
- One job, one clean executionNo runner reuse between untrusted jobs.
- Short-lived credentialsSecrets are scoped to one attempt and erased during cleanup.
- Provenanced evidenceControl-plane lifecycle is authoritative; guest diagnostics remain explicitly untrusted.
- Explicit evidence gapsUnavailable, expired, and incomplete data are never implied to exist.
Private pre-alpha
Help validate the first repository.
Design partners can bring a trusted GitHub repository to validate the workflow and bounded evidence model. This is evaluation access, not a production availability claim.