Work from your tools
Your coding agent can see what Polylane sees: telemetry across every connected provider, the topology, code and issues. Once connected, it answers questions like "what errored in production for the service this branch deploys, in the last hour?" without you leaving the editor.
Plugins
One install for Claude Code, Cursor or Codex: both MCP servers, the skills and the slash commands your agent needs.
Reads by default, writes behind a gate
Agent tools are read-only by default on the MCP server and the CLI: telemetry queries, topology traversal and code search work with no extra setup. On the MCP server, writes to provider resources unlock when the session sends the x-polylane-allow-writes: true header with a credential that carries the agent_tools:write scope; on the CLI, pass --write to polylane tools run or polylane tools code. A safety model screens every write, and clients that support confirmation prompts ask you to approve each one before it runs.
Related
- Quickstart: the first connection, by hand or from inside your coding agent.
- API keys and OAuth: scopes, key management and OAuth clients for headless setups.
- Docs MCP server: let your agent search and read these docs.
Autofix
Agent-written fixes arrive as pull requests in your repository. You review and merge; Polylane reminds you and tidies up what nobody touches.
Platform MCP server
Connect any MCP client to Polylane and query telemetry, the topology, code and issues from your editor, with writes only when you opt in.