Skip to content

Let an Unattended Handoff Run the Strict-Review Pass for a Worker That Cannot Dispatch #2342

Open

Description

@ptr727

Problem

local-strict-review now has the dispatcher own the strict-review pass when a PR-driving worker cannot start a reviewer subagent, as decided on #2318. The worker hands back its worktree, target and digest, the dispatcher runs the reviewer and records the pass in the worker's tree, and the worker pushes once a record matches its content.

unattended-handoff cannot follow that protocol as written:

  • Its orchestrator reads no file, issue, diff, or review, and only dispatches and reads one line back.
  • Its worker brief requires exactly one line from a fixed return table, and that table has no digest-handback line.
  • A reply outside the table ends the run, and a worker is discarded after one round, so nothing can continue it after a record.

So in an unattended run a worker that cannot dispatch still parks the handoff, and no lane pushes.

Options

  1. Add a digest-handback line to the return table. The orchestrator then dispatches the reviewer, has the reviewer run record itself in the worker's tree, and continues the same worker once.
  2. Dispatch unattended workers as an agent type that can start subagents, where the host allows one.
  3. Keep parking, and accept that an unattended run cannot push from a worker that cannot dispatch.

Done When

unattended-handoff states which option applies, and its return table and orchestrator rules agree with local-strict-review.

Activity

  1. added
    enhancementNew feature or request
    decisionA question waiting on the maintainer, alone or beside whatever else the issue carries
    on Oct 4, 2026
  2. ptr727 commented on Oct 4, 2026

    @ptr727
    OwnerAuthor

    Maintainer decision (2026-10-04): option 1. Add a digest-handback line to unattended-handoff's return table. The orchestrator dispatches the reviewer, which runs record itself in the worker's tree, and then continues the same worker once. The issue stays open as the work item.

  3. removed
    decisionA question waiting on the maintainer, alone or beside whatever else the issue carries
    on Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions