# Insights moves to the Context app, and the Studio plugin is deprecated

**Version:** v2.0.0

**Published:** September 3, 2026

@sanity/context 2.0 completes the move to the Context app in the Sanity Dashboard: Insights and configuration for new setups now live there. Existing Sanity Context documents remain editable in Studio, and conversations you've already recorded have been migrated to your organization's Context store.

## The Studio plugin is deprecated

The plugin still registers the Sanity Context document type, so existing MCP context documents remain editable in Studio—now with a notice pointing at the [migration guide](https://www.sanity.io/docs/ai/context-migration-guide). New setups create an MCP endpoint in the Context app instead. The plugin also works with both @sanity/ui v3 and v4, and no longer requires @sanity/icons, styled-components, @sanity/color, react-rx, or rxjs as peer dependencies.

## Insights lives in the Context app

Conversations are stored in your organization's Context store through `client.context`, and the Insights dashboard has moved from Studio to the Context app. Classification runs on your side with your own AI SDK model. `classifyConversations` handles fetching, batching, and error handling in one call. A new sharing option on the telemetry integration lets you opt in to sharing metrics or full transcripts with Sanity to help improve Context.

## Breaking changes

- Requires @sanity/client ^8.4.0 as a peer dependency, which comes with sanity 6.12 or later.
- sanityInsightsIntegration now takes an organization-scoped client (context: {organizationId}) and tags conversations with metadata.mcpEndpoints instead of agentId.
- saveConversation and generateConversationId are removed — save transcripts with client.context.conversations.save.
- The conversation document type is no longer registered in Studio; conversations live in the Context store.

Migrating takes a few minutes: re-create your MCP configuration as an endpoint in the Context app, then point your agent at the new URL with an organization-level API token. The [migration guide](https://www.sanity.io/docs/ai/context-migration-guide) has the step-by-step instructions.