Repository navigation
Use upstream's runtime-mode handling with a step-down fallback - #282
Merged
Merged
Conversation
Claude and Codex now report workspace policy through upstream's provider-level supportedRuntimeModes instead of per-model capabilities, so the composer, its new-thread permissions label, RuntimePolicy, and delegated tasks all read the same list. The fork's per-model modes, safe-modes-until-ready rule, CustomModelCapabilities contract, and composer and server copies of the fallback are gone. One delta remains: a mode the provider does not offer steps down to the broadest offered mode below it, as upstream's delegated-task resolver already does, instead of falling to Supervised. This also fixes the new-thread permissions label, which used upstream's resolver while the composer used the fork's. permission-modes.md describes the policy, the step-down, and the new-thread default setting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The fork now uses upstream's runtime-mode handling. One small difference remains: a mode the workspace policy disallows steps down to the next lower allowed mode, where upstream drops to Supervised.
Why: the Fable review of the 67661cf → 6d450a4 sync found that pingdotgg#25869's new-thread permissions label used upstream's resolver while the composer used the fork's. The label could say "Full access" while the run got "Auto-accept edits". Rather than add another seam, this removes the fork's own mode logic.
Changes:
disableAutoModeanddisableBypassPermissionsModepolicy) and Codex (configRequirements/read) report allowed modes through upstream's provider-levelsupportedRuntimeModes. If the policy can't be read, they offer only the safe modes.supportedRuntimeModesandCustomModelCapabilities(contracts and shared go back to upstream);attachSupportedRuntimeModes;resolveComposerRuntimeModesand its safe-modes-until-ready rule;RuntimePolicy.modelRuntimeMode;RuntimePolicyand delegated tasks all read it with upstream's code.runtimeModeConfig.resolveCompatibleRuntimeModeandRuntimePolicy.providerRuntimeModeboth step an unsupported mode down to the broadest offered mode below it, as upstream'sdelegatedTaskModes.resolveRuntimeModealready does. This is the only remaining delta, markedCoder:in both places.docs/user/permission-modes.mddescribes the policy, the step-down, and the new-thread default setting.coder-only.mdis updated.Trade-off: while a provider is still probing, the composer shows all four modes. Once the policy is read, the list and the mode the run gets are correct.
Verification:
pnpm test:coderpasses, except the knownlocalApiload flake (Tests that flake under full-suite load #236), which passes alone.pnpm buildpasses.pnpm knip:check,pnpm test:knip,vp fmt --checkand the unused-locals check pass.🤖 Generated with Claude Code