Architecture
How a GitHub event becomes a sandboxed turn, and what is allowed to decide.
A GitHub event reaches the hosted receiver, which checks access and saves the work before execution. The receiver does not run customer code. Vercel Workflow coordinates the work, and Vercel Sandbox runs the executor.
GitHub App autofeat-agent
|
v
POST https://api.autofeat.app/api/webhook
Vercel receiver -> Python admission checks
|
v
saved work -> Vercel Workflow
|
v
trusted Python control plane
|
v
Vercel Sandbox executor
restricted network access
|
v
check run autofeat/<action>
sticky comment <!-- autofeat:state -->
git ref heads/autofeat-state/pr-<N>The public webhook is POST https://api.autofeat.app/api/webhook. It forwards signed GitHub deliveries to the Python receiver at /api/py/webhook. The Python receiver checks the signature, repository activation and duplicate deliveries before saving admitted work.
Workflow coordinates claims, launch and result collection. The trusted Python control plane owns policy, budgets and access checks. A recovery task at /api/recovery checks unfinished work. Customer execution uses Vercel Sandbox with restricted network access.
The earlier Cloud Run, Pub/Sub and laptop worker path is historical. It is not the current hosted service.
Three control layers
Each layer can only narrow what the layer above already allows.
- Policy file.
.autofeat/config.ymlon the default branch is the ceiling.autofeat exec --configis ignored. The decision snapshot carriespolicy_sha, the default-branch commit that was judged. - Labels.
autofeat:gorequests a turn.autofeat:stopandautofeat:pauserefuse first. Removing a label does not resume a stopped or paused run. See Labels. - Signed directive. A directive in a comment is untrusted input. It is clamped to policy. The portal cannot forge the HMAC. See Security.
Automatic review does not require autofeat:go. It follows the repository's review settings and draft policy, and provides feedback without permission to implement or merge. A review requested from the App can also run without go. Manual label requests still follow policy and budget limits.
Repository access
GitHub App access alone does not enable a repository. The portal records an explicit enable or disable decision. An enabled record must still match the account, installation and repository. Disabled or revoked access blocks new work. The global pause_all switch blocks admission too.
Legacy operator allowlists apply only where no activation record exists and activation cutover is off. They cannot override a disabled or revoked record. With activation cutover on, a repository needs an activation record. See Admin API.
What one turn writes
| Write | Name |
|---|---|
| Check run | autofeat/<action>, for example autofeat/review |
| Sticky comment | marker <!-- autofeat:state --> |
| Journal | git ref heads/autofeat-state/pr-<N> |
A dry run still writes those three. It does not push, review, merge, or add autofeat:ready. The ready label is added only when dry run is off and merge mode is stop_before_merge. See Merge modes.
Policy mode
policy.mode: review_only (the default) allows review, gate, merge, and halt. It forbids plan, implement, and test. policy.mode: full can allow write actions. Doctor warns when full is combined with dry_run: false.
Hosted production selects the simple review engine: one structured model
request over the authorized diff. It does not run repository tests or inspect
the full repository. GitHub CI is separate. The schema retains delegate as
the review method default for other deployment configurations.
Requested implementation and autofix use the admitted OpenAI coding harness. They publish draft children against the original pull request branch. Children need checks and independent reviews; a human integrates them. This flow does not itself grant root approval or merge authority.
Gate, merge, and halt use method native. Method flow and native review are
refused. See Agents and models.