Merged
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
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.
[0.14.1] - 2026-02-27
Fixed
SDK/Server field format mismatches — Fixed three categories of mismatches between the Python SDK client and the protocol server's Pydantic models:
constraintstype mismatch —create_intent(),create_child_intent(), andIntentSpecsentconstraintsas alist[str](e.g.,["rule1", "rule2"]), but the server expectsDict[str, Any](e.g.,{"rules": [...]}). All three methods (sync and async) now accept and senddict[str, Any].Intent.from_dict()retains backward compatibility for legacy list-format constraints.createdBy→created_byfor portfolios —create_portfolio()sentcreatedByandgovernancePolicy(camelCase) but the server'sPortfolioCreatemodel expectscreated_byandgovernance_policy(snake_case). Fixed in both sync and async clients.get_portfolio_intents()response parsing — The server returns a raw JSON array fromGET /api/v1/portfolios/{id}/intents, but the SDK expected a{"intents": [...]}wrapper dict, silently returning an empty list.Silent empty results from list endpoints — Seven additional list-returning methods used
data.get("key", [])which silently returned empty lists when the server sent raw JSON arrays. All now useisinstance(data, list)detection to handle both raw array and wrapped dict responses:list_portfolios()— expected{"portfolios": [...]}get_intent_portfolios()— expected{"portfolios": [...]}get_attachments()— expected{"attachments": [...]}get_costs()— expected{"costs": [], "summary": {}}get_failures()— expected{"failures": [...]}get_subscriptions()— expected{"subscriptions": [...]}federation_list_agents()— expected{"agents": [...]}IntentLease.from_dict()KeyError on server responses —acquire_lease()threwKeyError('status')because the server'sLeaseResponsemodel does not include astatusfield (it usesacquired_at,expires_at, andreleased_atto represent lease state).IntentLease.from_dict()now derives status from these fields:RELEASEDifreleased_atis set,EXPIREDifexpires_atis in the past, otherwiseACTIVE. Also handles the field name differenceacquired_at(server) vscreated_at(SDK). Backward compatible with the SDK's own serialization format.Stale database singleton after server restart —
get_database()cached theDatabaseinstance at module level and never checked whetherdatabase_urlchanged between calls. When the protocol server restarted on a different port (e.g.,openintent_server_8001.db→openintent_server_8002.db), the singleton kept pointing at the old file. Writes went to the old database; reads came from the new (empty) one — intents appeared created but were invisible tolist_intents. The singleton now tracks its URL and recreates the connection when the URL changes.Example and test updates — All examples (
basic_usage.py,openai_multi_agent.py,multi_agent/coordinator.py,compliance_review/coordinator.py) and tests updated to use dict-format constraints.Changed