Move back to studio

Author: katmayb

src/docs.json

@@ -190,7 +190,7 @@
                   {
                     "group": "Use in production",
                     "pages": [
-                      "oss/python/langchain/debugger",
+                      "oss/python/langchain/studio",
                       "oss/python/langchain/test",
                       "oss/python/langchain/deploy",
                       "oss/python/langchain/ui",
@@ -228,7 +228,7 @@
                     "group": "Production",
                     "pages": [
                       "oss/python/langgraph/application-structure",
-                      "oss/python/langgraph/debugger",
+                      "oss/python/langgraph/studio",
                       "oss/python/langgraph/test",
                       "oss/python/langgraph/deploy",
                       "oss/python/langgraph/ui",
@@ -912,13 +912,13 @@
                     ]
                   },
                   {
-                    "group": "Debugger",
+                    "group": "studio",
                     "pages": [
-                      "langsmith/debugger",
-                      "langsmith/quick-start-debugger",
-                      "langsmith/use-debugger",
-                      "langsmith/observability-debugger",
-                      "langsmith/troubleshooting-debugger"
+                      "langsmith/studio",
+                      "langsmith/quick-start-studio",
+                      "langsmith/use-studio",
+                      "langsmith/observability-studio",
+                      "langsmith/troubleshooting-studio"
                     ]
                   },
                   {
@@ -1130,7 +1130,7 @@
                   {
                     "group": "Use in production",
                     "pages": [
-                      "oss/javascript/langchain/debugger",
+                      "oss/javascript/langchain/studio",
                       "oss/javascript/langchain/test",
                       "oss/javascript/langchain/deploy",
                       "oss/javascript/langchain/ui",
@@ -1168,7 +1168,7 @@
                     "group": "Production",
                     "pages": [
                       "oss/javascript/langgraph/application-structure",
-                      "oss/javascript/langgraph/debugger",
+                      "oss/javascript/langgraph/studio",
                       "oss/javascript/langgraph/test",
                       "oss/javascript/langgraph/deploy",
                       "oss/javascript/langgraph/ui",
@@ -1845,13 +1845,13 @@
                     ]
                   },
                   {
-                    "group": "Debugger",
+                    "group": "studio",
                     "pages": [
-                      "langsmith/debugger",
-                      "langsmith/quick-start-debugger",
-                      "langsmith/use-debugger",
-                      "langsmith/observability-debugger",
-                      "langsmith/troubleshooting-debugger"
+                      "langsmith/studio",
+                      "langsmith/quick-start-studio",
+                      "langsmith/use-studio",
+                      "langsmith/observability-studio",
+                      "langsmith/troubleshooting-studio"
                     ]
                   },
                   {

src/labs/deep-agents/quickstart.mdx

@@ -65,4 +65,4 @@ const result = await agent.invoke({
 
 </CodeGroup>
 
-The agent created with `createDeepAgent` is a LangGraph graph, so you can interact with it (streaming, human-in-the-loop, memory, the [Debugger](/langsmith/debugger)) the same way you would any LangGraph agent.
+The agent created with `createDeepAgent` is a LangGraph graph, so you can interact with it (streaming, human-in-the-loop, memory, [Studio](/langsmith/studio)) the same way you would any LangGraph agent.

src/langsmith/agent-auth.mdx

@@ -86,7 +86,7 @@ auth_result = await client.authenticate(
 
 During execution, if authentication is required, the SDK will throw an [interrupt](https://langchain-ai.github.io/langgraph/how-tos/human_in_the_loop/add-human-in-the-loop/#pause-using-interrupt). The agent execution pauses and presents the OAuth URL to the user:
 
-![The Debugger interrupt showing OAuth URL](/images/langgraph-auth-interrupt.png)
+![Studio interrupt showing OAuth URL](/images/langgraph-auth-interrupt.png)
 
 After the user completes OAuth authentication and we receive the callback from the provider, they will see the auth success page.
 

src/langsmith/cli.mdx

@@ -387,7 +387,7 @@ The LangGraph CLI requires a JSON configuration file that follows this [schema](
     | `--debug-port INTEGER`        |                  | Port for debugger to listen on                                                      |
     | `--wait-for-client`           | `False`          | Wait for a debugger client to connect to the debug port before starting the server   |
     | `--no-browser`                |                  | Skip automatically opening the browser when the server starts                       |
-    | `--studio-url TEXT`           |                  | URL of the Debugger instance to connect to. Defaults to https://smith.langchain.com |
+    | `--studio-url TEXT`           |                  | URL of the Studio instance to connect to. Defaults to https://smith.langchain.com |
     | `--allow-blocking`            | `False`          | Do not raise errors for synchronous I/O blocking operations in your code (added in `0.2.6`)           |
     | `--tunnel`                    | `False`          | Expose the local server via a public tunnel (Cloudflare) for remote frontend access. This avoids issues with browsers like Safari or networks blocking localhost connections        |
     | `--help`                      |                  | Display command documentation                                                       |
@@ -413,7 +413,7 @@ The LangGraph CLI requires a JSON configuration file that follows this [schema](
     | `--debug-port INTEGER`        |                  | Port for debugger to listen on                                                      |
     | `--wait-for-client`           | `False`          | Wait for a debugger client to connect to the debug port before starting the server   |
     | `--no-browser`                |                  | Skip automatically opening the browser when the server starts                       |
-    | `--studio-url TEXT`           |                  | URL of the Debugger instance to connect to. Defaults to https://smith.langchain.com |
+    | `--studio-url TEXT`           |                  | URL of the Studio instance to connect to. Defaults to https://smith.langchain.com |
     | `--allow-blocking`            | `False`          | Do not raise errors for synchronous I/O blocking operations in your code            |
     | `--tunnel`                    | `False`          | Expose the local server via a public tunnel (Cloudflare) for remote frontend access. This avoids issues with browsers or networks blocking localhost connections        |
     | `--help`                      |                  | Display command documentation                                                       |

src/langsmith/components.mdx

@@ -5,14 +5,20 @@ sidebarTitle: Deployment components
 
 When running the self-hosted [LangSmith with agent deployment](/langsmith/deploy-self-hosted-full-platform), your installation includes several key components. Together these tools and services provide a complete solution for building, deploying, and managing graphs (including agentic applications) in your own infrastructure:
 
-<Frame caption="LangSmith Components with agent/graph deployment">
-  <img src="/langsmith/images/platform-outline.svg" alt="High-level overview of the components in LangSmith when deploying an agent or graph." />
-</Frame>
+```mermaid
+flowchart
+    subgraph LangSmith Deployment
+        A[LangGraph CLI] -->|creates| B(LangGraph Server deployment)
+        B <--> D[Studio]
+        B <--> E[SDKs]
+        B <--> F[RemoteGraph]
+    end
+```
 
 - [LangGraph Server](/langsmith/langgraph-server): Defines an opinionated API and runtime for deploying graphs and agents. Handles execution, state management, and persistence so you can focus on building logic rather than server infrastructure.
 - [LangGraph CLI](/langsmith/cli): A command-line interface to build, package, and interact with graphs locally and prepare them for deployment.
-- The [Debugger](/langsmith/debugger): A specialized IDE for visualization, interaction, and debugging. Connects to a local LangGraph Server for developing and testing your graph.
+- [Studio](/langsmith/studio): A specialized IDE for visualization, interaction, and debugging. Connects to a local LangGraph Server for developing and testing your graph.
 - [Python/JS SDK](/langsmith/sdk): The Python/JS SDK provides a programmatic way to interact with deployed graphs and agents from your applications.
-- [Remote Graph](/langsmith/use-remote-graph): Allows you to interact with a deployed graph as though it were running locally.
-- [LangGraph Control Plane](/langsmith/control-plane): The UI and APIs for creating, updating, and managing LangGraph Server deployments.
+- [RemoteGraph](/langsmith/use-remote-graph): Allows you to interact with a deployed graph as though it were running locally.
+- [Control Plane](/langsmith/control-plane): The UI and APIs for creating, updating, and managing LangGraph Server deployments.
 - [Data plane](/langsmith/data-plane): The runtime layer that executes your graphs, including LangGraph Servers, their backing services (PostgreSQL, Redis, etc.), and the listener that reconciles state from the control plane.

src/langsmith/composite-evaluators.mdx

@@ -92,7 +92,7 @@ oai_client = OpenAI()
 
 examples = [
   {
-    "inputs": {"blog_intro": "Today we’re excited to announce the general availability of LangSmith — our purpose-built infrastructure and management layer for deploying and scaling long-running, stateful agents. Since our beta last June, nearly 400 companies have used LangSmith to deploy their agents into production. Agent deployment is the next hard hurdle for shipping reliable agents, and LangSmith dramatically lowers this barrier with: 1-click deployment to go live in minutes, 30 API endpoints for designing custom user experiences that fit any interaction pattern, Horizontal scaling to handle bursty, long-running traffic, A persistence layer to support memory, conversational history, and async collaboration with human-in-the-loop or multi-agent workflows, Native Debugger, the agent IDE, for easy debugging, visibility, and iteration "},
+    "inputs": {"blog_intro": "Today we’re excited to announce the general availability of LangSmith — our purpose-built infrastructure and management layer for deploying and scaling long-running, stateful agents. Since our beta last June, nearly 400 companies have used LangSmith to deploy their agents into production. Agent deployment is the next hard hurdle for shipping reliable agents, and LangSmith dramatically lowers this barrier with: 1-click deployment to go live in minutes, 30 API endpoints for designing custom user experiences that fit any interaction pattern, Horizontal scaling to handle bursty, long-running traffic, A persistence layer to support memory, conversational history, and async collaboration with human-in-the-loop or multi-agent workflows, Native Studio, the agent IDE, for easy debugging, visibility, and iteration "},
   },
   {
     "inputs": {"blog_intro": "Klarna has reshaped global commerce with its consumer-centric, AI-powered payment and shopping solutions. With over 85 million active users and 2.5 million daily transactions on its platform, Klarna is a fintech leader that simplifies shopping while empowering consumers with smarter, more flexible financial solutions. Klarna’s flagship AI Assistant is revolutionizing the shopping and payments experience. Built on LangGraph and powered by LangSmith, the AI Assistant handles tasks ranging from customer payments, to refunds, to other payment escalations. With 2.5 million conversations to date, the AI Assistant is more than just a chatbot; it’s a transformative agent that performs the work equivalent of 700 full-time staff, delivering results quickly and improving company efficiency."},

src/langsmith/configuration-cloud.mdx

@@ -117,7 +117,7 @@ Inside your deployment, select the "Assistants" tab. This will load a table of a
 
 To create a new assistant, select the "+ New assistant" button. This will open a form where you can specify the graph this assistant is for, as well as provide a name, description, and the desired configuration for the assistant based on the configuration schema for that graph.
 
-To confirm, click "Create assistant". This will take you to [the Debugger](/langsmith/debugger) where you can test the assistant. If you go back to the "Assistants" tab in the deployment, you will see the newly created assistant in the table.
+To confirm, click "Create assistant". This will take you to [Studio](/langsmith/studio) where you can test the assistant. If you go back to the "Assistants" tab in the deployment, you will see the newly created assistant in the table.
 
 ## Use an assistant
 
@@ -225,7 +225,7 @@ Receiving event of type: updates
 
 ### LangSmith UI
 
-Inside your deployment, select the "Assistants" tab. For the assistant you would like to use, click the **Debugger** button. This will open the Debugger with the selected assistant. When you submit an input (either in Graph or Chat mode), the selected assistant and its configuration will be used.
+Inside your deployment, select the "Assistants" tab. For the assistant you would like to use, click the **Studio** button. This will open Studio with the selected assistant. When you submit an input (either in Graph or Chat mode), the selected assistant and its configuration will be used.
 
 ## Create a new version for your assistant
 
@@ -287,7 +287,7 @@ Inside your deployment, select the "Assistants" tab. This will load a table of a
 
 To edit an existing assistant, select the "Edit" button for the specified assistant. This will open a form where you can edit the assistant's name, description, and configuration.
 
-Additionally, if using the Debugger, you can edit the assistants and create new versions via the "Manage Assistants" button.
+Additionally, if using Studio, you can edit the assistants and create new versions via the "Manage Assistants" button.
 
 ## Use a previous assistant version
 
@@ -324,7 +324,7 @@ If you now run your graph and pass in this assistant id, it will use the first v
 
 ### LangSmith UI
 
-If using the Debugger, to set the active version of your assistant, click the "Manage Assistants" button and locate the assistant you would like to use. Select the assistant and the version, and then click the "Active" toggle. This will update the assistant to make the selected version active.
+If using Studio, to set the active version of your assistant, click the "Manage Assistants" button and locate the assistant you would like to use. Select the assistant and the version, and then click the "Active" toggle. This will update the assistant to make the selected version active.
 
 <Warning>
 **Deleting Assistants**

src/langsmith/custom-auth.mdx

@@ -130,9 +130,9 @@ def my_node(state, config):
 Fetch user credentials from a secure secret store. Storing secrets in graph state is not recommended.
 </Note>
 
-### Authorizing a user for the Debugger
+### Authorizing a user for Studio
 
-By default, if you add custom authorization on your resources, this will also apply to interactions made from the [Debugger](/langsmith/debugger). If you want, you can handle logged-in Debugger users differently by checking [is_studio_user()](https://langchain-ai.github.io/langgraph/cloud/reference/sdk/python_sdk_ref/#langgraph_sdk.auth.types.StudioUser).
+By default, if you add custom authorization on your resources, this will also apply to interactions made from [Studio](/langsmith/studio). If you want, you can handle logged-in Studio users differently by checking [is_studio_user()](https://langchain-ai.github.io/langgraph/cloud/reference/sdk/python_sdk_ref/#langgraph_sdk.auth.types.StudioUser).
 
 <Note>
 `is_studio_user` was added in version 0.1.73 of the langgraph-sdk. If you're on an older version, you can still check whether `isinstance(ctx.user, StudioUser)`.

src/langsmith/data-storage-and-privacy.mdx

@@ -2,7 +2,7 @@
 title: Data storage and privacy
 sidebarTitle: Data storage and privacy
 ---
-This document describes how data is processed in the LangGraph CLI and the LangGraph Server for both the in-memory server (`langgraph dev`) and the local Docker server (`langgraph up`). It also describes what data is tracked when interacting with the hosted Debugger frontend.
+This document describes how data is processed in the LangGraph CLI and the LangGraph Server for both the in-memory server (`langgraph dev`) and the local Docker server (`langgraph up`). It also describes what data is tracked when interacting with the hosted Studio frontend.
 
 ## CLI
 
@@ -35,9 +35,9 @@ Additional API calls are made to confirm that the server has a valid license and
 
 If you've disabled [tracing](#langsmith-tracing), no user data is persisted externally unless your graph code explicitly contacts an external service.
 
-## The Debugger
+## Studio
 
-The [Debugger](/langsmith/debugger) is a graphical interface for interacting with your LangGraph server. It does not persist any private data (the data you send to your server is not sent to LangSmith). Though the the Debugger interface is served at [smith.langchain.com](https://smith.langchain.com), it is run in your browser and connects directly to your local LangGraph server so that no data needs to be sent to LangSmith.
+[Studio](/langsmith/studio) is a graphical interface for interacting with your LangGraph server. It does not persist any private data (the data you send to your server is not sent to LangSmith). Though the Studio interface is served at [smith.langchain.com](https://smith.langchain.com), it is run in your browser and connects directly to your local LangGraph server so that no data needs to be sent to LangSmith.
 
 If you are logged in, LangSmith does collect some usage analytics to help improve the debugging user experience. This includes:
 
@@ -46,7 +46,7 @@ If you are logged in, LangSmith does collect some usage analytics to help improv
 * Browser type and version
 * Screen resolution and viewport size
 
-Importantly, no application data or code (or other sensitive configuration details) are collected. All of that is stored in the persistence layer of your LangGraph server. When using the Debugger anonymously, no account creation is required and usage analytics are not collected.
+Importantly, no application data or code (or other sensitive configuration details) are collected. All of that is stored in the persistence layer of your LangGraph server. When using Studio anonymously, no account creation is required and usage analytics are not collected.
 
 ## Quick reference