Epiq: Git-based issue tracker with TUI for terminal workflows

What it does

Epiq is an issue tracker designed to work within terminal workflows. It uses Git as the underlying storage system, with issues stored as immutable event logs that sync across users. The tool offers both a terminal interface with keyboard-first navigation and a browser GUI. Issues can be tracked, moved between swimlanes, tagged, and commented on directly from the command line or web interface. Code changes linked to issues appear as diffs within the ticket itself when commits are prefixed with the issue reference.

Who it is for

Epiq targets developers who work primarily in the terminal and want issue tracking integrated into their existing Git workflow. It is also positioned for teams using AI agents to manage sprints, since the tool includes an MCP server that allows agents to interact with the board using the same event logs. Teams seeking to audit agent activity and replay what happened during unattended workflows appear to be a key audience.

Pricing

The site does not show prices.

How it stands out

Epiq diverges from centralized services by storing project state within the Git repository itself. Issues sync via Git rather than a managed platform, meaning no account is required and data stays independent. The tool emphasizes keyboard-first ergonomics with vim-like navigation and command completion. A notable feature is time travel: users can scrub the board timeline to see what changed at any point in the past, useful when agents run unsupervised. The terminal is a first-class interface, not an afterthought. Epiq is open source, unlike most commercial competitors.

What a founder should check

First, verify whether developers actually want issue tracking outside their repository or if the friction of learning yet another tool outweighs the convenience of staying in the terminal. Second, assess switching costs from incumbents. Jira and Linear have deep integrations with CI/CD pipelines, notification systems, and project management practices that Epiq would need to replicate before teams abandon them. Third, evaluate the durability of Git-based syncing at scale. Conflict resolution through append-only logs works in theory, but whether it handles messy real-world collaboration patterns—simultaneous edits, network delays, offline work—without user pain remains unclear.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.