Skip to content

Remove specific model versions from agentic chat docs #1052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 3, 2025
Merged

Remove specific model versions from agentic chat docs #1052

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/cody/capabilities/agentic-chat.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ Pro users can find the agentic chat option in the LLM selector drop-down.

Enterprise customers must opt-in to access this agentic chat feature (reach out to your account team for access).

For the experimental release, agentic chat is specifically limited to using Claude 3.5 Haiku for the reflection steps and Claude 3.5 Sonnet for the final response to provide a good balance between quality and latency. Therefore, your enterprise instance must have access to both Claude 3.5 Sonnet and Claude 3.5 Haiku to use agentic chat. These models may be changed during the experimental phase to optimize for quality and/or latency.
For the experimental release, agentic chat is specifically limited to using Claude Haiku for the reflection steps and Claude Sonnet for the final response to provide a good balance between quality and latency. Therefore, your enterprise instance must have access to both Claude Sonnet and Claude Haiku to use agentic chat. We use the latest versions of these models, and can fall back to older versions when necessary. These models may be changed during the experimental phase to optimize for quality and/or latency.

Additionally, enterprise users need to upgrade their supported client (VS Code, JetBrains, and Visual Studio) to the latest version of the plugin by enabling the following feature flags on their Sourcegraph Instance:

Expand Down