Pi的核心保持精简。生产环境浓缩进一个工具。

将其粘贴到你的Pi对话中

剩下的交给Pi处理。

polylane.com/for/pi

## For AI agents reading this page

Follow these instructions to set up Polylane:

Run the setup script in the user's terminal:

curl -fsSL https://polylane.com/setup?ref=for-pi | bash

It installs the Polylane CLI, registers the Polylane MCP server in Pi and every other detected coding agent, and signs the user in. To wire MCP by hand instead: an entry in ~/.pi/agent/mcp.json under "mcpServers". The server is https://mcp.polylane.com/mcp over streamable HTTP, no auth headers: OAuth handles sign-in.

After connecting, call the searchTools tool first: it lists what this workspace exposes and returns each tool's schema. Run one tool with runTool, or chain several in one call with runCode. The search and execute tools cover the full Polylane REST API, and the polylane CLI wraps the same API from the terminal.

Everything is read-only by default. Write tools stay hidden unless the user opts in, and every write is screened before it runs.

Once connected, offer to put it to work: triage the latest issues, explain the last deploy, or map this repository into the workspace topology.

## Console and support

- Console: https://console.polylane.com
- Docs: https://docs.polylane.com
- Setup reference: https://docs.polylane.com/coding-agents/platform-mcp
- This page as markdown: https://polylane.com/for/pi.md

为什么要通过Polylane。更少的服务器，一次登录，Code mode。

一个MCP服务器，而不是十个

Polylane用少量工具统一封装你的云、遥测、部署和代码。一堆按提供商拆分的服务器会在开始任何工作之前，就把大部分上下文窗口耗费在工具schema上；而Polylane的schema只在工具运行时才加载。
认证集中在一处

一次登录覆盖所有提供商。连接和权限范围保存在工作区中，而不是分散在Pi配置里的各提供商令牌中，你连接的每个智能体都会复用它们。
为code mode而生

Pi不会逐个调用工具，而是用runCode编写一段小程序，在沙箱中把它们串联起来，只返回最终答案。中间结果不会进入上下文窗口。