When Deep Search sidebar is opened from a repository's root page, the conversation now includes the repository name as context.
Improved ranking of file suggestions in @-mention of the Deep Search sidebar in the blob view. Results from the repository the user is currently browsing are prioritized.
Added shareable URL field to Deep Search API responses
Code intelligence dashboards now allow filtering indexing errors by time range (last 7 days, 30 days, 90 days, last year, or all time).
When the site configuration auth.idpDynamicClientRegistrationEnabled is set to false, existing DCR registered clients and tokens are disabled.
Integrations page now includes "Add to Cursor" and "Add to VS Code" buttons for Sourcegraph MCP.
Site admins can now set up the Slack integration for link unfurling independently of Deep Search, and control whether Deep Search is allowed in Slack via a new "Allow Deep Search" toggle on the Slack integration admin page.
Truncated deep search responses now show a rich preview card automatically via link unfurl, with a single "Send full response to thread" button replacing the previous prompt with two buttons.
Added a user setting to disable the Deep Search Slack integration CTA. This can be set globally for all users under Administration > Global Settings by adding "deepSearch.slackCta.disable": true,
Access tokens now display their last 5 characters in the UI, making it easier to identify which token corresponds to credentials stored in configuration files or environment variables.
Expired access tokens are now visible in the UI and marked as expired, allowing users to identify and delete them for easier token management.
Git notes are now displayed on commit pages and in commit elements throughout the UI. On commit pages, full notes are shown, while other views display a count of notes.
The Enterprise Portal access error page now explains that site admin access on a Sourcegraph instance does not automatically grant access to the Enterprise Portal, and directs users to contact their support engineer. The instance admin dashboard analytics card also clarifies that a separate account linked to the customer's subscription is needed.