Project management your AI agent can actually use.

You vibe-code with AI agents. They write features, fix bugs, refactor code. But who's tracking what got done? Vibe PM gives you and your agent a shared board — no cloud, no API, no setup.

claude code
$ claude
Claude: I'll update the issue status to in_progress...
Writing .issues/a3f8kx2p-fix-auth-bug.md
✓ Issue updated
vibe pm● Live
Open
Add dark mode
low
In Progress
Fix auth bug
● updating...
Done
Setup CI
✓ closed

You ship with AI. You manage with sticky notes.

AI agents changed how code gets written. Project management hasn't caught up.

  • You kick off a Claude Code session, it builds three features and fixes a bug — and none of that shows up in your project tracker
  • You open Cursor, vibe through a refactor, close the laptop — next morning you can't remember what's done and what's left
  • Your issue tracker lives in a browser. Your agent lives in the terminal. They don't talk to each other.
  • Multi-session projects fall apart because there's no structured handoff between coding sessions

Your agent updates the board while it codes.

Focus on outcomes, not mechanics.

You stay in the loop without interrupting the agent

Watch the Kanban board update live as the agent works. No need to ask "what did you do?" — it's on the board.

Context survives between sessions

Every vibe coding session leaves a trail: what was planned, what was done, what's still open. Project history is in Git, not in your memory.

Planning becomes part of the prompt

Write tickets on the board, your agent reads them as structured work items. Move from "do something with auth" to a clear backlog.

No integration required

If the agent can write a file, it can use Vibe PM. Works with Claude Code, Cursor, Aider — any agent that touches files.

You plan. Your agent executes. Both update the same board.

A simple workflow that just works.

1

Open your repo in Vibe PM

Point the app at any Git project, it picks up existing issues or starts fresh.

2

Create issues from the UI

Kanban board, priorities, labels, assignees. Write tickets the way you think about work.

3

Start a vibe coding session

Your agent reads .issues/, sees what needs doing, starts working.

4

Watch the board update

As the agent writes code, it sets issues to in_progress, adds comments, marks things done. Real-time, ~500ms.

5

Commit everything together

Code changes and issue updates are just files. One git commit, one PR, one diff that shows both what changed and why.

Built for developers who vibe-code.

The AI-first developer

You use Claude Code, Cursor, or Aider as your primary coding tool. You prompt more than you type.

What changes

Your agent gets a real backlog. You get visibility into what it's doing. Sessions have continuity.

The solo builder shipping fast

You're building a side project or startup MVP. Jira is absurd for your scale. GitHub Issues is one more tab.

What changes

Project management that costs zero setup and zero context switches. Open the app, see the board.

The small team that lives in Git

Your team is 2–5 developers. You already collaborate through branches and PRs.

What changes

Issues travel with branches. PR diffs show code changes and project updates together.

A proper project management UI — backed by plain files.

File-based doesn't mean primitive.

Kanban Board

Drag-and-drop between status columns. The board you're used to from Linear.

Real-Time Sync

File watcher picks up every change in under 500ms. It's live.

Keyboard-First

Cmd+K palette, single-key shortcuts. Designed for developers.

Dark & Fast

Linear-inspired design, dark-first, minimal chrome.

The filesystem is the only API every agent already speaks.

That's the technical bet.

  • Every AI coding agent can read and write files. Not every agent can call a REST API.
  • .issues/*.md with YAML frontmatter — human-readable, grep-able, diffable
  • Version-controlled by Git automatically. git log .issues/ = full project history.
  • Branch-aware: feature branch carries its own issue state. Merges cleanly.
  • No server, no database, no auth, no account. Your data stays on your machine.
.issues/a3f8kx2p-fix-dark-mode.md
---
id: a3f8kx2p
title: Fix dark mode toggle
status: in_progress
priority: high
assignee: claude
labels: [bug, ui]
created: 2025-01-30T14:22:00.000Z
updated: 2025-01-30T16:45:00.000Z
---

The toggle doesn't persist after reload.

## Comments

### @claude - 2025-01-30T16:30:00.000Z

Fixed by storing theme preference in localStorage.

Built for the AI coding workflow. Not retrofitted.

See how Vibe PM compares.

Vibe PMGitHub IssuesLinearJira
AI agent can read/writeYes (files)APIAPIAPI
Works offlineYesNoNoNo
Data in your repoYesNoNoNo
Branch-aware issuesYesNoNoNo
Setup requiredNoneAccountAccountAccount + Admin
Free to useYesFree tierPaidPaid

From download to first issue in under a minute.

Free download. No account required.

🍎
macOS
.dmg
Coming soon
🪟
Windows
.exe
Coming soon
🐧
Linux
.AppImage
Coming soon