Local-first issue tracking,
agent-native.

sneck keeps the work on your machine - instant because it's local, correct because it syncs, and open to the agents you already run.

Boards that stay instant

Every surface's database-query count is pinned in the test suite - board 54, list 48, detail 66 - so a change that adds queries fails CI before it slows your morning. At a 2,000-issue org, pages render in 6-54 ms.

An MCP server, dogfooded

Agents work the tracker natively - search, file, update, comment - through the same MCP server sneck's own backlog runs on. This page's roadmap was filed, tracked, and closed through it.

The sneck issue board at full width - status columns of issue cards, a project picker chip in the topbar, and the navigation rail on the left.

The board at 1280 - every surface below it rides the same local-first read path.

Built different, on purpose

Seven decisions you can point at - each one ships today, none is a roadmap slide.

Local-first sync

The board lives on your machine. Reads render without a round trip, writes land without a spinner, and offline is a mode - the tab keeps working and syncs quietly when the connection returns.

Team prefix refs

Each team owns its prefix and its number line: SIG-7 is the Signal crew's seventh issue, SNECK-7 the org-scope seventh - same digit, different issues, never confused. Rename a prefix and its refs re-skin without renumbering; move an issue across teams and it renumbers into the destination, project-style.

The composer

One form, every option at create: status, priority, assignee, team, project, cycle, estimate, labels, due date - plus templates for the work you repeat. Create keeps the modal open, so the next issue is a keystroke, not a pilgrimage.

The issue composer - a modal over the board where title, description, status, priority, assignee, team, project, cycle, estimate, labels and due date are all set before the issue is created.

Sprints that roll

Close a cycle with an explicit carry-over policy - drop what's left, carry it into the next box, or park it in the backlog. A recurring cadence re-arms sprints back-to-back at the length you set, and velocity and burn reads land per cycle.

Saved views

Pin the filters you actually work from. Personal views shape your own day; org-shared views put the whole crew on the same board - and both stay one keystroke away.

Forges, webhooks, imports

Link GitHub and GitLab issues both ways, fire outbound webhooks on the events that matter, and bring the backlog along from Linear or CSV - refs and history intact.

The API + MCP

A typed REST API and the MCP server share one token door - mint scoped tokens in settings and agents file, triage, and close like teammates. Included on every paid plan.

Start closing work today

Free for one crew to find the edges. Doers pay; viewers never do.