No coding tool found
Install and sign in to Codex or Claude Code using the same computer account that runs Drover. Return to Settings, Coding tools, and choose Check again. Signing in to Drover is a separate step.
If the tool works in a terminal but is still missing in Drover, quit the app completely, including its tray icon, and reopen it so it can read the updated environment.
Sign-in or device limit
Open Settings, Account, and read the sign-in status. If every device slot is used, remove a device you no longer use, then retry the account check. Removing a device signs that device out.
An expired sign-in needs a new sign-in. A temporary connection failure needs the account service to become reachable again; it does not mean your local work has disappeared.
Repository unavailable
Open Details beside the connection message and identify the affected repository. Check that its folder still exists and is accessible to the current computer account, then choose Try again.
If no repository has been added yet, use Getting started or Settings, Repositories. Do not treat an empty workspace as a broken repository.
Ask is unavailable
Read the message above the text box. Check Settings, Attendant, for an available model and effort, and Settings, Coding tools, for tool discovery. Confirm that a repository is connected. A disabled Send button with an empty draft is normal.
An update failed
Keep the error message and your current app version. Your current installation can still be used if the update was not installed. Check the Download page for a published build and its checksum, or send a feedback report if the failure repeats. Do not delete your local settings as a first troubleshooting step.
Runner stopped
The observed runner is no longer alive. Open the ticket and read its stage and failure, then use Restart when offered.
What the app shows: The runner is not running. Restart it to continue.
Too big
Planning stopped because the request is too large. Read the proposal, split or reduce the request to one deliverable increment with at most three acceptance sequences, then start the intended work again.
What the app shows: Too big on the ticket; Too big to plan groups these stops in Needs your input.
Needs your input
Open the ticket’s decision. Read the plan or question and the attendant’s context if present. Approve the plan only after reviewing it; answer a product question with the missing information. Use the cap guidance below for a request for more attempts.
What the app shows: Needs your input groups decisions waiting for a person.
Base red
Checks are failing on the base. Read the reported failing lanes and fix the base before choosing Retry checks. Stop if you cannot resolve it. Stopping and starting the ticket preserves the halt.
What the app shows: Retry checks permits another check; it does not fix the base.
The cap question
Read which limit was reached and the recorded failures. For an attempt or session cap, choose a finite additional allowance only if another attempt is warranted, then use Grant and resume with the displayed amount. Otherwise stop. For an outage, wait for the provider to recover before choosing Try again.
What the app shows: Grant additional reviews or Grant additional sessions in the decision view, followed by Grant with the chosen amount and resume. An outage offers Try again.