Skip to content

fix: make team creation API fields optional#681

Open
hyoseop1231 wants to merge 1 commit into
iOfficeAI:mainfrom
hyoseop1231:fix/team-create-api-optional-fields
Open

fix: make team creation API fields optional#681
hyoseop1231 wants to merge 1 commit into
iOfficeAI:mainfrom
hyoseop1231:fix/team-create-api-optional-fields

Conversation

@hyoseop1231

Copy link
Copy Markdown

Problem

POST /api/teams returns Invalid JSON request body for any payload where agent objects omit model or assistant_id, and silently rejects backend due to deny_unknown_fields on TeamAgentInputCompat.

Fix (3 changes)

  1. Added backend field to TeamAgentInputCompat
  2. Made model optional with serde(default)
  3. Made assistant_id optional in custom deserializer

- Add missing `backend` field to `TeamAgentInputCompat` (was silently rejected by `deny_unknown_fields`)
- Make `model` optional with `#[serde(default)]`
- Make `assistant_id` optional in custom deserializer (was forced required)

Previously, POST /api/teams required both `model` and `assistant_id`
in every agent object, and silently rejected `backend` due to
`deny_unknown_fields` on the compat struct. This made the API
unusable from external clients that don't know the internal
assistant catalog.

Now clients can create teams with minimal payloads:
{"name":"t","agents":[{"name":"Bot","role":"lead","backend":"claude"}]}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants