docs: explain when AI agent threads become read-only#668
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Adds a section to the AI agents user guide explaining the cases in which the chat input is disabled on an existing thread.
Changes
Context
Upstream change adds a third disabled state for the chat input: when the model originally used in a thread is no longer offered by the agent, the input is disabled and surfaces a message asking the user to start a new thread. The existing docs only implicitly covered the Slack and other-user cases, so this consolidates all three into a single user-facing section.