Documentation

What is TaskDrive

TaskDrive is an autonomous software engineer that connects to your Linear board and GitHub repos. It researches, plans, implements, reviews, and merges code — with human approval at every checkpoint you choose.

It retrofits into your existing setup with zero infrastructure changes: no new services to run, no new processes to manage. Point it at your Linear board, give it access to your repos, and it starts processing tickets through a five-stage pipeline. Every stage posts structured updates directly on the ticket so your team always knows what's happening.

Prerequisites

A Linear workspace where your engineering tickets live
One or more GitHub repos you want TaskDrive to work on
Access to a TaskDrive hosted plan — apply via the waitlist

TaskDrive retrofits into your existing Linear + GitHub workflow with no infrastructure changes needed. No new servers to provision, no new CI pipelines — it connects directly to what you already have.

Getting Started

1

Join the waitlist & get activated

Sign up at taskdrive.dev. Once your account is activated you'll receive setup instructions by email.

2

Connect Linear & GitHub

Authorise TaskDrive to read your Linear board and push branches to your GitHub repos. Permissions are scoped to the projects you specify — nothing outside your config is touched.

3

Add a `taskdrive.toml` config

Drop a config file pointing at your repo and Linear team. At minimum, define one [[projects]] entry. Optionally set model tiers in [models] and customise pipeline behaviour with a flow.yaml.

# taskdrive.toml
[[projects]]
repo       = "org/my-repo"
linear_team = "ENG"

[models]
# fast / normal / advanced — one-line to swap providers

4

TaskDrive starts processing tickets

Move a ticket into an active state on your Linear board. TaskDrive picks it up, runs it through the five-stage pipeline, and posts progress updates and artifacts directly on the ticket.

The Pipeline

Every ticket passes through a five-stage pipeline. Stages run sequentially; each one posts its output as a structured artifact on the Linear ticket. Human approval gates are optional — enable them per stage or disable all gates for lights-out autonomy.

1

Research

Explores the codebase, analyses related files, and posts structured findings to the ticket.

2

Plan

Reads the research and designs a phased implementation plan with file changes and test strategy.

Approval Gate

Research & Plan Review

Review the research and plan — approve to proceed or reject for revision. Skip this gate with gates_enabled = false.

3

Implement

Creates a branch, writes code using TDD, runs tests, captures visual proof, and pushes the PR.

4

Code Review

Validates against acceptance criteria, runs tests, checks scope, and delivers a PASS/FAIL verdict.

Approval Gate

Ship Review

Final human check — approve the merge or send it back for changes. Skip with gates_enabled = false.

5

Retro & Merge

Writes retrospective lessons to the knowledge base and merges the PR.

Feature Gates

Gates are optional human approval checkpoints. When a gate is reached, TaskDrive pauses and waits for your approval before continuing. You approve or reject via the dashboard, Slack, or Telegram.

Configure gate behaviour in taskdrive.toml:

# Run with all gates enabled (default)
# TaskDrive pauses at each approval checkpoint for human review
gates_enabled = true

# Run lights-out — fully autonomous, no human approvals required
gates_enabled = false

You can also customise which pipeline stages exist, what prompts agents use, and which stages have gates by dropping a flow.yaml in your config directory. The full pipeline is YAML-configurable — add, remove, or reorder stages without touching code.

Note: There is currently no dashboard UI to toggle gates. Set gates_enabled directly in taskdrive.toml.

FAQ & Learn More

What LLM does TaskDrive use?

TaskDrive runs on Claude Code with three configurable model tiers: fast (haiku), normal (sonnet), and advanced (opus). You can also swap providers via OpenRouter or bring your own Anthropic API keys. The [models] section in taskdrive.toml makes it a one-line change.

Can I customise the pipeline stages?

Yes. Drop a flow.yaml in your config directory and define custom stages, gates, and prompts. Add, remove, or reorder stages — the full pipeline is YAML-configurable. See examples/flow.yaml in the repo.

Can TaskDrive work on multiple repos?

Yes. The [[projects]] config supports multiple repos, each with its own Linear team, branch conventions, language profile, and test commands. They all run in the same daemon process.

What infrastructure do I need?

TaskDrive retrofits into your existing setup — just a Linear board and GitHub repos. No new servers, no new infra, no pipeline changes.

More questions? See the full FAQ on the landing page, or reach us at support@taskdrive.dev.