Can I vibecode Linear?

What you build

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 you need

• 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.

The prompt

A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.

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.

What you lose

• real-time multiplayer and the sub-100ms sync engine
• native mobile and desktop apps
• two-way integrations with GitHub, Slack, Figma, and Sentry
• Triage, Insights, and Linear Asks
• the interaction polish that makes people actually file the issue

Why people still pay

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.

moat: Collaboration Execution quality Integrations what a moat is

collaboration/sync/integrations

Free alternatives

Not in the mood to build it? These already exist, they are free or open source, and we checked them one by one.

Who has already built it

Starting from here is still vibecoding: the prompt is for when you want it exactly your way.

• Plane (opens in a new tab) — Open-source project and issue tracker with cycles, modules, and boards; the closest self-hosted Linear analogue. (alive)
• Huly (opens in a new tab) — Open-source all-in-one platform whose tracker module is an explicit Linear alternative. (alive)

What it costs in a year

Do you agree?

Related apps

Todoist 7 $ YES Notion 12 $ KIND OF Motion 34 $ KIND OF