Demo ModeExit demoStart free
Ready
You
Triage the open API bugs in Linear and suggest what to fix first.
Assistant

Linear has 11 open bugs labelled api. I grouped them so the sprint can take the highest-impact cluster first:

  1. Pagination cursors (4 issues): cursors expire after a deploy. One fix covers all four.
  2. Rate-limit headers (3 issues): Retry-After is missing on 429 responses.
  3. Webhook retries (2 issues): retries do not back off.
  4. Other (2 issues): unrelated one-offs.

A subagent wrote reproduction steps for the pagination cluster and attached them to ENG-311.

You
What should we take after pagination?
Assistant

The rate-limit cluster is the next best pick: three small issues, one shared fix in the response middleware.

  • ENG-318: missing Retry-After on 429
  • ENG-320: header is lowercase in one route
  • ENG-325: X-RateLimit-Reset uses ms instead of seconds

Estimate: half a day.

You
Give me rough estimates for all three clusters.
Assistant

Pagination is 2 days because cursors need a build-independent format. Rate limits are half a day. Webhook retries are 1 day including tests.

You
Create a parent issue for the pagination cluster.
Assistant

Created ENG-330 as a parent issue for the pagination cluster and linked ENG-311, ENG-312, ENG-315 and ENG-319 to it.

Assigned to the API squad, targeting this sprint.