TL;DR
Epiq is a new issue tracker designed for terminal users, leveraging Git for distributed collaboration. It offers ASCII kanban boards, event-sourced logs, and Vim-like navigation, aiming to streamline project management for developers who prefer command-line tools.
Epiq, a terminal-oriented, Git-backed issue tracker, has been launched, offering a visual ASCII kanban interface and distributed collaboration without relying on SaaS or browsers. This development is significant for developers seeking a lightweight, local-first project management tool integrated directly within their Git workflows.
Epiq is a vim-inspired issue tracker that renders as ASCII art, providing a kanban-style board navigable via keyboard commands. It stores work as an immutable event log, enabling traceability and deterministic replay, which is especially useful for auditing and agent workflows. The tool operates entirely within the local Git repository, using isolated worktrees and state branches to facilitate distributed collaboration without central servers or cloud services.
Installation is straightforward: users run a single command to install globally, then initialize Epiq within any existing Git repository. Once set up, users can create, move, filter, close, reopen, and synchronize issues seamlessly—either manually or automatically. Epiq’s design emphasizes speed and minimal context switching, with Vim-like navigation (hjkl) and command history, making it suitable for terminal dwellers and those who prefer keyboard-centric workflows.
The system supports conflict-aware collaboration through user-scoped, append-only event logs, preventing merge conflicts common in traditional issue trackers. An MCP server interface allows integration with AI agents and tools, enabling automated interactions with issues and workflows, further enhancing its utility for advanced workflows and agent-based automation.
Why It Matters
This development matters because it offers a new approach to project management that aligns with developers’ preferences for local, command-line tools. By removing reliance on web-based SaaS, Epiq enhances privacy, control, and speed, which can improve developer productivity. Its distributed, conflict-aware design makes it suitable for teams working in decentralized environments, potentially reducing coordination overhead and merge conflicts.
Moreover, by integrating directly with Git, Epiq simplifies workflows for teams already using Git for version control, reducing the need for separate issue-tracking systems. Its focus on traceability and event sourcing also aligns with best practices in software engineering for auditability and reproducibility.
terminal-based issue tracker software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Background
Traditional issue trackers are often SaaS-based or require web interfaces, which can introduce latency, privacy concerns, and dependency on external services. Recent years have seen increased interest in local-first, decentralized tools, especially among developers seeking more control over their workflows. Epiq builds on this trend by offering a terminal-based, Git-integrated solution that emphasizes speed, traceability, and minimal external dependencies.
While there are existing terminal tools for project management, few combine ASCII visualizations, event sourcing, and Git synchronization at this level. The project’s announcement on Hacker News indicates growing interest in lightweight, developer-centric tools that prioritize workflow efficiency.
“Epiq brings devX to project management by combining keyboard-centric navigation, Git-based collaboration, and traceable event logs, all in the terminal.”
— the developer behind Epiq
“Using Epiq feels like managing issues with vim commands—fast, local, and integrated with my Git workflow.”
— a user testing Epiq
As an affiliate, we earn on qualifying purchases.
What Remains Unclear
Details about the full feature set, stability, and scalability of Epiq are still emerging. It is unclear how well it performs in large, complex projects or how it handles conflicts in highly active repositories. The extent of support for automation and AI integration via MCP remains to be tested in diverse environments.
Vim-inspired project management tool
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What’s Next
Next steps include broader user testing, feedback collection, and potential feature expansion. The developers are likely to release updates based on community input, with possible integration enhancements and improved conflict resolution mechanisms. Monitoring adoption and real-world use cases will clarify its role in developer workflows.
As an affiliate, we earn on qualifying purchases.
Key Questions
How do I install Epiq?
Install globally with npm: npm install --global epiq. Then, run epiQ inside your existing Git repository to initialize and start managing issues.
Does Epiq require a server or cloud service?
No. Epiq operates entirely within your Git repository, using Git’s native features for synchronization and collaboration.
Can Epiq handle conflicts when multiple users edit issues?
Yes. It uses user-scoped, append-only event logs to prevent merge conflicts and ensure convergence in distributed environments.
Is Epiq suitable for large teams or complex projects?
While designed to be scalable, its performance and conflict resolution in very large or highly active repositories are still being evaluated. Community feedback will inform its future development.
What integrations are available with Epiq?
Currently, it supports interaction with AI tools via the MCP server, enabling automated workflows and agent interactions.
