Skip to content

applying-a-configuration-turns-act-off - #824

Merged
VeryComplexAndLongName merged 5 commits into
mainfrom
applying-a-configuration-turns-act-off
Oct 6, 2026
Merged

VeryComplexAndLongName merged 5 commits into
mainfrom
applying-a-configuration-turns-act-off

Conversation

@VeryComplexAndLongName

Copy link
Copy Markdown
Owner

applying-a-configuration-turns-act-off

Reported by the owner: applying any named configuration to a change under the supervisor's Act failed with supervisor.mode "act" needs autonomyLevel "autonomous" in the same file. Every named configuration sets Semi-autonomous, applying one keeps the rest of the change's file, and the result broke the Act rule. Rule from the owner: configurations change freely by clear rules; refuse only where truly needed.

  • Core: withoutActItCannotUse (in harness-templates.ts, browser-safe) removes supervisor.mode: "act" where the same file's level is not Autonomous, keeping the fallback agents and allowances; changeTemplateConfigToWrite applies it, so every surface that applies a configuration gets it. actTurnedOff / actTurnedOffNote let surfaces say so in the same words.
  • Harness Settings: saving with a level other than Autonomous turns Act off instead of being refused; the note says so before saving. Applying a configuration in the form says Act is off.
  • Extension and standalone run dialog: the applied note says Act is off.
  • Still refused: a hand-written file that sets both Act and another level — nothing chose between them.

Checks

  • typecheck clean, lint 0 errors; core 2101, core-git-subprocess 67, cli 201, webui 713, server 122, extension 503 passed.
  • openspec validate --strict; merge gate with the absolute worktree path: only 4.3 open (Human-only, for the owner in their workspace).

🤖 Generated with Claude Code

VeryComplexAndLongName and others added 4 commits October 5, 2026 21:54
… Act off instead of failing (applying-a-configuration-turns-act-off)

Reported by the owner: applying any named configuration to a change under
the supervisor's Act failed, since every configuration sets
Semi-autonomous and Act is accepted only under Autonomous. Applying one,
or saving a change's Harness Settings with another level, now removes
supervisor.mode, keeps the fallback agents and allowances, and says so
where it says what was applied or saved. A file written by hand with both
Act and another level is still refused.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ct-off

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…arness Settings (applying-a-configuration-turns-act-off)

Found in the owner's check: the rule that Act needs autonomyLevel
"autonomous" in the same file was part of reading a change's file, so a
file written by hand with both could not even open in its Harness
Settings ("Load failed"), the one place that would put it right. It is
now checked where a change's file is written and where it resolves for a
run - which names both ways out - and not where it is read. The settings
view opens such a file, says Act turns off on saving, and offers Save
with nothing else changed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…checked by the owner)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings in simple-git 4.0.2 (#825), which the dependency audit needs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@VeryComplexAndLongName
VeryComplexAndLongName merged commit b77aa7f into main Oct 6, 2026
10 checks passed
@VeryComplexAndLongName
VeryComplexAndLongName deleted the applying-a-configuration-turns-act-off branch October 6, 2026 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant