v1.1.0Pi v1.1.0 源码分析Analysis of Pi v1.1.0 · 2026-10-07

mcpmcp

独立的 Model Context Protocol 客户端Standalone Model Context Protocol client for pi and other applications

Extensions

← → 翻页 · F 全屏 · O 目录 · T 明暗 · L 语言← → navigate · F fullscreen · O overview · T theme · L language

图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.001
01 · 模块结构01 · Module structureExtensions

模块结构Module structure

pi-mcp modules (3,243 lines of TypeScript)客户端与协议Client & protocol传输TransportsOAuth（入口 ./oauth）OAuth (entry ./oauth)导入路径、依赖与使用者Import paths, dependencies and users615client.tsMcpClient：握手 · 请求 · 分页McpClient: handshake · requests · paging113protocol/jsonrpc.tsJSON-RPC 2.0 消息 · 错误JSON-RPC 2.0 messages · errors131protocol/types.ts协议版本 · 能力 · Toolversions · capabilities · Tool117protocol/content.ts内容块 · toLlmContent()content blocks · toLlmContent()20auth-provider.tsAuthProvider 接口the AuthProvider interface71index.ts包入口 "."package entry "."55transports/transport.tsMcpTransport · TransportEvents216transports/stdio.ts子进程 · 按行 JSONchild process · line-delimited JSON505transports/streamable-http.tsPOST + SSE · 会话 · 重连POST + SSE · sessions · reconnect51transports/in-memory.ts测试用的一对传输a linked pair for tests1testing/index.ts入口 "./testing"entry "./testing"481oauth/flow.tsauthorizeMcp · PKCE · 刷新authorizeMcp · PKCE · refresh215oauth/discovery.ts.well-known 元数据发现.well-known metadata discovery209oauth/types.ts元数据 · 令牌 · 客户端类型metadata · token · client types168oauth/provider.tsMcpOAuthProvider · 状态存储McpOAuthProvider · state store164oauth/callback.ts本地回调服务器loopback callback server55oauth/errors.tsOAuthError 等 5 个类OAuthError and 4 more@earendil-works/pi-mcp@earendil-works/pi-mcp/oauth@earendil-works/pi-mcp/testingcross-spawn 7.0.6coding-agent · extensions/mcp (4,240)运行时依赖：runtime dep:不依赖任何 pi 包；pi 内唯一的使用者是 coding-agent 的内置 MCP 扩展。Depends on no pi package; inside pi its only user is coding-agent's built-in MCP extension.标签 = 行数tag = lines of code客户端 · 协议client · protocol传输transportsOAuth

最大的文件是 client.ts；其次是 transports/streamable-http.ts——HTTP 传输要处理会话、SSE 解析、认证重试和断线续传。The largest file is client.ts, followed by transports/streamable-http.ts — the HTTP transport handles sessions, SSE parsing, auth retries and stream resumption.

图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.002
02 · 连接与握手02 · Connecting and the handshakeExtensions

连接与握手Connecting and the handshake

Connecting: the state machine and the initialize handshakeMcpClient 状态McpClient state只能 connect 一次；closed 不可逆connect() once; closed is final握手时序（client.connect）Handshake sequence (client.connect)idleconnectingconnectedclosedMcpClientMcpTransportMCP 服务器MCP server«client»ClientCapabilities+experimental+roots+sampling+elicitation«server»ServerCapabilities+experimental+logging+prompts+resources+tools+completions2025-11-252025-06-182025-03-262024-11-05connect()握手完成handshake doneclose()任一步失败 → close()any step fails → close()transport.start()stdio：启动子进程 · http：无操作stdio: spawn the process · http: no-opinitializeprotocolVersion "2025-11-25" · capabilities · clientInfoInitializeResultprotocolVersion · capabilities · serverInfo · instructions校验：版本必须是支持的 4 个之一check: the version must be one of the 4 supportedsetProtocolVersion(v)http：之后每个请求带 MCP-Protocol-Versionhttp: every later request carries MCP-Protocol-Versionnotifications/initializedhttp：此后才打开 GET 事件流http: only now is the GET stream openedinitialize 不可取消；roots 选项存在时 capabilities 自动加上 roots: {}。initialize cannot be cancelled; with a roots option, capabilities gains roots: {} automatically.支持的协议版本SUPPORTED VERSIONS第一个 = LATEST_PROTOCOL_VERSION，默认发送它the first = LATEST_PROTOCOL_VERSION, sent by default123456实线：客户端 → 服务器solid: client → server虚线：服务器 → 客户端dashed: server → client失败failure

