Epiq: Distributed, Git-Based Issue Tracking for the Terminal

Project management often feels like a chore for developers—a constant cycle of switching between the IDE, the terminal, and a browser-based SaaS tool. Epiq aims to eliminate this friction by bringing issue tracking directly into the terminal, treating project management as a first-class citizen of the development environment.

By leveraging Git as its synchronization layer and an immutable event log for state management, Epiq provides a local-first experience that removes the "SaaS ceremony" and keeps issues living alongside the code they describe.

A Terminal-Native Approach to Flow

Epiq is designed for "terminal dwellers" who prioritize keyboard efficiency and minimal context switching. The interface is a TUI (Terminal User Interface) that renders as ASCII, utilizing vim-like navigation (hjkl) to move through boards, issues, and swimlanes.

Key features focused on developer experience include:

• Keyboard-Centric Navigation: Full support for vim movements and command history.
• Command-Line Interface: Users can perform actions via a command bar, such as :new issue to create work or :filter to narrow the board.
• Local-First Interaction: Edits are instant because they happen locally, with synchronization occurring explicitly via :sync or automatically in the background.

The Architecture: Git and Event Sourcing

Unlike traditional issue trackers that rely on a central database, Epiq uses a distributed model. This approach solves several common problems associated with distributed state:

Git as the Transport Layer

Epiq uses Git under the hood, employing isolated worktrees and state branches. This allows teams to collaborate on issues without needing a dedicated central service. The repository becomes the source of truth for both the code and the project management state.

Immutable Event Logs

To prevent the dreaded merge conflicts that typically plague text-based project management files, Epiq implements an event-sourced model. Changes are appended as immutable events in user-scoped logs. These events are replayed deterministically to converge the current state of the board in memory.

As noted by community member @SidVikJay, this is a "clever architectural choice" to handle the distributed issue state problem, ensuring that the system remains traceable and conflict-aware.

AI and Agent Readiness

Modern development is shifting toward AI-assisted coding. Epiq is built with this in mind by providing an MCP (Model Context Protocol) server. This allows AI agents to interact with the issue tracker in a predictable, structured way, enabling agents to not only write code but also manage the backlog and update issue statuses autonomously.

Community Perspectives and Trade-offs

While the technical implementation of Epiq has been praised, the Hacker News community raised several important points regarding its viability in a broader organizational context.

The "Devs for Devs" Challenge

One of the primary critiques is that a TUI-only interface may limit the tool's adoption to engineers. As @goyozi pointed out, if product managers and designers are intended to be part of the workflow, a TUI is likely a barrier:

I don’t think it’s organizationally viable to force everyone else in the terminal.

To address this, several users suggested the implementation of a local web server as an alternative UI, which would allow non-technical stakeholders to view and manage the board without leaving their browser.

Decoupling Issues from Code

Another point of contention is the tight coupling of issues to the git repository. Some developers argue that project management state evolves at a different pace than code. @goyozi noted that updating an issue's requirements shouldn't necessarily require a commit and push of a local WIP (Work In Progress) version of the code.

Tooling and Installation

Some users expressed strong preferences regarding the distribution method, specifically criticizing the reliance on npm for global installation. This highlights a recurring tension in the developer community between the convenience of the Node.js ecosystem and the desire for single-binary distributions.

Summary

Epiq represents a bold experiment in returning project management to the developer's local environment. By combining a vim-inspired TUI with the power of Git and event sourcing, it offers a high-velocity alternative to the heavy SaaS tools that dominate the industry. While the challenge of scaling this workflow to non-technical team members remains, its architectural approach to distributed state makes it a compelling tool for solo developers and small, highly technical teams.