Conversation
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
mnkiefer
approved these changes
Jan 19, 2026
Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Investigate failed campaign generation run
Fix Claude API rejection of safe_outputs tools with top-level oneOf constraints
Jan 19, 2026
Contributor
|
@copilot add sanity check validation in compiler to ensure the bug is not reoccurring |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
Added |
pelikhan
approved these changes
Jan 19, 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.
Campaign generation workflow failed with Claude API error:
input_schema does not support oneOf, allOf, or anyOf at the top level. Two MCP tools (assign_to_agent,update_project) used top-leveloneOffor conditional field requirements.Changes
Removed top-level
oneOfconstraints from tool schemas:assign_to_agent: RemovedoneOfrequiring eitherissue_numberorpull_number. Both fields now optional; validation documented in descriptions.update_project: RemovedoneOffor conditional requirements based oncontent_type. Required fields simplified to["project", "content_type"]; conditional requirements documented in field descriptions.Added regression test:
TestNoTopLevelOneOfAllOfAnyOfinpkg/workflow/safe_outputs_tools_schema_test.govalidates that all 31 safe output tools comply with the constraint. Test acts as a compiler sanity check to prevent this bug from reoccurring.Before:
{ "name": "assign_to_agent", "inputSchema": { "properties": { "issue_number": {"type": ["number", "string"]}, "pull_number": {"type": ["number", "string"]} }, "oneOf": [ {"required": ["issue_number"]}, {"required": ["pull_number"]} ] } }After:
{ "name": "assign_to_agent", "inputSchema": { "properties": { "issue_number": { "type": ["number", "string"], "description": "... Either issue_number or pull_number must be provided, but not both." }, "pull_number": { "type": ["number", "string"], "description": "... Either issue_number or pull_number must be provided, but not both." } } } }Updated both
pkg/workflow/js/safe_outputs_tools.jsonandactions/setup/js/safe_outputs_tools.json. Runtime validation handles constraints previously enforced by schema.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.