You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several significant assistant features shipped in the last 2 months that are not yet reflected in the docs. This ticket covers the UI-visible changes that end users and org admins need to know about.
Assistants are now created manually via a unified API instead of being auto-created. Update any docs that imply assistants are automatically provisioned. The creation form requires the user to explicitly fill in model and configuration fields.
The model selection dropdown in the Create Assistant form now shows a fixed list of supported models instead of fetching them from the backend. Docs should note that only limited models are supported.
Background
Several significant assistant features shipped in the last 2 months that are not yet reflected in the docs. This ticket covers the UI-visible changes that end users and org admins need to know about.
Changes to Document
Assistants are now created manually via a unified API instead of being auto-created. Update any docs that imply assistants are automatically provisioned. The creation form requires the user to explicitly fill in model and configuration fields.
The model selection dropdown in the Create Assistant form now shows a fixed list of supported models instead of fetching them from the backend. Docs should note that only limited models are supported.
The assistant listing page now shows a status chip for each assistant. Possible statuses to document:
Uploading files to an assistant's knowledge base now has improved behavior. Document:
Users can now clone an existing assistant. Document:
References (PRs)