Uh oh!
There was an error while loading. Please reload this page.
feat: update to unstable schema and metadata - #42
Conversation
Signed-off-by: Frost Ming <me@frostming.com>
PsiACE
commented
Nov 24, 2025
My main concern now is the compatibility boundary between the stable and unstable parts of the schema, and whether we should reflect that separation explicitly in the Python SDK. |
frostming
commented
Nov 24, 2025
In fact, we have no restrictions on the protocol side; Agent and Client developers are free to define any methods they like, whether legal or illegal. And I only added a guard in the caller site(router). |
PsiACE
commented
Nov 25, 2025
Schema version 0.7.0 has just been released https://github.com/agentclientprotocol/agent-client-protocol/releases/tag/v0.7.0 . We may need to generate and debug the new schema on this PR. |
Signed-off-by: Frost Ming <me@frostming.com>
Complete. Also added a flag to enable the use of unstable protocol(disabled by default). |
Uh oh!
There was an error while loading. Please reload this page.
* feat: update to unstable schema and metadata Signed-off-by: Frost Ming <me@frostming.com> * feat: adapt to the 0.7.0 schema Signed-off-by: Frost Ming <me@frostming.com> --------- Signed-off-by: Frost Ming <me@frostming.com>
Signed-off-by: Frost Ming me@frostming.com
Summary
This PR integrates the change of unstable schema and metadata.
the refs/main tag will be updated once the upstream release is tagged.
Related issues
Testing
Docs & screenshots
Checklist
feat:,fix:).make gen-all) are called out if applicable.