Repository navigation
Add an opt-in model catalog to multi-agent context - #49560
Merged
copyberry[bot] merged 1 commit intoSep 30, 2026
Merged
copyberry[bot] merged 1 commit into
copyberry[bot] merged 1 commit into
Conversation
## Why Refreshing available model descriptions changes the `spawn_agent` tool schema. Keep model choices current while preserving tool definitions and earlier conversation input. ## What changed - Add the disabled-by-default `model_catalog_in_context` feature for multi-agent V1 and V2. When enabled and model overrides are available, move model listings from tool descriptions into developer `<model_catalog>` messages. - Include picker-visible, compatible models with descriptions, reasoning efforts, and service tiers in a listing bounded to 1,000 bytes. Point `spawn_agent` guidance to the latest catalog. - Append updated listings only when their rendered content changes, restore missing listings, and invalidate retained catalogs when they no longer apply. ## Testing Extend integration coverage for V1 and V2 with the feature enabled and disabled. Verify that catalog refreshes preserve tool definitions and prior input when enabled, append the updated listing once, and retain the existing tool-description behavior when disabled. Add a request-history snapshot for the V1 opt-in path. GitOrigin-RevId: 67b11b4ad6c35f00d0e29edf6343bb0b4804d797
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/67b11b4ad6c35f00d0e29edf6343bb0b4804d797
branch
from
September 30, 2026 10:03
7179855 to
2e5fea6
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/67b11b4ad6c35f00d0e29edf6343bb0b4804d797
branch
September 30, 2026 10:03
This branch was successfully 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.
4 participants
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.
Add an opt-in model catalog to multi-agent context
Why
Refreshing available model descriptions changes the
spawn_agenttool schema. Keep model choices current while preserving tool definitions and earlier conversation input.What changed
model_catalog_in_contextfeature for multi-agent V1 and V2. When enabled and model overrides are available, move model listings from tool descriptions into developer<model_catalog>messages.spawn_agentguidance to the latest catalog.Testing
Extend integration coverage for V1 and V2 with the feature enabled and disabled. Verify that catalog refreshes preserve tool definitions and prior input when enabled, append the updated listing once, and retain the existing tool-description behavior when disabled. Add a request-history snapshot for the V1 opt-in path.