接线 · MCP 把上下文接进来Wire In · MCP Brings Your Context In.
你的上下文大半不在仓库里 —— 在 Figma 的稿、Sentry 的报错、Linear 的工单、文档站的页面里。MCP 有两个方向:Codex 作 client 时用 codex mcp add 接 STDIO 或 Streamable HTTP 服务器;Codex 作 server 时用 codex mcp-server 通过 STDIO 让别的 agent 委派编码活。客户端一侧还有更细的闸门:服务器白名单、危险工具禁用、逐工具审批。这一章也算一笔多数教程不算的账:每接一个服务器,它的工具清单都要占上下文。Most of your context isn't in the repo — it's in a Figma file, a Sentry error, a Linear ticket, a docs page. MCP runs in two directions: as a client, Codex uses codex mcp add to connect STDIO or Streamable HTTP servers; as a server, codex mcp-server exposes Codex over STDIO so another agent can delegate coding work. The client side also has finer gates: server allowlists, dangerous-tool disabling, and per-tool approvals. This chapter counts a bill most tutorials skip too: every connected server's tool list occupies context.
你的上下文大半不在仓库里 —— 需求在 Linear 的工单,报错在 Sentry,设计稿在 Figma,文档在别的站点。于是你的日常变成搬运:开网页、复制、粘进对话、再解释一遍这是什么。MCP 把搬运换成接线:Codex 既能作 client 读 / 调别的服务器,也能用 codex mcp-server 作 server,让别的 agent 把编码活委派进来。这一章讲两种方向、闸门怎么收紧,以及一条更要紧的线 —— 每接一个,它的读写半径和你的额度都大一圈。Most of your context isn't in the repo — requirements in a Linear ticket, errors in Sentry, designs in Figma, docs on another site. So your day becomes haulage: open the page, copy, paste into chat, explain what it is. MCP replaces hauling with wiring: Codex can act as a client reading / calling other servers, or as a server through codex mcp-server so another agent delegates coding work to it. This chapter covers both directions, how to tighten the gates, and a line that matters more — every hookup widens both its read-write radius and your quota bill.
— I
作为 client:一条命令,两种 transportAs a Client: One Command, Two Transports.
MCP(Model Context Protocol)是把模型接到工具与上下文的开放协议 —— 第三方文档、浏览器、Figma 都能接进来。1注 1Note 1OpenAI Codex 文档 · Model Context Protocol —— MCP 把模型接到工具与上下文,让 ChatGPT 或 Codex 用上第三方文档、浏览器、Figma 等。Codex 把 MCP 配置存在 config.toml([mcp_servers.名字]),CLI / IDE / 桌面应用共用同一份。加服务器:codex mcp add …(STDIO 本地进程,或 Streamable HTTP 远程地址,支持 Bearer / OAuth);codex mcp list 看已配、codex mcp login 走 OAuth;TUI 里 /mcp 看在连的服务器。每服务器可配 enabled_tools 白名单、disabled_tools 黑名单、default_tools_approval_mode(auto / prompt / writes / approve)与按工具的 approval_mode。文档举的常用服务器:OpenAI Docs、Context7、Figma、Playwright、Sentry、GitHub。截至 2026-08-05。OpenAI Codex Docs · Model Context Protocol — MCP connects models to tools and context, giving ChatGPT or Codex third-party docs, a browser, Figma, and more. Codex stores MCP config in config.toml ([mcp_servers.name]), shared by the CLI / IDE / desktop app. Add a server: codex mcp add … (STDIO local process, or Streamable HTTP remote address, with Bearer / OAuth); codex mcp list shows configured servers, codex mcp login runs OAuth; /mcp in the TUI shows connected servers. Per server you can set an enabled_tools allowlist, a disabled_tools denylist, default_tools_approval_mode (auto / prompt / writes / approve), and per-tool approval_mode. Common servers the docs cite: OpenAI Docs, Context7, Figma, Playwright, Sentry, GitHub. As of 2026-08-05.Codex 把配置存在 config.toml 里:同一台机器上的 CLI、IDE、桌面应用共用一份 MCP 配置;云端不会读这份本地文件。接入一条命令,分两种 transport:本地进程走 STDIO,远程服务走 Streamable HTTP(支持 Bearer token 或 OAuth):MCP (Model Context Protocol) is the open protocol connecting models to tools and context — third-party docs, a browser, Figma all wire in.1注 1Note 1OpenAI Codex 文档 · Model Context Protocol —— MCP 把模型接到工具与上下文,让 ChatGPT 或 Codex 用上第三方文档、浏览器、Figma 等。Codex 把 MCP 配置存在 config.toml([mcp_servers.名字]),CLI / IDE / 桌面应用共用同一份。加服务器:codex mcp add …(STDIO 本地进程,或 Streamable HTTP 远程地址,支持 Bearer / OAuth);codex mcp list 看已配、codex mcp login 走 OAuth;TUI 里 /mcp 看在连的服务器。每服务器可配 enabled_tools 白名单、disabled_tools 黑名单、default_tools_approval_mode(auto / prompt / writes / approve)与按工具的 approval_mode。文档举的常用服务器:OpenAI Docs、Context7、Figma、Playwright、Sentry、GitHub。截至 2026-08-05。OpenAI Codex Docs · Model Context Protocol — MCP connects models to tools and context, giving ChatGPT or Codex third-party docs, a browser, Figma, and more. Codex stores MCP config in config.toml ([mcp_servers.name]), shared by the CLI / IDE / desktop app. Add a server: codex mcp add … (STDIO local process, or Streamable HTTP remote address, with Bearer / OAuth); codex mcp list shows configured servers, codex mcp login runs OAuth; /mcp in the TUI shows connected servers. Per server you can set an enabled_tools allowlist, a disabled_tools denylist, default_tools_approval_mode (auto / prompt / writes / approve), and per-tool approval_mode. Common servers the docs cite: OpenAI Docs, Context7, Figma, Playwright, Sentry, GitHub. As of 2026-08-05. Codex stores the config in config.toml: the CLI, IDE, and desktop app on the same host share one MCP configuration; cloud does not read this local file. Connecting is one command in two transports: local processes over STDIO, remote services over Streamable HTTP (with Bearer token or OAuth):
加一个本地服务器,或直接写 config.toml;/mcp 看连接Add a local server, or write config.toml directly; /mcp shows connections
远程服务器直接写进 config.toml 更省事,一个 [mcp_servers.名字] 表配好 URL 和认证:Remote servers are easier written straight into config.toml, one [mcp_servers.name] table with the URL and auth:
一个远程 HTTP 服务器,带按工具的审批档A remote HTTP server, with a per-tool approval mode
文档自己举的常用服务器就那几个,覆盖多数人的搬运:OpenAI Docs(查官方文档)、Context7(查最新的第三方库文档)、Figma、Playwright、Sentry、GitHub。1注 1Note 1OpenAI Codex 文档 · Model Context Protocol —— MCP 把模型接到工具与上下文,让 ChatGPT 或 Codex 用上第三方文档、浏览器、Figma 等。Codex 把 MCP 配置存在 config.toml([mcp_servers.名字]),CLI / IDE / 桌面应用共用同一份。加服务器:codex mcp add …(STDIO 本地进程,或 Streamable HTTP 远程地址,支持 Bearer / OAuth);codex mcp list 看已配、codex mcp login 走 OAuth;TUI 里 /mcp 看在连的服务器。每服务器可配 enabled_tools 白名单、disabled_tools 黑名单、default_tools_approval_mode(auto / prompt / writes / approve)与按工具的 approval_mode。文档举的常用服务器:OpenAI Docs、Context7、Figma、Playwright、Sentry、GitHub。截至 2026-08-05。OpenAI Codex Docs · Model Context Protocol — MCP connects models to tools and context, giving ChatGPT or Codex third-party docs, a browser, Figma, and more. Codex stores MCP config in config.toml ([mcp_servers.name]), shared by the CLI / IDE / desktop app. Add a server: codex mcp add … (STDIO local process, or Streamable HTTP remote address, with Bearer / OAuth); codex mcp list shows configured servers, codex mcp login runs OAuth; /mcp in the TUI shows connected servers. Per server you can set an enabled_tools allowlist, a disabled_tools denylist, default_tools_approval_mode (auto / prompt / writes / approve), and per-tool approval_mode. Common servers the docs cite: OpenAI Docs, Context7, Figma, Playwright, Sentry, GitHub. As of 2026-08-05.TUI 里 /mcp 随时看哪些在连着。The common servers the docs themselves cite are just a handful, covering most people's haulage: OpenAI Docs (official docs), Context7 (up-to-date third-party library docs), Figma, Playwright, Sentry, GitHub.1注 1Note 1OpenAI Codex 文档 · Model Context Protocol —— MCP 把模型接到工具与上下文,让 ChatGPT 或 Codex 用上第三方文档、浏览器、Figma 等。Codex 把 MCP 配置存在 config.toml([mcp_servers.名字]),CLI / IDE / 桌面应用共用同一份。加服务器:codex mcp add …(STDIO 本地进程,或 Streamable HTTP 远程地址,支持 Bearer / OAuth);codex mcp list 看已配、codex mcp login 走 OAuth;TUI 里 /mcp 看在连的服务器。每服务器可配 enabled_tools 白名单、disabled_tools 黑名单、default_tools_approval_mode(auto / prompt / writes / approve)与按工具的 approval_mode。文档举的常用服务器:OpenAI Docs、Context7、Figma、Playwright、Sentry、GitHub。截至 2026-08-05。OpenAI Codex Docs · Model Context Protocol — MCP connects models to tools and context, giving ChatGPT or Codex third-party docs, a browser, Figma, and more. Codex stores MCP config in config.toml ([mcp_servers.name]), shared by the CLI / IDE / desktop app. Add a server: codex mcp add … (STDIO local process, or Streamable HTTP remote address, with Bearer / OAuth); codex mcp list shows configured servers, codex mcp login runs OAuth; /mcp in the TUI shows connected servers. Per server you can set an enabled_tools allowlist, a disabled_tools denylist, default_tools_approval_mode (auto / prompt / writes / approve), and per-tool approval_mode. Common servers the docs cite: OpenAI Docs, Context7, Figma, Playwright, Sentry, GitHub. As of 2026-08-05./mcp in the TUI shows what's connected anytime.
— II
作为 server:把 Codex 接给别的 agentAs a Server: Wire Codex into Another Agent.
MCP 还有反方向:不是 Codex 去调工具,而是把 Codex 自己作为 MCP server,交给另一个 client / agent 调。命令不是管理配置的 codex mcp,而是多一个后缀的 codex mcp-server;它只走 STDIO。4注 4Note 4OpenAI Codex 文档 · Run Codex as an MCP server —— 服务端入口是 codex mcp-server(不是管理客户端配置的 codex mcp),通过 STDIO 提供 Codex。它暴露两个工具:codex 启动一场新对话并在 structuredContent.threadId 返回线程 ID;codex-reply 用 threadId 继续同一场。conversationId 只是弃用兼容别名。适合让另一个 MCP client / agent 把编码工作委派给 Codex。截至 2026-08-05。OpenAI Codex Docs · Run Codex as an MCP server — the server entry point is codex mcp-server (not codex mcp, which manages client configuration), exposing Codex over STDIO. It offers two tools: codex starts a new conversation and returns the thread ID in structuredContent.threadId; codex-reply continues it with threadId. conversationId is only a deprecated compatibility alias. This lets another MCP client / agent delegate coding work to Codex. As of 2026-08-05.服务端暴露两个工具:codex 起一场新对话,从 structuredContent.threadId 取回线程 ID;codex-reply 拿这个 threadId 继续。旧的 conversationId 只剩弃用兼容。这样上层 agent 能把「到这个仓库里实现并验证一项改动」委派给 Codex,再沿同一线程追问。MCP also runs in the opposite direction: instead of Codex calling tools, Codex itself becomes an MCP server for another client / agent. The command isn't codex mcp, which manages client configuration, but the suffixed codex mcp-server; it uses STDIO only.4注 4Note 4OpenAI Codex 文档 · Run Codex as an MCP server —— 服务端入口是 codex mcp-server(不是管理客户端配置的 codex mcp),通过 STDIO 提供 Codex。它暴露两个工具:codex 启动一场新对话并在 structuredContent.threadId 返回线程 ID;codex-reply 用 threadId 继续同一场。conversationId 只是弃用兼容别名。适合让另一个 MCP client / agent 把编码工作委派给 Codex。截至 2026-08-05。OpenAI Codex Docs · Run Codex as an MCP server — the server entry point is codex mcp-server (not codex mcp, which manages client configuration), exposing Codex over STDIO. It offers two tools: codex starts a new conversation and returns the thread ID in structuredContent.threadId; codex-reply continues it with threadId. conversationId is only a deprecated compatibility alias. This lets another MCP client / agent delegate coding work to Codex. As of 2026-08-05. The server exposes two tools: codex starts a new conversation and returns the thread ID in structuredContent.threadId; codex-reply continues that threadId. The old conversationId remains only as a deprecated alias. An orchestrating agent can delegate 'implement and verify this change in the repo' to Codex, then follow up in the same thread.
codex mcp-server
启动 Codex 的 MCP server —— STDIO 由上层 client 接管Start Codex's MCP server — the parent client owns its STDIO
— III
比「接不接」更细的闸门Gates Finer Than Connect-or-Not.
接一个服务器不是「全接或全不接」。Codex 给了按服务器、按工具的闸门:enabled_tools 只放行你要的那几个工具,disabled_tools 关掉危险的,default_tools_approval_mode 定这台服务器的默认审批档(auto 自动、prompt 每次问、writes 只对非只读工具问、approve 全要批),还能对单个工具再单独定 approval_mode。1注 1Note 1OpenAI Codex 文档 · Model Context Protocol —— MCP 把模型接到工具与上下文,让 ChatGPT 或 Codex 用上第三方文档、浏览器、Figma 等。Codex 把 MCP 配置存在 config.toml([mcp_servers.名字]),CLI / IDE / 桌面应用共用同一份。加服务器:codex mcp add …(STDIO 本地进程,或 Streamable HTTP 远程地址,支持 Bearer / OAuth);codex mcp list 看已配、codex mcp login 走 OAuth;TUI 里 /mcp 看在连的服务器。每服务器可配 enabled_tools 白名单、disabled_tools 黑名单、default_tools_approval_mode(auto / prompt / writes / approve)与按工具的 approval_mode。文档举的常用服务器:OpenAI Docs、Context7、Figma、Playwright、Sentry、GitHub。截至 2026-08-05。OpenAI Codex Docs · Model Context Protocol — MCP connects models to tools and context, giving ChatGPT or Codex third-party docs, a browser, Figma, and more. Codex stores MCP config in config.toml ([mcp_servers.name]), shared by the CLI / IDE / desktop app. Add a server: codex mcp add … (STDIO local process, or Streamable HTTP remote address, with Bearer / OAuth); codex mcp list shows configured servers, codex mcp login runs OAuth; /mcp in the TUI shows connected servers. Per server you can set an enabled_tools allowlist, a disabled_tools denylist, default_tools_approval_mode (auto / prompt / writes / approve), and per-tool approval_mode. Common servers the docs cite: OpenAI Docs, Context7, Figma, Playwright, Sentry, GitHub. As of 2026-08-05.也就是说,你可以接一个能查也能改的服务器,但只放行「查」,把「改」单独设成必须弹窗。Connecting a server isn't 'all or nothing.' Codex offers per-server, per-tool gates: enabled_tools allows only the tools you want, disabled_tools turns off the dangerous ones, default_tools_approval_mode sets that server's default approval (auto, prompt to ask each time, writes to ask only for non-read-only tools, approve for everything), and a single tool can override its approval_mode.1注 1Note 1OpenAI Codex 文档 · Model Context Protocol —— MCP 把模型接到工具与上下文,让 ChatGPT 或 Codex 用上第三方文档、浏览器、Figma 等。Codex 把 MCP 配置存在 config.toml([mcp_servers.名字]),CLI / IDE / 桌面应用共用同一份。加服务器:codex mcp add …(STDIO 本地进程,或 Streamable HTTP 远程地址,支持 Bearer / OAuth);codex mcp list 看已配、codex mcp login 走 OAuth;TUI 里 /mcp 看在连的服务器。每服务器可配 enabled_tools 白名单、disabled_tools 黑名单、default_tools_approval_mode(auto / prompt / writes / approve)与按工具的 approval_mode。文档举的常用服务器:OpenAI Docs、Context7、Figma、Playwright、Sentry、GitHub。截至 2026-08-05。OpenAI Codex Docs · Model Context Protocol — MCP connects models to tools and context, giving ChatGPT or Codex third-party docs, a browser, Figma, and more. Codex stores MCP config in config.toml ([mcp_servers.name]), shared by the CLI / IDE / desktop app. Add a server: codex mcp add … (STDIO local process, or Streamable HTTP remote address, with Bearer / OAuth); codex mcp list shows configured servers, codex mcp login runs OAuth; /mcp in the TUI shows connected servers. Per server you can set an enabled_tools allowlist, a disabled_tools denylist, default_tools_approval_mode (auto / prompt / writes / approve), and per-tool approval_mode. Common servers the docs cite: OpenAI Docs, Context7, Figma, Playwright, Sentry, GitHub. As of 2026-08-05. Which means you can wire in a server that both reads and writes, but allow only 'read' and make 'write' individually prompt.还有一条 Codex 替你兜底的硬规矩:标了破坏性注解的 app / MCP 工具调用永远要审批 —— 即便那个工具同时声称自己只读,只要它宣告了破坏性,Codex 就一定停下问你。2注 2Note 2OpenAI Codex 文档 · Agent approvals & security —— Codex 也会为宣告有副作用的 app(连接器)工具调用征求审批;标了破坏性注解的 app / MCP 工具调用永远要审批,即便它同时标了只读等其它提示。默认 agent 断网;会抓取外部内容的场景可能带来 prompt injection —— 它替你读回的网页或工单里,可能藏着写给模型看的指令。截至 2026-08-05。OpenAI Codex Docs · Agent approvals & security — Codex also elicits approval for app (connector) tool calls that advertise side effects; app / MCP tool calls marked with a destructive annotation always require approval, even if they also advertise other hints like read-only. By default the agent has no network; fetching external content can expose you to prompt injection — the page or ticket it reads back may hide instructions written for the model. As of 2026-08-05.这是「能接但别失控」的最后一格:再松的档,也拦不住的那类动作,由协议层替你按住。And one hard rule Codex backstops for you: app / MCP tool calls marked with a destructive annotation always require approval — even if that tool also claims to be read-only, once it advertises destructiveness, Codex stops and asks.2注 2Note 2OpenAI Codex 文档 · Agent approvals & security —— Codex 也会为宣告有副作用的 app(连接器)工具调用征求审批;标了破坏性注解的 app / MCP 工具调用永远要审批,即便它同时标了只读等其它提示。默认 agent 断网;会抓取外部内容的场景可能带来 prompt injection —— 它替你读回的网页或工单里,可能藏着写给模型看的指令。截至 2026-08-05。OpenAI Codex Docs · Agent approvals & security — Codex also elicits approval for app (connector) tool calls that advertise side effects; app / MCP tool calls marked with a destructive annotation always require approval, even if they also advertise other hints like read-only. By default the agent has no network; fetching external content can expose you to prompt injection — the page or ticket it reads back may hide instructions written for the model. As of 2026-08-05. This is the last cell of 'connect but don't lose control': the class of action no loose setting waves through, held for you at the protocol layer.
— IV
能接,不等于该接'Can Connect' Is Not 'Should Connect'.
现在说那条更要紧的线,它有两头。一头是额度:每接一个服务器,它的工具清单就要占你每条消息的上下文 —— 官方省额度建议里明写着一条「限制你用的 MCP 服务器数量,不用时禁用它们」。3注 3Note 3OpenAI Codex 文档 · Pricing(省额度建议)—— 每接一个 MCP 服务器都会给你的每条消息加更多上下文、多吃额度;官方省额度建议里明列一条:「限制你用的 MCP 服务器数量……不用时禁用它们。」截至 2026-08-05。OpenAI Codex Docs · Pricing (quota-saving tips) — every MCP server you add puts more context into each message and uses more of your allowance; the official quota-saving tips list one verbatim: 'Limit the number of MCP servers you use … Disable MCP servers when you don't need them.' As of 2026-08-05.接十个服务器却只用一个,是拿真金白银养着九份闲置上下文。另一头是安全:会抓取外部内容的服务器可能带来 prompt injection —— 它替你读回的网页或工单里,可能藏着写给模型看的指令,诱它做你没让它做的事。2注 2Note 2OpenAI Codex 文档 · Agent approvals & security —— Codex 也会为宣告有副作用的 app(连接器)工具调用征求审批;标了破坏性注解的 app / MCP 工具调用永远要审批,即便它同时标了只读等其它提示。默认 agent 断网;会抓取外部内容的场景可能带来 prompt injection —— 它替你读回的网页或工单里,可能藏着写给模型看的指令。截至 2026-08-05。OpenAI Codex Docs · Agent approvals & security — Codex also elicits approval for app (connector) tool calls that advertise side effects; app / MCP tool calls marked with a destructive annotation always require approval, even if they also advertise other hints like read-only. By default the agent has no network; fetching external content can expose you to prompt injection — the page or ticket it reads back may hide instructions written for the model. As of 2026-08-05.Now the line that matters more, and it has two ends. One is quota: every server you add parks its tool list in the context of each message — the official quota-saving tips write it plainly, 'limit the number of MCP servers you use, disable them when you don't need them.'3注 3Note 3OpenAI Codex 文档 · Pricing(省额度建议)—— 每接一个 MCP 服务器都会给你的每条消息加更多上下文、多吃额度;官方省额度建议里明列一条:「限制你用的 MCP 服务器数量……不用时禁用它们。」截至 2026-08-05。OpenAI Codex Docs · Pricing (quota-saving tips) — every MCP server you add puts more context into each message and uses more of your allowance; the official quota-saving tips list one verbatim: 'Limit the number of MCP servers you use … Disable MCP servers when you don't need them.' As of 2026-08-05. Connecting ten servers to use one is paying real money to keep nine idle contexts alive. The other end is security: servers that fetch external content can expose you to prompt injection — the page or ticket it reads back may hide instructions written for the model, luring it to do what you didn't ask.2注 2Note 2OpenAI Codex 文档 · Agent approvals & security —— Codex 也会为宣告有副作用的 app(连接器)工具调用征求审批;标了破坏性注解的 app / MCP 工具调用永远要审批,即便它同时标了只读等其它提示。默认 agent 断网;会抓取外部内容的场景可能带来 prompt injection —— 它替你读回的网页或工单里,可能藏着写给模型看的指令。截至 2026-08-05。OpenAI Codex Docs · Agent approvals & security — Codex also elicits approval for app (connector) tool calls that advertise side effects; app / MCP tool calls marked with a destructive annotation always require approval, even if they also advertise other hints like read-only. By default the agent has no network; fetching external content can expose you to prompt injection — the page or ticket it reads back may hide instructions written for the model. As of 2026-08-05.接线前过三问,比接完再后悔便宜:这条数据真需要直读吗 —— 一次性的贴进来更快,反复要的才值得接;只读够不够 —— 能查和能改是两个半径,从只读开始;写操作有没有闸 —— 危险动作用上一节的按工具审批档单独按住。接线是为了少搬运,不是为了收集服务器。Three questions before wiring beat regret after: does this data truly need direct reading — one-offs are faster pasted, only the recurring earns a wire; is read-only enough — querying and mutating are two radii, start read-only; is there a gate on writes — hold dangerous actions with the previous section's per-tool approval. Wiring is to haul less, not to collect servers.动手 · 接第一条线,按信任梯度来:Hands-on · wire your first line, up the trust gradient:
01
挑你每周复制最多的那个系统Pick the system you copy from most
工单、报错监控或文档站,选一个。codex mcp add 接上,/mcp 确认连通,先只开只读工具。Tracker, error monitor, or docs site — pick one. codex mcp add it, confirm in /mcp, and enable only the read-only tools first.
02
给它定一个 prompt 审批档,跑一周Give it a prompt approval mode, run a week
default_tools_approval_mode 设 prompt,让每次调用都过你一眼;观察它把数据用得对不对,再决定要不要放开某几个自动。Set default_tools_approval_mode to prompt so each call passes your eye; watch whether it uses the data correctly, then decide which few to let run automatically.
03
月底数一遍你真在用的服务器At month's end, count the servers you actually use
把一个月没调用过的服务器 disabled 掉 —— 每个闲置服务器都在吃你的上下文和额度。少接,是省额度纪律里最实的一条。Disable any server you haven't called in a month — each idle one eats context and quota. Fewer servers is the most concrete quota discipline there is.
上下文不该靠你搬运,
但每根线都记在账上.
Context shouldn't be hauled by you —
but every wire is on the bill.
Aklman Library
— 讨论Discussion
讨论Discussion.
评论区初始化中…Initializing comments…
01 / 01
没有匹配结果No matches.
换个关键词，或按 Esc 回到页面Try another keyword, or press Esc to return
