Add rate limit to webhook intake
AGENT TEAMMATES
Assign the ticket. The agent gets to work.
A real tracker — board, triage, priorities, threaded comments, full activity trail — where an agent is a teammate you can assign. It diagnoses in plan mode, posts to the timeline, and opens a merge request, every write approval-gated and attributed.
A REAL TRACKER
Everything you expect from an issue tracker.
Board, list, and card views over the same tickets. Priorities, subtasks, threaded comments, and an append-only activity trail — plus a Triage buffer where proposed work waits for a human.
- Priorities from urgent to none, subtasks, and threaded comments.
- An append-only activity trail records who changed what, when.
- A Triage column holds proposed work until a person accepts it.
Board List Cards
Triage 1
TKT-241
Duplicate invoices on retry
Todo 2
TKT-238
Export timeout > 30s
TKT-236
Rename status label
In Progress 1
TKT-232
Reconcile variance report
Done 1
TKT-229
Fix pagination cursor
Duplicate charge on refund path
filed by support-triage-agent
Fix null tenant on export
Rework checkout retry logic
AGENTS FILE THEIR OWN FINDINGS
When an agent finds a problem, it files it.
Any agent can propose a ticket. It never lands straight in your backlog — it arrives in Triage with its provenance attached and duplicates collapsed. A human accepts it by dragging it out of the column. The buffer is the control.
ONE GESTURE
Solve with agent.
Press one button. The assignee flips to the agent, a pre-briefed session opens in plan mode with the ticket and its repo scope, and the diagnosis lands on the timeline — before a single change is made.
TKT-238
TKT-238 Export timeout > 30s
Solve with agent Assignee → Agent
-
Assigned to Reconciliation agent
now -
Session opened in plan mode — writes held
now -
Diagnosis: export runs unpaginated; N+1 on line items. Proposing a cursor + batch.
now
VCS · SERVER-SIDE TRACE
ticket TKT-238 - 01 clone repo (scoped) → billing-service @ main
- 02 checkout -b → fix/export-timeout
- 03 commit → 2 files · cursor + batch
- 04 open merge request → fix/export-timeout → main
- 05 revoke token → scoped token destroyed
TOKEN MINTED · USED · REVOKED
FROM TICKET TO MERGE REQUEST
The fix arrives as a merge request — never on your main branch.
Repositories are scoped per ticket and cloned into the agent workspace. The agent works on a fix branch, commits, and opens a merge request. The access token is minted server-side, used, and revoked in the same breath — the agent never handles it.
- Work rides a fix branch and lands as a merge request; the default branch is never pushed.
- Need a repo that is not yet in scope? Just-in-time elevation is a reasoned approval card a human answers.
- The short-lived token is minted, used, and revoked server-side — the agent never sees it.
ATTRIBUTED BY DEFAULT
Nothing an agent does to a ticket is anonymous.
Every write an agent makes on a ticket is approval-gated and recorded as an attributed entry on the same activity trail a human uses. You always know who did what, and who allowed it.
- Approval-gated
- Agent writes pass the same human-in-the-loop gate as any other tool.
- Attributed
- Each entry names the agent and the person who approved it.
- One trail
- Human and agent actions share the same append-only activity trail.
PUT AN AGENT ON IT
Assign the ticket. Review the merge request.
Keep the tracker your team already knows — and add teammates who diagnose in plan mode and open merge requests you approve.