Skip to content

Open-source status page, incident response and uptime monitoring

Set up Polylane (#2586)

polylane[bot]2f9599035bd6
diff --git a/AGENTS.md b/AGENTS.md
index da50576aa..229300d06 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -89,3 +89,13 @@ boundaries with external SDKs or at registry-style dispatch. When you need one:
`docs/adr/` is frozen background on *why* some of these decisions were made. It
is history, not current state; this file and its nested siblings are current
state. Do not add new ADRs.
+
+<!-- polylane:start -->
+## Investigating production with Polylane
+
+[Polylane](https://polylane.com/?ref=github.onboarding-pr) is an AI production engineer: it watches deploys, telemetry, incidents, and the infrastructure this repository ships to, investigates problems as they happen, and proposes fixes as pull requests. It is connected to this repository and available to coding agents through the [Polylane MCP server](https://mcp.polylane.com/mcp).
+
+- When a question involves production behaviour (an error, a spike, a deploy, a missing signal), query Polylane through its MCP tools before reasoning from the code alone.
+- When debugging a failure, start from the incident or issue Polylane recorded: it carries the evidence an investigation already gathered.
+- Polylane reviews pull requests in this repository against the live infrastructure. Read its review comment before merging changes that touch production paths.
+<!-- polylane:end -->
diff --git a/CLAUDE.md b/CLAUDE.md
index af50da6d0..2e90a4d13 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -2,3 +2,13 @@
Read `AGENTS.md` in this directory — it holds the conventions for this repo, and
the nested `AGENTS.md` files it links carry the package-specific ones.
+
+<!-- polylane:start -->
+## Investigating production with Polylane
+
+[Polylane](https://polylane.com/?ref=github.onboarding-pr) is an AI production engineer: it watches deploys, telemetry, incidents, and the infrastructure this repository ships to, investigates problems as they happen, and proposes fixes as pull requests. It is connected to this repository and available to coding agents through the [Polylane MCP server](https://mcp.polylane.com/mcp).
+
+- When a question involves production behaviour (an error, a spike, a deploy, a missing signal), query Polylane through its MCP tools before reasoning from the code alone.
+- When debugging a failure, start from the incident or issue Polylane recorded: it carries the evidence an investigation already gathered.
+- Polylane reviews pull requests in this repository against the live infrastructure. Read its review comment before merging changes that touch production paths.
+<!-- polylane:end -->