Skip to content
Documentation / 3 min read

Install and first ticket

Install Drover, open it, and the setup screen takes you from sign-in to your first ticket. This page says what to expect at each step and what Drover needs on your machine.

Install

Drover runs the coding tools already on your machine, so it does not install them. Two things need to be there before your first ticket:

  1. Download and open Drover

    Open the Download page, choose Download for Linux or Download for Windows, run the installer, and open Drover.

    What you see: Getting started opens with five steps and ticks each one off as you go.

The setup screen

Five steps, in the order the app shows them.

  1. Sign in

    Sign in to Drover with GitHub.

    What you see: Your GitHub login in the header. This is separate from signing in to your coding tools.

  2. Coding tools

    Drover looks for Claude Code and Codex. If one says Needs attention, open that tool, sign in as you normally do, and choose Check again.

    What you see: Found for each tool it can run.

  3. Choose your workflow

    Pick a preset: Codex only, Claude Code only, or Claude plans and reviews while Codex builds. Change models and stages later in Settings if you want to.

    What you see: The chosen preset under Choose your workflow.

  4. Add a repository

    Choose a local Git repository, or name an empty folder and Drover creates one. Confirm the target branch and the test command, such as npm test or cargo test.

    What you see: The repository card with its branch and test command.

  5. Connect a tracker, or skip it

    Connect Jira, GitHub Issues or Linear and attach it to the repository, or choose Skip and write tickets by hand.

    What you see: Connected after a passing check, or Skipped.

Your first ticket

Choose Start ticket, pick the repository, and either search your tracker or choose Write a ticket and describe one small change. Follow it in Active tickets. When it needs you, it appears in Needs your input: approve the plan, answer a question, or grant more attempts. Done means the change is on your branch and the tracker has the result.

Start with something small: one deliverable, a few acceptance checks. A ticket that is really three tickets stops as Too big before anything is built, and the proposal tells you how to split it.

Details, when you need them

Pull requests instead of landing on main: in the repository settings choose Open a pull request, which needs the GitHub CLI installed and signed in with gh auth login.

Linux AppImage: Claude Code builds and fixes run in a sandbox that needs bubblewrap and socat. The .deb installs both; with the AppImage, install them with your package manager.

Verifying a download: every file ships with a SHA-256 checksum on the Download page and a minisign signature. Save the public key as minisign.pub next to the file and run minisign -Vm FILE -p minisign.pub.