Where the work happens
Drover is a desktop app for Linux and Windows. Sign in with GitHub, add a repository and pick a ticket from Jira, GitHub Issues or Linear, or write one by hand. The free open beta is the whole app.
Your code stays on your machine. Drover checks the ticket out into its own worktree, runs the coding tools signed in on that computer, runs your test command, and lands the result on your branch. It keeps working from the system tray when the window is closed, and About offers the update when a new release is out.
Following a ticket
Tickets shows what is queued, Active tickets what is running, and Needs your input what is waiting on you. Open a ticket and four tabs tell the story. Overview is the stage it is on, what it is doing and why it stopped if it stopped. Plan is the plan it is working from and the review that plan went through.
Agent log is what each session did, stage by stage: the messages, the tool calls and what came back, the files it changed. Changes is the commits and diffs, grouped by the task of the plan that produced them, so you can read a diff next to the reason for it.
Usage & stats counts sessions, attempts, fix rounds, reviews and findings for each repository, so you can see which parts of your workflow earn their keep.
Where it asks for you
Five things come to you in Needs your input: approve the plan, answer a question the planner could not settle from the ticket, grant more attempts when review keeps sending the work back, retry the checks after Base red, and try again after a provider outage. Plan approval can go to the attendant instead, with Let the attendant decide in Settings.
Between those, Drover does not interrupt. There is no prompt for each file edit or command. A session gets the plan, the repository and your test command, and its work comes back as a review and a diff rather than a stream of questions.
Ask, in the app header, is for the questions you have: what happened while you were away, why a ticket is waiting, what the reviewer found. It reads the same records you can open and cites them. When you ask it to do something, it proposes the commands and runs them only after you confirm.
Settings worth knowing
Appearance offers Light theme, Dark theme and Match device theme. Running tickets sets one parallel limit across every repository; it starts at one ticket at a time and goes up when you want the queue to run wider.
Attendant chooses the model and effort for Ask and for the decisions made while you are away. Account lists your machines; an account can be signed in on three at once, and revoking one signs it out. Close to tray, in About, is on by default.
From a terminal
The driver that does the work also ships as the drover command line tool. It reads and writes the same records as the app, so a ticket you queue from a script or a terminal shows up in Active tickets like any other.