Skip to content

Set up Polylane #847

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
polylane wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Set up Polylane #847

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,3 +10,13 @@
- Commits carry code and the docs that ship with it. Research notes, analysis
writeups, and other non-shipping generated markdown (e.g. `docs/research/`)
stay as untracked working files — commit them only when explicitly asked.

<!-- 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.

@greptile-apps greptile-apps Bot Sep 28, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Polylane connection setup missing

If a coding agent does not already have a Polylane MCP connection, it cannot follow this instruction using the repository guidance alone. The section provides a server link but no connection steps or fallback, so production investigations may stall in environments that are not preconfigured. This is a non-blocking documentation concern.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Artifacts

Evidence from the check

  • The authored Python check reads each Git revision's agent instructions, tracked documentation, and client configuration candidates without requiring credentials.

Command output from the check

  • Running the check against the parent revision found no Polylane instruction or configured client, establishing the comparison baseline.

Command output from the check

  • Running the same check against the PR revision found the instruction at AGENTS.md line 19 but no tracked setup guidance or configured Polylane client, supporting the finding.

View artifacts

T-Rex Ran code and verified through T-Rex

- 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 -->
Loading