支持的版本：2025-11-25、2025-06-18、2025-03-26、2024-11-05。服务器选了别的版本时连接直接失败，而不是“尽量兼容”。Supported versions: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05. A server that picks another version fails the connection outright instead of a best-effort fallback.

图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.003
03 · 请求、超时与取消03 · Requests, timeouts and cancellationExtensions

请求、超时与取消Requests, timeouts and cancellation

Request bookkeeping: timeouts, progress, cancellation and paging客户端发出的请求Requests the client sendsclient.request(method, params, opts)服务器发来的请求Requests from the server分页：listAll()Paging: listAll()listTools · listResources · listResourceTemplatesid = nextRequestId++递增整数an increasing integer_meta.progressToken = id仅当传了 onProgressonly with onProgresspending.set(id, entry)resolve · reject · timer · signalarmTimeout(30,000 ms)默认值，可按请求覆盖default; per-request overridetransport.send(message)发送失败 → 直接 rejectsend fails → reject at once响应到达response arrivesresult → resolve · error → McpError(code)notifications/progress重新计时 + onProgress(…)re-arm the timeout + onProgress(…)超时timeoutMcpTimeoutError + notifications/cancelledsignal 中止signal abortedMcpAbortError + notifications/cancelled传输关闭 / close()transport closed / close()所有 pending → McpConnectionClosedErrorall pending → McpConnectionClosedErrorrequestHandlers.get(method)内置：ping → {} · roots/list（配置了 roots 时）built in: ping → {} · roots/list (when roots are set)没有处理器no handler-32601 Method not foundhandler(params, { signal })incoming.set(id, AbortController)回复replyresult ?? {} · McpError 原样 · 其他 → -32603result ?? {} · McpError as is · other → -32603notifications/cancelled{ requestId } → 中止该处理器的 signal{ requestId } → abort that handler's signalrequest(method, { cursor })第一页不带 cursorfirst page without cursoritems.push(...page)tools / resources / resourceTemplatesnextCursor?缺失、null 或 "" → 结束missing, null or "" → done重复 cursor → 抛错duplicate cursor → throw最多 1,000 页at most 1,000 pagesinitialize 例外：中止或超时只 reject，不发 notifications/cancelled（规范禁止取消 initialize）。Exception: initialize is rejected on abort/timeout but never cancelled — the spec forbids it.每条进度通知都把超时重新计时，长任务只要持续报进度就不会超时。Every progress notification re-arms the timeout, so long tasks that keep reporting never time out.未知 id 的响应只报 onError，不影响其他请求。A response with an unknown id only goes to onError; other requests are unaffected.setRequestHandler(method, fn) 可增加或替换处理器。setRequestHandler(method, fn) adds or replaces a handler.listResourcesPage(cursor) 等单页方法留给需要自己控制分页的调用方。Single-page methods such as listResourcesPage(cursor) are there for callers that page themselves.流程flow收到消息message received失败 / 取消failure / cancel

传了 onProgress 时，请求的 _meta.progressToken 就是它的 id；每条 notifications/progress 都会重新计时——持续报进度的长任务不会超时。With onProgress, the request's _meta.progressToken is its id; every notifications/progress re-arms the timeout — long tasks that keep reporting never time out.

图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.004
04 · stdio 传输04 · The stdio transportExtensions

stdio 传输The stdio transport

