From 315b1e957d985ee314679ba0c9b4c38ee780f90e Mon Sep 17 00:00:00 2001
From: Jay Sabva <94957904+JaySabva@users.noreply.github.com>
Date: Sat, 6 Dec 2025 23:47:18 +0530
Subject: [PATCH] docs: fix documentation of rmcp client flag (#7665)

## Summary
- Updated the rmcp client flag's documentation in config.md file
- changed it from `experimental_use_rmcp_client` to `rmcp_client`
---
 docs/config.md | 16 +++-------------
 1 file changed, 3 insertions(+), 13 deletions(-)

diff --git a/docs/config.md b/docs/config.md
index 3b06d7301..0ba711f02 100644
--- a/docs/config.md
+++ b/docs/config.md
@@ -464,10 +464,11 @@ http_headers = { "HEADER_NAME" = "HEADER_VALUE" }
 env_http_headers = { "HEADER_NAME" = "ENV_VAR" }
 ```
 
-Streamable HTTP connections always use the experimental Rust MCP client under the hood, so expect occasional rough edges. OAuth login flows are gated on the `experimental_use_rmcp_client = true` flag:
+Streamable HTTP connections always use the experimental Rust MCP client under the hood, so expect occasional rough edges. OAuth login flows are gated on the `rmcp_client = true` flag:
 
 ```toml
-experimental_use_rmcp_client = true
+[features]
+rmcp_client = true
 ```
 
 After enabling it, run `codex mcp login <server-name>` when the server supports OAuth.
@@ -489,17 +490,6 @@ disabled_tools = ["search"]
 
 When both `enabled_tools` and `disabled_tools` are specified, Codex first restricts the server to the allow-list and then removes any tools that appear in the deny-list.
 
-#### Experimental RMCP client
-
-This flag enables OAuth support for streamable HTTP servers.
-
-```toml
-experimental_use_rmcp_client = true
-
-[mcp_servers.server_name]
-…
-```
-
 #### MCP CLI commands
 
 ```shell