TicketBunker brings a ticket, its related branches, and the relevant code into one workspace.
Intent
Make it easier to pick up work when the ticket leaves out context: which branch contains the change, what was merged, and which files are involved.
Behavior
An ordered Git pipeline gathers diffs, merge history, and branch relationships before an agent interprets the findings. Reports distinguish observed Git facts from the agent's inferences.
Work is organized by ticket. The workspace includes file browsing, an editor, comments, and sessions that can retain the ticket's context.
Limits
Branch discovery depends on ticket keys in branch names. Inferences still need review, especially when a ticket is incomplete or the relevant work is outside the connected repositories.
Shared collaboration currently uses a SQLite reference service. PostgreSQL support is an intended direction, rather than part of that service.
Setup
The repository README contains the current setup instructions.