Merge branch 'main' into migrate-lg

lnhsingh · web-flow · commit 9d28a64c7943 · 2025-08-08T11:44:52.000-04:00
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -0,0 +1,19 @@
+# Owner of the CODEOWNERS
+/.github/CODEOWNERS @lnhsingh
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence, they will be requested for review when someone opens a pull request.
+*       @lnhsingh
+
+# Any file in the `/src/langgraph-platform`
+# and any of its subdirectories.
+/src/langgraph-platform/ @katmayb @lnhsingh
+
+# Any file in the `/src/langsmith`
+# and any of its subdirectories.
+/src/langsmith/ @katmayb @lnhsingh
+
+# Any file in the `/src/oss`
+# and any of its subdirectories.
+/src/oss/ @beklapko @lnhsingh
+
diff --git a/README.md b/README.md
@@ -20,6 +20,10 @@ README.md             # This file
 
 ### Quick Start
 
+#### Install the Mintlify CLI
+
+Install `mint` from https://mintlify.com/docs/installation
+
 #### Setup Virtual Environment (Recommended)
 
 1. **Install uv:**
diff --git a/src/docs.json b/src/docs.json
@@ -17,20 +17,10 @@
     "light": "/images/brand/favicon.svg",
     "dark": "/images/brand/favicon-dark-mode.svg"
   },
-  "navbar": {
-    "links": [
-      {
-        "label": "Forum",
-        "href": "https://forum.langchain.com/"
-      },
-      {
-        "label": "Trust center",
-        "href": "https://trust.langchain.com/"
-      }
-    ]
-  },
   "fonts": {
-    "family": "Manrope"
+    "heading": {
+      "family": "Manrope"
+    }
   },
   "styling": {
       "eyebrows": "breadcrumbs"
@@ -45,16 +35,72 @@
           "icon": "file",
           "href": "https://docs.langchain.com/llms.txt"
         },
-      "chatgpt", 
+      "chatgpt",
       "claude"
-      ]
+    ]
   },
   "integrations": {
     "gtm": {
         "tagId": "GTM-MBBX68ST"
     }
   },
+  "head": [
+    "<link rel=\"stylesheet\" href=\"/style.css\">"
+  ],
+  "footer": {
+    "links": [
+      {
+        "header": "Resources",
+        "items": [
+          {
+            "label": "Trust Center",
+            "href": "https://trust.langchain.com/"
+          },
+          {
+            "label": "Changelog",
+            "href": "https://changelog.langchain.com/"
+          },
+          {
+            "label": "LangChain Academy",
+            "href": "https://academy.langchain.com/"
+          }
+        ]
+      },
+      {
+        "header": "Company",
+        "items": [
+          {
+            "label": "About",
+            "href": "https://langchain.com/about"
+          },
+          {
+            "label": "Careers",
+            "href": "https://langchain.com/careers"
+          },
+          {
+            "label": "Blog",
+            "href": "https://blog.langchain.com/"
+          }
+        ]
+      }
+    ],
+    "socials": {
+      "github": "https://github.com/langchain-ai",
+      "x": "https://x.com/LangChainAI",
+      "linkedin": "https://www.linkedin.com/company/langchain/",
+      "youtube": "https://www.youtube.com/@LangChain"
+    }
+  },
   "navigation": {
+    "global":  {
+    "anchors": [
+      {
+         "anchor": "Forum",
+         "icon": "comments",
+         "href": "https://forum.langchain.com/"
+      }
+    ]
+  },
     "dropdowns": [
       {
         "dropdown": "LangGraph",
@@ -370,8 +416,8 @@
                   }
                 ]
               },
