A non-interactive version of /autofix-pr exists in the build but nothing calls it yet.
A text-only result path for /autofix-pr is fully written but unreachable; the command stays interactive-only.
What's wrong with this entry?
/autofix-pr, which watches your current pull request and fixes problems it finds, gains a second code path that returns a plain text result instead of drawing a UI. Nothing in this build calls it, so the command still behaves exactly as before: interactive only, and only when remote sessions are enabled for your account.
- The new path trims the arguments you pass, runs the same autofix work, and returns text for success and failure, or the fixed string
Autofix PR cancelledwhen the run is stopped. - That text-result shape is what commands usable from print mode return elsewhere in the bundle, which is what suggests a future non-interactive
/autofix-pr. - The command's own description is unchanged and it is still declared as a UI command, without the flag that around 30 other commands set to mark themselves usable outside the interactive session.
- The interactive flow is untouched, including its
Spawning cloud autofix session…andTurning on autofix…steps. - Availability of
/autofix-pritself is unchanged: it needs the remote-sessions capability on your account plus an enterprise or API-key condition.
return { type: "text", value: "Autofix PR cancelled" };
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command