Pull requests and delivery

A repository supplies source context. A Project can separately require pull-request delivery for repository-backed Tasks. That requirement follows existing and future Tasks while they have a repository.

Report the pull request before asking for review

An agent working on a pull-request-required task reports its pull request directly to Task Machine. The task shows the source link, current commit, source state, and Task Machine review state. The report also records the required CI result and source mergeability for the exact commit.

A pull request mentioned in a transcript or comment does not become task state. The Agent must explicitly link it to the Task and report each new revision.

When a report moves away from an approved head, Task Machine deactivates readiness, implementer pre-review, and current approval for that revision, while keeping the final approval evidence bound to its exact approved commit. The new head remains unapproved.

If a later fresh report returns the same pull request to that approved commit while it is open, CI is passing, the source says mergeable, and any required source-host review is approved, Task Machine reactivates the approval without asking for another review decision or creating another Inbox item.

Review the exact commit

Review follows the reported commit.

Before submitting a revision, the Agent must:

1. Fetch and rebase onto the latest tip of the pull request's actual base branch.
2. Inspect the repository's instructions, hooks, CI workflows, scripts, and tooling.
3. Determine which checks apply and run the required incremental validation for that exact revision.
4. Follow the repository's validation workflow before checking the source again.

Repository-owned hooks and remote checks run at their defined boundaries. The agent does not duplicate them or claim them as passing without evidence.

A scheduled source recheck inspects required checks, mergeability, the source-host review decision, every review thread and comment, and whether the head still contains the latest base tip. Requested changes, unresolved actionable feedback, a stale base, failed checks, or conflicts return the work to implementation.

The agent addresses the feedback, rebases when needed, repeats the repository's required validation, pushes the new head, and waits for its source checks. It can submit only a feedback-complete head that includes the latest base tip, passes every required CI check, and can merge cleanly.

Human final review follows an implementer pre-review

When an agent implements the task and a human owns the final decision, the implementer first reviews the exact head in a fresh session. Only a passing pre-review sends that same revision to the human's Inbox, where the decision includes the agent's rationale.

If a source recheck replaces that commit, its stale review leaves the active Inbox and Task Activity feeds when the replacement review arrives, so only the current commit asks for a decision. An old notification opens its original persisted item as read-only history, without current data or actions. The replacement remains a separate actionable request. Explicit approvals, requested changes, and dismissals remain in the task history.

If the pre-review finds a gap, the work returns to the implementer without asking for human attention. An assigned agent reviewer remains one fresh review rather than adding a second agent pass.

Supervised and Balanced work requires a human reviewer. Autonomous and Full autonomy can use a human or agent. Workspace owners and admins can use the same Inbox actions when they need to override the assigned human reviewer, and Task Machine records who made that decision.

A later safe report can reactivate an earlier final approval only for the same exact approved commit. It does not restore implementer pre-review evidence or approve a different commit.

Approval continues into delivery

Approval in Task Machine and approval on the source host are separate. Task Machine always requires its own final reviewer approval before an agent may merge an open pull request. When a repository rule additionally requires source-host approval, the agent must report it before the exact head becomes ready for the final Task Machine decision.

Who performs the final review determines the next step:

• Agent reviewer: checks and merges the exact approved revision in the same Run.
• Human reviewer: approval returns the work to the implementer's queue for delivery.

The delivering agent performs the exact-head merge check, merges with its source tool, reports the merged state, writes the completion summary, and closes the task. A temporary source-provider failure can retry delivery for the unchanged approved head without asking for another review.

Work merged outside this sequence

If direct source inspection shows that the canonical linked pull request's exact current source head was already merged outside this sequence, the agent records that head and state, writes the completion summary, and closes the task without asking for retroactive approval.

Changes after approval

A new commit, newly failing required check, or newly reported conflict deactivates readiness and current approval for that revision. A later safe report may reactivate preserved approval only when it returns the same canonical pull request to the exact approved commit and the current source checks are safe.

Any other commit must pass the review sequence before a future merge. Any pending approval explicitly tied to that pull request is also superseded and its Inbox item is skipped, without inferring a decision or creating a replacement request, so the new head must receive a fresh approval.

Task-only approvals, approvals for another pull request, and prior Human decisions remain unchanged.

Agent work whose pull-request gate is active cannot finish while a linked pull request remains open or without a source-confirmed merged current head.

Repository-backed tasks whose Project setting is off use the repository for setup and execution while keeping the ordinary completion-review flow, even when an optional pull request is linked.