litpm is a local tracker for a team: issues are markdown files, projects are folders, and the dashboards are read from them. Everyone works on one server or through git. Mention an agent and it joins the thread under its own name, and litpm stays out of its way.
A Linear-grade tracker over a folder of markdown. The issue on the left is the file on the right, and either one can change first. Everyone on the team sees the same files.
---
title: Launch the new checkout
status: in_progress
priority: urgent
labels: [feature]
milestone: checkout
assignee: Nancy
due: 2026-09-29
---
Restaurants still order by phone because the web
checkout asks for everything again on every order.
Ship a checkout that remembers the customer and
takes a card.
## Done when
- [x] Saved delivery addresses (NW-2)
- [ ] Card payments through the bank's gateway (NW-3)
- [ ] Confirmation email with the picking slip
- [ ] The volume discount shows on the total
## Comments
### 2026-09-09 15:42 - Andrew
The gateway sandbox is up; test cards are in the
shared vault.
### 2026-09-13 11:34 - Nancy
Pilot customers confirmed: Bottom-Dollar Markets,
Ernst Handel and eight more. They start on the 20th.
Open an issue in the app or in any editor. The file is the truth, and whoever changes it, the rest of the team sees it live.
Milestones, health updates and a progress graph roll up from what is inside. Turn on initiatives when you need a layer above.
Run one litpm for the team and send invites, with roles and who is typing. Or keep the workspace in a repo and let commits carry it.
Nothing to maintain: the dashboards are read from the same files. Who has what, what is at risk, what is due, and how fast it is moving.
Pick a chip and see their open work, what is in progress and what got done this week.
Started, at risk, off track, due in thirty days, at a glance and in the list.
A saved filter is a card with its count and its split by status, shared in workspace.md for everyone.
Mention an agent in a comment the way you would a teammate. It reads the issue, does the work, whether that is a plan, a draft, a check or a fix, and answers in the same thread under its own name. Open the run to watch it think and to approve what it asks.
Claude Code, Codex, Grok, Cursor, Gemini and more, each under its own name next to the people. Every run gets its own litpm command, so what it writes is signed by it.
Supervised asks before every change; full access never asks. Approvals and questions land in the thread, and the badge shows who is waiting on whom.
litpm doesn't wrap anyone's agent in a framework or steer how it works. It starts the program each person already runs, with their own login, and hands it one skill: the litpm CLI.
Run litpm on one machine and invite the team, with member and viewer roles and presence. Or keep the workspace in a repo and let commits carry it.
Markdown with a little frontmatter. Anyone can open it, grep it, back it up, or take it along.
Link a codebase and each commit shows up on its issue. A commit that says Fixes NW-5 closes it, and pull requests on GitHub or GitLab are tracked to merge.
Local-first. Nothing hidden.
What you see in the app is what's on disk. Your agents see the same.