Can AI replace Linear?

01What it costs

Checked Aug 14, 2026 · source: linear.app.

Hidden costs: Every unsuspended workspace member is billable; annual plans receive monthly seat true-ups and removals create invoice credits rather than cash refunds. Linear's AI agents use separately prepaid credits: ad-hoc purchases start at $10 and auto-reload starts at $50.

02Could AI build it for you?

The core job: Local SQLite issue tracker with prefixed IDs, statuses, priorities, labels, a drag board, rolling two-week cycles, a command palette, and a script that pulls GitHub issues in.

What a working version needs:

• local or hosted database
• GitHub personal access token for issue sync
• a box the team can reach if more than one person uses it

Buildable for one person, unbuildable for a team; the moat is agreement, not features.

03What you'd give up

An issue tracker is only worth anything when everyone uses it, and people only use one that never makes them wait. Linear sells speed and shared context, not features: the whole team sees the same board update instantly, GitHub PRs close issues on merge, and the roadmap stays honest because filing is faster than complaining. A solo copy tracks your own work fine and settles no arguments.

04Free and cheaper alternatives

05The build prompt

Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.

Build me a personal issue tracker to replace Linear. Requirements:

- A local web app: Node + Express + better-sqlite3, server-rendered, dark, bound
  to localhost. One SQLite file I back up.
- Issues have an auto ID with a team prefix (ENG-142), a Markdown body, a status
  (backlog, todo, in progress, in review, done, canceled), a priority (urgent to
  none), labels, and a point estimate.
- Keyboard-first: c creates, s status, p priority, l labels, / searches titles,
  bodies, and comments with SQLite FTS5, cmd+k opens a command palette for all
  of it.
- Three views: My Issues, a board with drag between columns, and the current
  cycle, a two-week window with a remaining-estimate burndown. On its last
  day, unfinished issues roll forward, done ones archive.
- node scripts/sync-github.js (octokit, token and repo list in .env) pulls open
  GitHub issues in, keyed on issue number so re-runs update instead of duplicate.
- Pressing b copies a branch name (me/eng-142-short-title) to the clipboard.
- Comments and a per-issue activity log. No accounts, no telemetry, nothing
  leaves the machine except the GitHub calls.
- Out of scope: multiplayer, mobile apps, and writing back to GitHub. Skip auth
  and deploy config, this runs on my machine.
- README: how to run it, where the SQLite file lives, and the GitHub token scope.

06Open-source starting points

• Plane: Open-source project and issue tracker with cycles, modules, and boards; the closest self-hosted Linear analogue.
• Huly: Open-source all-in-one platform whose tracker module is an explicit Linear alternative.