ExecWarden Docs

Run summary

See one hosted GitHub run with connected compute complete end to end.

Follow the July 24 run summary: seeded bug, selected repo and branch boundary, failing test, patch, two passing tests, PR opened, no merge.

Run Summary

This page summarizes an internal run record from July 24, 2026. An ExecWarden-hosted agent loop with connected execution capacity completed the expected GitHub run: one seeded bug in the demo repo, one selected repo boundary, one agent/* branch boundary, one failing test, one patch, two passing tests, one PR, and no merge.

Repoexecwarden-codex/execwarden-demo-incident-app
Branch boundaryagent/* only
OutcomePatch pushed and PR opened without merging.
Authority shapeThe successful unattended run used scoped Allow grants.

What the Run Demonstrated

GitHub scope

The run stayed inside a selected repo allowlist and a review-branch pattern.

Hosted loop plus compute

ExecWarden kept the hosted session and transcript; customer-configured execution capacity supplied the repository, shell, and test environment.

Recorded evidence

The internal run record included the failing test, the patch, the passing tests, and the PR URL. A sanitized public artifact is still follow-up work.

Limits

The proof did not establish reliable Ask-mode continuation on every surface; that behavior is client-dependent.

Pattern to Reuse

Scope the toolsAllow only the repositories, tools, environments, or API actions the task needs; this can be one repository or several.
Keep merge separateLet the run end in a branch and PR unless you intentionally test merge authority.
Use scoped Allow when you need unattended proofThat is the shape used by the successful hosted example.