Build log. What shipped, week by week.

Scans grew up this week. A scan used to be a throwaway result you watched scroll by; it’s now a report with its own URL. There’s a scans page with filtering and bulk actions, live progress while a scan runs, topology and starter questions when it lands, and a public share link when you want to show someone outside your workspace. It works on cloud accounts and on your Datadog, Honeycomb, Axiom, and Sentry integrations.

The feed got the same treatment. It now opens with a 30-day summary of what Polylane actually did for you (issues caught, changes that caused issues, autofix PRs, anomalies resolved, each with a sparkline), a health score, and a “waiting on you” table of the decisions that need a human. And under the hood, incident threads moved onto durable workflows, so investigations survive deploys and restarts, and the built-in autofix executor now runs the open-source pi coding agent, with the full transcript readable behind every PR.

Also this week:

• Sentry alert-rule and issue webhooks now open incidents: triaged by an agent the moment they arrive, with status and verdict badges and a one-click investigate
• Recurring anomalies keep the metrics, logs, and traces captured at every occurrence, browsable newest-first, instead of only the latest
• Anomaly pages lead with sparkline metric cards showing value, baseline, and deviation, a blast-radius view, and a log summary
• Change history per resource: change signals on every node’s detail panel, and top-changed resources surfaced in the feed
• Advisories are computed on the backend, each one marked fixable in place or with guidance
• Thread reliability: stale turns are swept automatically, model capacity issues fall back gracefully, and runaway turns get cut off instead of spinning
• And as always: reliability, performance, and stability improvements

Nobody wants a thousand raw log lines dumped into the middle of an investigation. This week every telemetry query the agents run (CloudWatch, Datadog, Honeycomb, Axiom, Sentry, Cloudflare, Vercel, Fly, Render, X-Ray) gained a summary mode: the full, untruncated result gets distilled into severity, error counts, recurring patterns, and the handful of lines actually worth reading, quoted verbatim. Threads stay readable, and the agent stops drowning its own context in logs.

Connecting an account got better too. A first scan now produces a structured report of ranked risks, key metrics, and log and trace digests, with starter questions to dig in. And for Cloudflare, a new modal pre-fills every permission Polylane needs and lets you choose between read-only (investigate and explain only; changes only ever land as PRs) and full access, so nobody has to hand-pick API token permissions again.

Also this week:

• Resource tiers re-classify automatically every day, and you can now override any resource’s tier by hand (overrides are pinned) or re-run classification for a whole account
• Every anomaly gets a one-click investigate that opens an incident thread, with dedupe so the same anomaly never spawns duplicates
• AI-suggested starter questions now appear on changes, check-run evaluations, and individual resources, not just after connecting
• polylane automation create and POST /automations accept custom triggers, instructions, and tools, so you can build automations no template covers
• A check-run slideover to inspect a single evaluation’s metrics, logs, and traces, with investigate and question actions inline
• Per-resource monitoring now gathers structured evidence: top and new log templates, severity totals, error and fault rates, and p50/p95/p99 per operation
• One-click repair for broken Mermaid diagrams in resource wikis
• And as always: reliability, performance, and stability improvements

Connecting an account finally has a proper moment. Instead of dropping you back on a dashboard, Polylane now lands you on a page that explains what it can see in the account you just connected, kicks off a first scan, and offers three tailored questions worth asking the agent. The first five minutes went from “now what?” to an actual conversation about your infrastructure.

The other theme this week is trust. When an agent wants to perform a mutating action, the thread now shows you the method, path, body, and reason, and waits for your approval, with deletes flagged as destructive. And every incident now declares where it stands at the end of each agent turn (needs human action, needs a decision, awaiting a change, failed, or resolved), so you can tell at a glance which investigations actually need you.

Also this week:

• Every monitoring pass is recorded as a check run (healthy, breached, or stable), giving each resource a timeline of evaluations you can inspect, plus a manual trigger
• Resources are automatically classified into tiers 1–4 by operational criticality, using topology, traffic, and recent changes; tiers now drive how anomalies are prioritised
• AWS sync gained Kinesis, KMS, Secrets Manager, and Service Discovery
• You can discover and link GitHub repositories to a cloud account, tying the code to the infra it runs
• Rate limiting and request coalescing landed across every provider client, so investigations stop getting throttled by provider APIs
• Change intelligence now maps provider change events to the specific resources they touched, rendered in the feed
• A rolling 24-hour view of incident usage against your workspace limits
• And as always: reliability, performance, and stability improvements

Autofix opened up this week. You can now connect Cursor and route autofix pull requests through its cloud agents instead of the built-in one: when an investigation ends at a line of code, Polylane hands off the fix and Cursor opens the PR. Pick a default executor per workspace in Settings → Integrations.

Automations got easier to start with, too. There’s now a catalog of pre-built templates, with the trigger, agent instructions, and actions already wired, installable in one step from the console, the CLI (polylane automation from-template), or the API. Templates are filterable by category and provider, and only enable actions for providers you’ve actually connected. Alongside it, new triage controls give you a master switch plus per-alert-rule toggles on every cloud account and integration, so you decide exactly which alerts Polylane picks up and investigates.

Also this week:

• Much broader Cloudflare coverage in the graph: zones, load balancing, WAF and security rulesets, Tunnels, Spectrum, Access, Stream, Images, and more Workers resources
• Cross-cloud edges: a DNS record on one provider pointing at a resource on another now shows up as a real edge in the graph
• Quieter anomaly detection: a deterministic backstop drops isolated spikes and near-zero-baseline noise before triage, detection respects which direction is actually bad per metric, and change-record anomalies dedupe within 24 hours instead of re-paging
• The Changes tab shows impact at a glance: an impact badge, risks, post-change verification, and affected resources as chips
• Custom LLM endpoints now list the models they actually advertise, so you pick from real models instead of typing IDs
• OAuth client secrets can be rotated without recreating the client
• And as always: reliability, performance, and stability improvements