Private beta · v0.1

Tickets in.
Pull requests out.

Assign a ticket in Linear and get back a tested, reviewed pull request — while you focus on the work that actually needs you.

Ticket → PR While you sleep
You approve Every merge, if you want
0 changes To your existing workflow

Built Around Your Backlog

Whatever size your team is, the bottleneck is the same: more tickets than hands.

🧑‍💻

Solo developers

Your side project stalls every time life gets busy.

Queue up tickets before bed, review PRs over coffee. Your project keeps moving even when you can't.

👥

Small teams

The backlog grows faster than you can hire.

Hand the well-scoped tickets to TaskDrive and keep your engineers on the hard problems. Throughput scales without headcount.

🚀

Growing startups

Every sprint ends with bug fixes and chores pushed to "next time".

Let the routine work ship itself. You choose the control level — approve every merge, or run fully lights-out.

See What TaskDrive Does

A 40-second tour of the engineering pipeline and the features that turn Linear tickets into merged pull requests.

How It Works

TaskDrive watches your Linear board and autonomously processes tickets through a six-stage pipeline.

🎛️ You decide how much control to keep. Run fully autonomous end-to-end, or switch on approval gates at the plan and merge checkpoints — nothing ships without your OK.

Your Code. Your Rules.

An AI touching your repo should earn your trust. Here's how TaskDrive does.

🎚️

You choose the autonomy level

Run fully autonomous, or turn on approval gates at the plan and merge checkpoints. Approve or reject from Slack or Telegram — flip the setting any time.

🔍

Everything is reviewable

Every ticket produces a normal branch and pull request in your repo. Research notes, plans, and review verdicts are posted to the Linear ticket — a full audit trail.

🧪

Tested before it ships

Your test suite runs at implementation, code review, and again before merge. A failing suite stops the pipeline — not your main branch.

🔒

Isolated by design

Each ticket runs in its own isolated container with only the access it needs: your Linear board and the one repo the runner is assigned to.

Simple Per-Runner Pricing

One runner watches one repo. Add runners to process more tickets in parallel.

Frequently Asked Questions

What if TaskDrive writes bad code?

Nothing has to merge without you. Turn on approval gates and every plan and merge waits for your explicit OK — or reject the PR like you would any teammate's. Your test suite runs at implementation, review, and again before merge, so a failing suite stops the pipeline.

What access does TaskDrive need?

Your Linear board and the repos you connect — nothing else. Each runner is scoped to one repo and one Linear team, and every ticket runs in its own isolated container.

Do I have to change my workflow?

No. TaskDrive retrofits into your existing Linear + GitHub or GitLab setup. You keep writing tickets the way you already do; TaskDrive picks them up, works on a branch, and opens a normal PR.

Can I control how autonomous it is?

Yes — it's your call. Run fully lights-out for end-to-end autonomy, or enable human approval gates at the plan and merge checkpoints and respond from Slack or Telegram. You can change the setting at any time.

What LLM does TaskDrive use?

TaskDrive runs on opencode — a coding agent. The Starter plan uses managed GLM-5.2; the Pro plan uses managed Sonnet 5; Indie lets you bring your own key. Model selection is part of your plan, so there's nothing to configure.

Can TaskDrive work on multiple repos?

Yes. Provision a separate runner for each repository from your dashboard — each runner watches one Linear team and one GitHub or GitLab repo, with its own auto-derived language profile and branch conventions.

Is TaskDrive ready to use today?

Yes — TaskDrive v0.1 is running in production. Sign up to get started with hosted plans and priority support.

Know someone who'd use TaskDrive? Refer a friend and you both get $29 in account credit — no cap. Learn more