-              { 
-                "group": "LangGraph Studio", 
+              {
+                "group": "LangGraph Studio",
                 "pages": [
                   "langgraph-platform/langgraph-studio",
                   "langgraph-platform/invoke-studio",
@@ -404,7 +450,7 @@
                   "langgraph-platform/deploy-to-cloud",
                   "langgraph-platform/deploy-hybrid",
                   "langgraph-platform/deploy-self-hosted-full-platform",
-                  "langgraph-platform/deploy-data-plane-only",
+                  "langgraph-platform/deploy-standalone-server",
                   "langgraph-platform/use-remote-graph"
                 ]
               },
@@ -427,15 +473,15 @@
             "tab": "Manage",
             "groups": [
 
-              { 
-                "group": "Authentication & access control", 
+              {
+                "group": "Authentication & access control",
                 "pages": [
                   "langgraph-platform/auth",
                   "langgraph-platform/custom-auth",
                   "langgraph-platform/set-up-custom-auth",
                   "langgraph-platform/resource-auth",
                   "langgraph-platform/add-auth-server",
-                  "langgraph-platform/openapi-security"                
+                  "langgraph-platform/openapi-security"
                 ]
               },
               {
@@ -444,21 +490,21 @@
                   "langgraph-platform/scalability-and-resilience"
                 ]
               },
-              { 
+              {
                 "group": "Server customization",
                 "pages": [
                   "langgraph-platform/custom-lifespan",
                   "langgraph-platform/custom-middleware",
                   "langgraph-platform/custom-routes"
-                ] 
+                ]
               },
-              { 
-                "group": "Data management", 
+              {
+                "group": "Data management",
                 "pages": [
                   "langgraph-platform/data-storage-and-privacy",
                   "langgraph-platform/semantic-search",
                   "langgraph-platform/configure-ttl"
-                ] 
+                ]
               },
               {
                 "group": "Tutorials",
diff --git a/src/images/ui-screenshot.png b/src/images/ui-screenshot.png
diff --git a/src/labs/swe/faq.mdx b/src/labs/swe/faq.mdx
@@ -1,13 +1,13 @@
 ---
-title: "FAQ"
-description: "Frequently Asked Questions"
+title: FAQ
+description: Frequently Asked Questions
 ---
 
 <Accordion title="How much does an end to end Open SWE run cost?">
   The cost per run varies greatly based on the complexity of the task, the size of the repository, and the number of files that need to be changed.
 
   For most tasks, you can expect to pay between `$0.50` -> `$3.00` when using Claude Sonnet 4.
-  For the same tasks running on Claude Opus 4, you can expect to pay between `$1.50` -> `$9.00`.
+  For the same tasks running on Claude Opus 4/4.1, you can expect to pay between `$1.50` -> `$9.00`.
 
   Always remember to monitor your runs if you're cost conscious. The most expensive run I've seen Open SWE complete was ~50M Opus 4 tokens, costing `$25.00`.
 </Accordion>
diff --git a/src/labs/swe/index.mdx b/src/labs/swe/index.mdx
@@ -5,11 +5,6 @@ description: "An introduction to Open SWE"
 
 Open SWE is an open-source cloud-based coding agent built with [LangGraph](https://langchain-ai.github.io/langgraphjs/). It's designed to autonomously understand, plan, and execute code changes across entire repositories.
 
-<Note>
-  Open SWE is currently under active development and is not yet ready for
-  production use.
-</Note>
-
 ## How It Works
 
 Open SWE operates through three specialized LangGraph agents:
@@ -20,6 +15,8 @@ Open SWE operates through three specialized LangGraph agents:
 
 The agent can be used through a web interface or triggered automatically via GitHub webhooks, making it flexible for both interactive development and automated workflows.
 
+![Open SWE UI Screenshot](/images/ui-screenshot.png)
+
 <CardGroup cols={2}>
   <Card title="Setup" icon="robot" href="/labs/swe/setup/intro">
     How to set up Open SWE for development
diff --git a/src/labs/swe/setup/development.mdx b/src/labs/swe/setup/development.mdx
@@ -74,7 +74,7 @@ Before starting, ensure you have the following installed:
     GITHUB_APP_REDIRECT_URI="http://localhost:3000/api/auth/github/callback"
 
     # GitHub App details (will be filled after creating GitHub App)
-    GITHUB_APP_NAME="open-swe-dev"
+    GITHUB_APP_NAME="open-swe-dev" # this must match the name of your GitHub app, excluding spaces
     GITHUB_APP_ID=""
     GITHUB_APP_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----
     ...add your private key here...
@@ -105,7 +105,7 @@ Before starting, ensure you have the following installed:
     FIRECRAWL_API_KEY=""  # For URL content extraction
 
     # GitHub App settings (same as web app)
-    GITHUB_APP_NAME="open-swe-dev"
+    GITHUB_APP_NAME="open-swe-dev" # this must match the name of your GitHub app, excluding spaces
     GITHUB_APP_ID=""
     GITHUB_APP_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----
     ...add your private key here...
diff --git a/src/labs/swe/usage/best-practices.mdx b/src/labs/swe/usage/best-practices.mdx
@@ -40,7 +40,7 @@ Submit separate requests for different features or fixes. This allows Open SWE t
 ## Model Selection
 
 - **Claude Sonnet 4 (Default)**: The default model for planning, writing code, and reviewing changes. This model offers the best balance of performance, speed and cost.
-- **Claude Opus 4**: A larger, more powerful model for difficult, or open-ended tasks. Opus 4 is more expensive and slower, but will provide better results for complex tasks.
+- **Claude Opus 4.1**: A larger, more powerful model for difficult, or open-ended tasks. Opus 4.1 is more expensive and slower, but will provide better results for complex tasks.
 
 ### Avoid Other Models
 
@@ -74,8 +74,8 @@ If you're running Open SWE against an open-ended or very complex task, you may w
 
 - `open-swe`: Manual mode with Sonnet 4
 - `open-swe-auto`: Auto mode with Sonnet 4
-- `open-swe-max`: Manual mode with Opus 4
-- `open-swe-max-auto`: Auto mode with Opus 4
+- `open-swe-max`: Manual mode with Opus 4.1
+- `open-swe-max-auto`: Auto mode with Opus 4.1
 
 <Note>
   In development environments, append `-dev` to all labels (e.g.,
diff --git a/src/labs/swe/usage/github.mdx b/src/labs/swe/usage/github.mdx
@@ -33,7 +33,7 @@ Open SWE supports three types of labels that control how the agent operates:
 
 **Max Mode (`open-swe-max` and `open-swe-max-auto`)**
 
-- Uses Claude Opus 4 for both planning and programming tasks
+- Uses Claude Opus 4.1 for both planning and programming tasks
 - Provides enhanced performance and reasoning capabilities for complex problems
 - `open-swe-max`: Requires manual plan approval with premium model performance
 - `open-swe-max-auto`: Combines automatic execution with premium model capabilities
diff --git a/src/langgraph-platform/components.mdx b/src/langgraph-platform/components.mdx
@@ -5,12 +5,12 @@ sidebarTitle: Overview
 
 LangGraph Platform consists of several key components that work together to provide a complete solution for deploying and managing agentic applications:
 
-* [LangGraph Server](/langgraph-platform/langgraph-server): The server defines an opinionated API and architecture that incorporates best practices for deploying agentic applications, allowing you to focus on building your
-* [LangGraph CLI](/langgraph-platform/langgraph-cli): LangGraph CLI is a command-line interface that helps to interact with a local LangGraph
+* [LangGraph Server](/langgraph-platform/langgraph-server): The server defines an opinionated API and architecture that incorporates best practices for deploying agentic applications, allowing you to focus on building your agent logic rather than developing server infrastructure.
+* [LangGraph CLI](/langgraph-platform/langgraph-cli): LangGraph CLI is a command-line interface that helps to interact with a local LangGraph.
 * [LangGraph Studio](/langgraph-platform/langgraph-studio): LangGraph Studio is a specialized IDE that can connect to a LangGraph Server to enable visualization, interaction, and debugging of the application locally.
 * [Python/JS SDK](/langgraph-platform/sdk): The Python/JS SDK provides a programmatic way to interact with deployed LangGraph Applications.
 * [Remote Graph](/langgraph-platform/use-remote-graph): A RemoteGraph allows you to interact with any deployed LangGraph application as though it were running locally.
-* [LangGraph Control Plane](/langgraph-platform/control-plane): The LangGraph Control Plane refers to the Control Plane UI where users create and update LangGraph Servers and the Control Plane APIs that support the UI expe
-* [LangGraph Data Plane](/langgraph-platform/data-plane): The LangGraph Data Plane refers to LangGraph Servers, the corresponding infrastructure for each server, and the "listener" application that continuously polls for u
+* [LangGraph Control Plane](/langgraph-platform/control-plane): The LangGraph Control Plane refers to the Control Plane UI where users create and update LangGraph Servers and the Control Plane APIs that support the UI experience.
+* [LangGraph Data Plane](/langgraph-platform/data-plane): The LangGraph Data Plane refers to LangGraph Servers, the corresponding infrastructure for each server, and the "listener" application that continuously polls for updates from the LangGraph Control Plane.
 
 ![LangGraph components](/langgraph-platform/images/lg-platform.png)
diff --git a/src/langgraph-platform/control-plane.mdx b/src/langgraph-platform/control-plane.mdx
@@ -26,14 +26,24 @@ The Control Plane UI is embedded in [LangSmith](https://docs.smith.langchain.com
 
 This section describes the data model of the control plane API. The API is used to create, update, and delete deployments. See the [control plane API reference](/langgraph-platform/api-ref-control-plane) for more details.
 
-### Deployment
+### Integrations
+
+An integration is an abstraction for a `git` repository provider (e.g. GitHub). It contains all of the required metadata needed to connect with and deploy from a `git` repository.
+
+### Deployments
 
 A deployment is an instance of a LangGraph Server. A single deployment can have many revisions.
 
-### Revision
+### Revisions
 
 A revision is an iteration of a deployment. When a new deployment is created, an initial revision is automatically created. To deploy code changes or update secrets for a deployment, a new revision must be created.
 
+### Listeners
+
+A listener is an instance of a ["listener" application](/langgraph-platform/data-plane#”listener”-application). A listener contains metadata about the application (e.g. version) and metadata about the compute infrastructure where it can deploy to (e.g. Kubernetes namespaces).
+
+The listener data model only applies for [Hybrid](/langgraph-platform/hybrid) and [Self-Hosted](/langgraph-platform/self-hosted) deployments.
+
 ## Control Plane Features
 
 This section describes various features of the control plane.
diff --git a/src/langgraph-platform/deploy-standalone-server.mdx b/src/langgraph-platform/deploy-standalone-server.mdx
@@ -1,8 +1,8 @@
 ---
-title: How to deploy self-hosted data plane only
-sidebarTitle: Deploy self-hosted data plane only
+title: How to deploy self-hosted standalone server
+sidebarTitle: Deploy self-hosted standalone server
 ---
-Before deploying, review the [conceptual guide for the Data Plane Only](/langgraph-platform/self-hosted#data-plane-only) deployment option.
+Before deploying, review the [conceptual guide for the Standalone Server](/langgraph-platform/self-hosted#standalone-server) deployment option.
 
 ## Prerequisites
 
@@ -13,14 +13,14 @@ Before deploying, review the [conceptual guide for the Data Plane Only](/langgra
     <Note>
       **Shared Redis Instance**
       Multiple self-hosted deployments can share the same Redis instance. For example, for `Deployment A`, `REDIS_URI` can be set to `redis://<hostname_1>:<port>/1` and for `Deployment B`, `REDIS_URI` can be set to `redis://<hostname_1>:<port>/2`.
-      
+
       `1` and `2` are different database numbers within the same instance, but `<hostname_1>` is shared. **The same database number cannot be used for separate deployments**.
     </Note>
   2. `DATABASE_URI`: Postgres connection details. Postgres will be used to store assistants, threads, runs, persist thread state and long term memory, and to manage the state of the background task queue with 'exactly once' semantics. The value of `DATABASE_URI` must be a valid [Postgres connection URI](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING-URIS).
     <Note>
       **Shared Postgres Instance**
       Multiple self-hosted deployments can share the same Postgres instance. For example, for `Deployment A`, `DATABASE_URI` can be set to `postgres://<user>:<password>@/<database_name_1>?host=<hostname_1>` and for `Deployment B`, `DATABASE_URI` can be set to `postgres://<user>:<password>@/<database_name_2>?host=<hostname_1>`.
-      
+
       `<database_name_1>` and `database_name_2` are different databases within the same instance, but `<hostname_1>` is shared. **The same database cannot be used for separate deployments**.
     </Note>
   3. `LANGSMITH_API_KEY`: LangSmith API key.
@@ -49,9 +49,9 @@ docker run \
 
 <Note>
   * You need to replace `my-image` with the name of the image you built in the prerequisite steps (from `langgraph build`)
-  
+
   and you should provide appropriate values for `REDIS_URI`, `DATABASE_URI`, and `LANGSMITH_API_KEY`.
-  
+
   * If your application requires additional environment variables, you can pass them in a similar way.
 </Note>
 
diff --git a/src/langgraph-platform/deployment-options.mdx b/src/langgraph-platform/deployment-options.mdx
diff --git a/src/langgraph-platform/langgraph-server-changelog.mdx b/src/langgraph-platform/langgraph-server-changelog.mdx
diff --git a/src/langgraph-platform/self-hosted.mdx b/src/langgraph-platform/self-hosted.mdx
diff --git a/src/style.css b/src/style.css
