Repository navigation
Move Guardian thread context into guardianv2 configuration - #43104
Merged
copyberry[bot] merged 1 commit intoSep 5, 2026
Conversation
## What changed Replace `features.guardian_thread_context` with `features.guardianv2.thread_context` and update the configuration schema. The setting controls thread-owned context for synchronous and asynchronous Guardian, defaults to `false`, and remains independent of `features.guardianv2.enabled`. ## Testing Update configuration tests to cover the nested setting, profile overrides, and enabling thread context while Guardian v2 is disabled. Migrate Guardian approval, history, and async scorer tests to the new configuration key. GitOrigin-RevId: 54a91555eb68001e0adedc8a07bdbc5ea2273f9b
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/54a91555eb68001e0adedc8a07bdbc5ea2273f9b
branch
from
September 5, 2026 21:29
bc30df2 to
e4ce834
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/54a91555eb68001e0adedc8a07bdbc5ea2273f9b
branch
September 5, 2026 21:30
garetjaxor
temporarily deployed
to
issue-triage
September 5, 2026 21:38 — with
GitHub Actions
Inactive
garetjaxor
temporarily deployed
to
issue-triage
September 5, 2026 21:38 — with
GitHub Actions
Inactive
garetjaxor
temporarily deployed
to
issue-triage
September 5, 2026 21:38 — with
GitHub Actions
Inactive
garetjaxor
temporarily deployed
to
issue-triage
September 5, 2026 21:39 — with
GitHub Actions
Inactive
Vulcan-Approach
temporarily deployed
to
issue-triage
September 5, 2026 21:44 — with
GitHub Actions
Inactive
Vulcan-Approach
temporarily deployed
to
issue-triage
September 5, 2026 21:44 — with
GitHub Actions
Inactive
Vulcan-Approach
temporarily deployed
to
issue-triage
September 5, 2026 21:44 — with
GitHub Actions
Inactive
I-AM-PRASHANT-VERMA
temporarily deployed
to
issue-triage
September 5, 2026 21:45 — with
GitHub Actions
Inactive
I-AM-PRASHANT-VERMA
temporarily deployed
to
issue-triage
September 5, 2026 21:45 — with
GitHub Actions
Inactive
I-AM-PRASHANT-VERMA
temporarily deployed
to
issue-triage
September 5, 2026 21:45 — with
GitHub Actions
Inactive
This branch was previously deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Move Guardian thread context into
guardianv2configurationWhat changed
Replace
features.guardian_thread_contextwithfeatures.guardianv2.thread_contextand update the configuration schema. The setting controls thread-owned context for synchronous and asynchronous Guardian, defaults tofalse, and remains independent offeatures.guardianv2.enabled.Testing
Update configuration tests to cover the nested setting, profile overrides, and enabling thread context while Guardian v2 is disabled. Migrate Guardian approval, history, and async scorer tests to the new configuration key.