StdioTransport: a child process, line-delimited JSON and a three-step shutdownstart()启动服务器进程spawn the server分帧Framing一行 = 一条 JSON-RPC 消息one line = one JSON-RPC messageclose()规范要求的关闭顺序：先关 stdin，再发信号the spec's shutdown order: close stdin first, then signalscrossSpawn(command, args)cross-spawn：Windows 上也能跑 .cmd 包装cross-spawn: .cmd shims work on Windows tooenv = process.env + envinheritEnv: false → 只用 envinheritEnv: false → env onlydetached: true非 Windows：自己的进程组non-Windows: its own process groupawait "spawn" | "error"命令不存在 → start() rejectmissing command → start() rejectsMcpClientchild.stdinJSON.stringify(msg) + "\n"MCP 服务器MCP server子进程child processchild.stdout按 0x0a 切分 · 去掉 \rsplit at 0x0a · strip \rchild.stderr保留最后 64 KiB · onStderrkeeps the last 64 KiB · onStderr进程组记入 liveProcessGroups；宿主退出时统一 SIGTERM。Groups go into liveProcessGroups; host exit SIGTERMs them all.send()onMessage空行跳过；解析失败 → onError，继续读下一行blank lines skipped; parse failure → onError, keep reading单行超过 16 MiB → 丢弃并报错a line over 16 MiB → dropped with an errorstderr 只是日志：stderr is only a log:stderr: "inherit" 时直接给宿主终端stderr: "inherit" sends it to the host terminalt = 0 msstdin.end()让服务器自己退出let the server exit on its ownt = 500 msSIGTERM500 ms 后 · 整个进程组after 500 ms · the whole groupt = 2,500 msSIGKILL再过 2,000 ms（closeTimeoutMs）2,000 ms later (closeTimeoutMs)子进程 "close" 后：after the child's "close":再对进程组发一次 SIGTERM，SIGTERM the group once more, sonpx / uvx 包装下的真正服务器也会退出the real server under npx / uvx exits tooWindows：taskkill /pid … /T /FWindows: taskkill /pid … /T /F服务器提前退出时：残留的半行 → onError，然后 onClose（只触发一次），McpClient 拒绝所有 pending 请求。If the server exits first: a leftover partial line → onError, then onClose (fires once); McpClient rejects every pending request.客户端 → 服务器client → server服务器 → 客户端server → client日志log

用进程组是为了 npx、uvx 这类包装命令：只杀包装进程会留下真正的服务器。Windows 上改用 taskkill /T /F。Process groups exist for wrapper commands such as npx and uvx: killing only the wrapper would leave the real server running. Windows uses taskkill /T /F instead.

图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.005
05 · Streamable HTTP 传输05 · The Streamable HTTP transportExtensions

Streamable HTTP 传输The Streamable HTTP transport

  • 会话：服务器在响应头里给出 Mcp-Session-Id，之后每个请求都带上；带着会话 id 收到 404 → McpSessionExpiredError。Sessions: the server returns Mcp-Session-Id in a response header and every later request carries it; a 404 with a session id → McpSessionExpiredError.
  • 401（或 403 且 error="insufficient_scope"）先交给 authProvider.onUnauthorized() 一次，然后用新凭据重发；仍失败就抛 McpAuthRequiredError。A 401 (or a 403 with error="insufficient_scope") goes to authProvider.onUnauthorized() once, then the request is retried with the new credentials; if it still fails, McpAuthRequiredError is thrown.
