Quickstart
This page takes you from nothing to the first fix Polylane opens as a pull request. At the end, your cloud, code and telemetry are connected, and the first issue is being worked in a thread you can read from top to bottom.
Install the CLI or sign in at the console
One command on macOS or Linux installs the CLI, signs you in, and starts connecting your stack:
curl -fsSL https://polylane.com/install | bash
Sign in with Google, GitHub or email; signing in creates your account and workspace when you do not have one yet. If you would rather skip the terminal, sign in at console.polylane.com, create a workspace, and connect from Settings. Package managers and Windows are covered on the CLI page.
Connect a repository, a cloud and an observability tool
The installer offers each connection in the order below, and the console has a page for each under Settings.
| What to connect | Description |
|---|---|
| Repository | Install the GitHub App and agents can read your code, review every pull request, and open fixes as pull requests. See Repositories. |
| Cloud account | Every resource appears on the topology, kept in sync and checked on a schedule. See Clouds. |
| Slack | Mention Polylane in a channel and the answer arrives in a Slack thread. See Integrations. |
| Observability tool | Logs, metrics and alerts from your provider feed detection and give agents evidence to cite. See Integrations. |
Clouds whose logs and metrics Polylane can query (AWS, Cloudflare, Vercel, Fly, Render, Railway and Kubernetes) already count as a telemetry source, so you can start without a separate observability tool.
Ask a first question
Open Threads, choose New thread, and ask about what Polylane already sees, for example: "Which services run in our production cloud account, and which had deploys in the last 24 hours?" The answer draws on the connected resources and cites the tool calls behind it.
Watch the first fix run
Detection starts as soon as resources sync, and alerts from your connected tools join the same lifecycle. Each real problem becomes an issue worked by one fix run: the agent reaches a verdict, traces the cause, and opens a pull request when a code change fixes it. Read the run under Threads with the Type filter set to Fix run; the pull request appears in your repository for your review.
Connect your coding agent
Ask the same questions from your editor or terminal. Polylane for coding agents has the prompt to paste and the CLI path. polylane setup registers the platform MCP server with your coding agents through the CLI.
Related
- How Polylane works: the loop and every primitive you will meet in the console, on one page.
- Connect: everything you can connect and what Polylane builds from it.
- Work from your tools: the MCP server, the CLI and the plugins that bring Polylane into your editor.
- API reference: the full HTTP surface for scripts and CI.