Remove defaults and example URLs from adagents.json #335
Conversation
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
The `default` field for $schema wasn't providing functional value (JSON Schema validators don't auto-insert defaults), and the example $schema URLs were pointing to non-existent paths that would drift with versions. Since $schema is optional in adagents.json files, removing these references avoids version maintenance issues without losing any functionality. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add $schema back to examples using relative /schemas/ path - Update build script to transform $schema fields (not just $id/$ref) - This allows examples to be testable while still being version-agnostic in source The build will transform /schemas/adagents.json → /schemas/2.5.0/adagents.json 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
Summary
Alternative fix for #324. Instead of hard-coding
v2URLs that will eventually go stale, this removes the unnecessary$schemareferences entirely:defaultfields from$schemaproperty definitions (JSON Schema validators don't auto-insert defaults, so these weren't functional)$schemafields from all examples (the field is optional in adagents.json files)This avoids version maintenance issues without losing any functionality.
Context
The original issue was that
https://adcontextprotocol.org/schemas/adagents.jsonreturns 404 while/schemas/v2/adagents.jsonworks. The build system transforms$idand$refbut notdefaultvalues or example content.Rather than hard-coding a version that will need updating when v3 releases, we simply remove these non-functional references.
Test plan
🤖 Generated with Claude Code