Thanks to visit codestin.com
Credit goes to docs.polylane.com

Getting started

Quickstart

Install the Polylane CLI with one command, sign in, connect your stack, and watch Polylane start detecting, investigating, and fixing.

Install the CLI

One command on macOS or Linux:

Terminal
curl -fsSL https://polylane.com/install | bash

The script downloads the latest release of the polylane CLI, verifies its checksum, installs it to ~/.polylane/bin, and puts it on your PATH. It then runs polylane setup, which detects your coding agents (Claude Code, Cursor, OpenCode, Codex, Pi, Warp, Cline, Roo Code, Goose, Gemini CLI, Windsurf, Zed, VS Code), installs the Polylane skills where the agent supports them, and registers the platform MCP server in each agent's own config. Skip that step with --no-setup. It needs Node.js 20+ and falls back to Homebrew when Node is missing. Safe to re-run. Prefer a package manager, or on Windows? Every channel is listed in the CLI overview.

The installer then signs you in: browser OAuth through Google or GitHub, email, a device code for machines without a browser, or an API key. Sign-in creates your account and workspace on the spot if you don't have one. After sign-in the installer authenticates the MCP server it just registered with a workspace API key, offers to connect GitHub, Slack, cloud accounts, an observability tool, and a cloud coding agent, and finishes by opening your workspace in the browser. Each connect starts discovery in the background, so there is something to see when it does.

Installed with npm or Homebrew instead? Sign in yourself:

Terminal
polylane auth login

This opens the browser OAuth flow (use --no-browser on SSH or headless machines). From here the whole platform is in reach: polylane issue list --active shows what needs attention, and every command group is a --help away.

What is Polylane?

Polylane runs agents that read your code, watch your infrastructure, detect issues, investigate them, and fix them. The platform works as a loop with four steps:

  • Context: connect your clouds, repositories, and observability providers. Polylane builds a live context graph of everything, rendered as your topology.
  • Detection: checks run against connected resources and raise issues, each worked by a fix run you read as a thread. Alerts from your providers flow into the same lifecycle.
  • Investigation: agents dig into what was detected through threads and investigations.
  • Remediation: autofixes turn findings into fixes.

Set up with your coding agent

Prefer to let the agent you already use do the setup? Copy this prompt into your coding agent, then follow its lead:

Loading the prompt…

The agent points you at Google or GitHub sign-in, which arrives already verified, then connects the platform MCP server with an API key and connects every cloud and integration it can from credentials you already have. If you prefer email and password, it runs signup itself and asks you for the emailed code. Either way the GitHub App installation and OAuth for Vercel, Slack, and Sentry stay yours to click. Nothing to install.

Or set up from the console

  1. Sign in at console.polylane.com and create a workspace.
  2. Connect one of each: a cloud, a code host, and an observability provider. See Integrations and Clouds for everything you can connect.
  3. Start a thread and ask about what Polylane already sees: "which services run in our production cloud account, and which had deploys in the last 24 hours?"

Watch the loop start

Detection begins as soon as resources sync. Checks run against everything you connected, and each real problem becomes an issue with a fix run you read under Threads. Provider alerts you already have flow into the same lifecycle, and every pull request in a connected repository is reviewed by change intelligence before it merges.

Issues and alerts get investigated on their own. For anything else, ask in a thread or mention Polylane in Slack, and the agent investigates with the same context.

Next steps