StreamableHttpTransport: one URL, POST to send, SSE to receive每个请求的头Headers on every requestsend(message) → POST按消息类型和 Content-Type 分支branches on message kind and Content-Type错误映射Error mappingcheckResponse()SSE 流与重连SSE streams and reconnectionauthorizedFetch("POST")401/403 → 见下方401 / 403 → see below通知 / 响应notification / response202 · 丢弃 body；若是 notifications/initialized → 打开 GET 流202 · discard the body; notifications/initialized → open the GET streamapplication/json一条或一批（数组）消息 → onMessageone message or a batch (array) → onMessagetext/event-streamconsumeResponseStream(body, id)：读到该 id 的响应为止consumeResponseStream(body, id): read until that id's response请求却得到 202/204，或其他类型a request answered 202/204, or another typeMcpHttpError401404othersrunGetStream()一直保持打开；405 = 服务器不提供kept open; 405 = server offers noneconsumeResponseStream()只有带事件 id 时才续传resumes only if events carry ids退避重连：Last-Event-ID 续传Back-off reconnect, resuming with Last-Event-ID延迟 = 服务器的 retry 字段，否则 min(1,000 × 2^n, 30,000) ms · 连续失败 5 次放弃delay = the server's retry field, else min(1,000 × 2^n, 30,000) ms · give up after 5 failures in a rowAcceptapplication/json, text/event-streamContent-Typeapplication/jsonMcp-Session-Id服务器在响应里分配后once the server assigned oneMCP-Protocol-Version握手协商出的版本the negotiated versionAuthorizationBearer <authProvider.token()>options.headers 先放入，上面这些覆盖它们。options.headers go first; these override them.McpAuthRequiredError带 wwwAuthenticatecarries wwwAuthenticateMcpSessionExpiredError仅当已有会话 idonly with a session idMcpHttpError(status)body 截到 8 KiBbody capped at 8 KiB401，或 403 且 error="insufficient_scope"：401, or 403 with error="insufficient_scope":先交给 authProvider.onUnauthorized() 一次，再重发hand to authProvider.onUnauthorized() once, then retry可重试：408 · 429 · 5xx · 网络错误（TypeError、E*/UND_ERR_* 码）；认证、会话与协议错误不重试。Retryable: 408 · 429 · 5xx · network errors (TypeError, E* / UND_ERR_* codes); auth, session and protocol errors are not.响应流断掉且无法续传：为该请求合成一条 -32603 错误响应，其余请求不受影响。A response stream that breaks and cannot resume: a synthetic -32603 error response for that request only.close()：中止所有 fetch，带会话 id 发 DELETE（1 s 超时，复用上一个 token）。close(): abort every fetch, send DELETE with the session id (1 s timeout, reusing the last token).分支branch错误error流streams
图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.006
06 · OAuth 授权06 · OAuth authorizationExtensions

OAuth 授权OAuth authorization

  • adaptOAuthProvider() 把它包装成传输用的 AuthProvider：并发的 401 共用一次授权；如果出错请求用的 token 已经被别人换掉了，就直接重试——轮换的 refresh token 不能用两次。adaptOAuthProvider() wraps it as the transport's AuthProvider: concurrent 401s share one authorization; if the failing request's token was already replaced, it simply retries — a rotating refresh token cannot be used twice.
  • 403 insufficient_scope 是 step-up：跳过刷新，请求“已授予 ∪ 挑战要求”的 scope。A 403 insufficient_scope is a step-up: refresh is skipped and the scope requested is “granted ∪ challenged”.
OAuth: from a 401 to a usable access tokenrunFlow()每一步的结果都存进 providereach step's result is saved in the providerOAuthCallbackServer.listen()McpOAuthProviderMcpOAuthStateHTTP 401 · 403 insufficient_scope来自 StreamableHttpTransportfrom StreamableHttpTransportadaptOAuthProvider().onUnauthorized并发 401 共用一次 · token 已换过就直接重试concurrent 401s share one run · token already replaced → just retryauthorizeMcp(provider, options)→ "AUTHORIZED" | "REDIRECT"4 · 有 refresh_token？4 · Have a refresh_token?grant_type=refresh_tokensaveTokens → "AUTHORIZED"刷新成功；scope 缺省 = 原授权的refreshed; missing scope = the grant's5 · startAuthorization()PKCE S256 · state · resourcesaveCodeVerifier → redirectToAuthorization返回 "REDIRECT"returns "REDIRECT"传输里 → McpOAuthAuthorizationRequiredErrorin the transport → McpOAuthAuthorizationRequiredError6 · 带 authorizationCode 再调一次6 · Called again with authorizationCodeiss 校验（RFC 9207）iss check (RFC 9207)exchangeAuthorizationCode + codeVerifiersaveTokens → "AUTHORIZED"scope 缺省 = 请求的 scopemissing scope = the requested oneclientInformationtokenstokensExpireAtcodeVerifieroauthStatediscovery1 · 发现1 · DiscoverWWW-Authenticate: resource_metadata=…/.well-known/oauth-protected-resource{path}→ authorization_servers[0]（缺省：服务器根）→ authorization_servers[0] (default: server root)/.well-known/oauth-authorization-server{path}/.well-known/openid-configuration{path}结果缓存为 discoveryStatecached as discoveryState2 · resource 与 scope2 · resource and scoperesource 必须与服务器 URL 匹配resource must match the server URLscope = 参数 || scopes_supportedscope = option || scopes_supported || clientMetadata.scope403 step-up：已授予 ∪ 挑战要求403 step-up: granted ∪ challenged3 · 客户端身份3 · Client identity已存的 clientInformationstored clientInformation或 Client ID Metadata Documentor a Client ID Metadata Document （https、路径非根） (https, non-root path)或动态注册 registration_endpointor dynamic registration at registration_endpoint有yes无no刷新遇到网络错误或 server_error → 落到第 5 步；其他 OAuthError 抛出，交给 authorizeMcp 的恢复逻辑。A refresh that hits a network error or server_error falls through to step 5; other OAuthErrors are thrown to authorizeMcp's recovery.错误恢复：invalid_client / unauthorized_client → 清空全部凭据重来；invalid_grant → 只清令牌重来。Recovery: invalid_client / unauthorized_client → wipe all credentials and rerun; invalid_grant → wipe tokens only and rerun.127.0.0.1 · 端口 0（随机）· 路径 /callback127.0.0.1 · port 0 (random) · path /callback浏览器带回 code · state · iss；5 分钟超时the browser brings back code · state · iss; 5-minute timeout之后用这些参数调用第 6 步step 6 then runs with these parameterspi：只有 /mcp 里的登录会走浏览器；连接本身从不弹浏览器。pi: only sign-in from /mcp opens a browser; connections never do.按精确的 serverUrl 存取：别的服务器的状态一律忽略。keyed by the exact serverUrl: state of any other server is ignored.默认 MemoryOAuthStateStore；pi 存到 mcp-auth.json。default MemoryOAuthStateStore; pi persists to mcp-auth.json.流程flow需要用户参与 / 失败needs the user / failure成功success
图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.007
07 · 内容转换与错误类型07 · Content conversion and error typesExtensions

