Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Pull RequestsArea: what it touches
In DevelopmentKind: in v2.1.284,
What probably matters to youSection of the release
What
PR Steward is described as a Claude agent that can watch a GitHub pull request (PR), fix its automated checks (CI) and merge it. Behind a flag, tengu_federated_flask, Claude Code now avoids working on PRs that Steward is handling. A PR is under Steward when it carries the label claude-pr-steward-watching or claude-pr-steward-is-working.
/autofix-pr, which starts a cloud session to fix a PR, now also reads the PR's labels through gh pr view. If a Steward label is present, it refuses to take the PR on and explains the options: leave it with Steward, make one change and hand back, or take over by removing the label.
/autofix-pr gives the same answer when the server responds pr_steward_owns_binding. In that case, a cloud session that was just started is archived.
The periodic check inside an autofix session is told not to fix or push while those labels are present. Cloud autofix sessions also get extra instructions added to their first message.
A new PR Steward section is added to the /loop skill prompt, to the PR-monitoring prompt ('You're monitoring PR #...') and to one other prompt. It tells Claude to check a PR's labels before pushing to it or watching it. If a Steward label is present, Claude must not push or start a loop, and must offer the same three choices.
In cloud sessions, Claude is told never to remove the label itself.
This site's flag readings for tengu_federated_flask were off for its own account and for the anonymous baseline. None of them were taken under this release.
Why
Two agents pushing to one PR race each other. This keeps Claude and PR Steward from both making changes to the same pull request and leaves the choice of who handles it to you.
Read from
Feature flag
tengu_federated_flaskOff in both readings
The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.284: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's release notes agreeFixed /loop status updates in self-paced mode often not being shown because Claude wrote them only in its reasoning; Claude now writes each…
The name it cites is new in this buildNew in this build: tengu_federated_flask