内容转换与错误类型Content conversion and error types

How tool results become model input, and the error typestoLlmContent(result)CallToolResult → (text | image)[]错误类型Error types缩进 = 子类indent = subclassJSON_RPC_ERROR_CODESTextContent · "text"{ type: "text", text }ImageContent · "image"{ type: "image", data, mimeType }AudioContent · "audio""[audio <mime> omitted]"ResourceLinkContent · "resource_link""<name>: <uri>"resource · TextResourceContents{ type: "text", text }resource · Blob, mimeType image/*{ type: "image", data: blob }resource · other blob"[binary resource … omitted]"content 为空但有 structuredContent → 一条 JSON 文本（缩进 2）no content but structuredContent → one JSON text block (indent 2)McpErrorcode · data：JSON-RPC 错误响应code · data: a JSON-RPC error responseMcpTimeoutError请求超时request timed outMcpAbortErrorsignal 中止signal abortedMcpConnectionClosedError传输关闭 / 未连接transport closed / not connectedMcpHttpErrorstatus · bodyMcpAuthRequiredError401 · wwwAuthenticateMcpSessionExpiredError404：会话失效404: session expiredMcpOAuthAuthorizationRequiredError需要用户登录（./oauth）the user must sign in (./oauth)-32700 parseError-32600 invalidRequest-32601 methodNotFound-32602 invalidParams-32603 internalErrorContentBlockLlmContent原样as is原样as is占位文字placeholder名称 + URIname + URI内嵌文本embedded text内嵌图片embedded image占位文字placeholder转换converted降级为文字degraded to text子类subclass

LlmContent 的形状与 pi-ai 的 TextContent / ImageContent 一致，但 pi-mcp 并不依赖 pi-ai。LlmContent has the same shape as pi-ai's TextContent / ImageContent, yet pi-mcp does not depend on pi-ai.

图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.008
08 · 在 pi 中的使用08 · How pi uses itExtensions

在 pi 中的使用How pi uses it

How pi uses pi-mcp: coding-agent's built-in MCP extension服务器从哪里来Where servers come fromextensions/mcp/4,240 行4,240 lines工具名Tool namescreateMcpToolName()exposure：工具怎样出现在模型面前exposure: how tools reach the model按服务器设置，toolExposure 按工具覆盖set per server; toolExposure overrides per tool~/.pi/agent/mcp.json全局 · 可用 auth: { provider }global · may use auth: { provider }.pi/mcp.json仅受信任的项目 · 同名覆盖全局trusted projects only · same name replaces global只写 enabled/exposure 时只改这几项only enabled / exposure → just overrides thosepi.registerMcpServer()扩展注册 · mcp.json 中同名优先from extensions · mcp.json wins on a name clashcommand → StdioTransporturl → StreamableHttpTransportnew McpClient({ name, version })会话开始时后台连接connects in the background at session startOAuth：存的令牌 + 刷新OAuth: stored token + refresh<agent-dir>/mcp-auth.json · /mcp 登录<agent-dir>/mcp-auth.json · sign in with /mcp"codemode"默认：只能在 codemode 脚本里调用default: callable only from codemode scripts不进工具声明；脚本用 searchTools() 找not declared; scripts find them via searchTools()"deferred"tool_search 加载后才声明declared once tool_search loads them激活 tool_search 而不是 codemodeactivates tool_search instead of codemode"direct"立即声明给模型declared to the model right away和内置工具一样直接调用called directly like built-in tools"hidden"完全不可达unreachable/mcp 里可以改回来switch it back in /mcp格式与其他 MCP 客户端相同：{ "mcpServers": { … } }Same shape as other MCP clients: { "mcpServers": { … } }env / headers 的值可写 ${NAME} 或 !cmdenv / header values may use ${NAME} or !cmd第一次提示只等待有 direct 工具的服务器；The first prompt waits only for servers with direct tools;其他服务器在脚本或工具真正用到时再等。others are awaited when a script or tool needs them.规则RULEmcp__<server>__<tool># [^A-Za-z0-9_] → _mcp__docs__search_pagesmcp__my_server__get_issue超过 64 个字符或与另一工具重名：Longer than 64 chars, or clashing:截断 + "_" + sha256(server\0tool) 前 8 位truncate + "_" + first 8 hex of sha256(server\0tool)名字同时就是 codemode 脚本里的标识符：The name is also the identifier in codemode:await tools.mcp__docs__search_pages({…})资源走 3 个通用工具：Resources use three generic tools:list_mcp_resources · …_templates · read_mcp_resourcecodemode 曝光的服务器连上时，若 autoEnableCodemode（默认 true）就自动激活 codemode 工具。When a codemode-exposure server connects, the codemode tool is activated unless autoEnableCodemode (default true) is false.每次调用都走 pi 的工具管线：tool_call / tool_result 钩子与权限扩展同样作用于 MCP 工具。Every call runs through pi's tool pipeline: tool_call / tool_result hooks and permission extensions apply to MCP tools too.配置configMCP 运行时MCP runtimeOAuth传输transport

四种 exposure：codemode（默认）、deferred（tool_search 加载后才声明）、direct（立即声明）、hidden；toolExposure 可以按工具覆盖。Four exposures: codemode (default), deferred (declared once tool_search loads them), direct (declared right away) and hidden; toolExposure overrides per tool.

图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.009
扩展点Extension pointspi-coding-agent

mcp 的扩展点Where to plug into mcp

1
McpTransportMcpTransport

实现 start / send / close 与三个监听即可接入新的传输。Implement start / send / close and three listeners to add a transport.

2
AuthProviderAuthProvider

token() 加可选的 onUnauthorized()：任何认证方案。token() plus an optional onUnauthorized(): any auth scheme.

3
OAuthClientProvider · McpOAuthStateStoreOAuthClientProvider · McpOAuthStateStore

自定义 OAuth 状态的存储与跳转方式。Customise how OAuth state is stored and how redirects happen.

4
client.setRequestHandler(method, fn)client.setRequestHandler(method, fn)

响应服务器发来的请求（如 sampling、elicitation）。Answer requests from the server (e.g. sampling, elicitation).

5
client.onNotification(method, fn)client.onNotification(method, fn)

监听 list_changed 等通知。Listen for notifications such as list_changed.

← 返回完整图解← Back to the full walkthroughgithub.com/earendil-works/pi · v1.1.0
图解 Pi Agent · Pi v1.1.0Pi Agent, Illustrated · Pi v1.1.010
←
1 / 10