Epiq
Distributed Git based issue tracker TUI
Details
- External ID
- 48155570
- Source
- HN
- Company
- —
- Product
- Epiq
- Website domain
- github.io
- Launched
- May 16, 2026
- Cohort
- —
- Upvotes
- 91
- Upvotes percentile
- 0.8966074313408724
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
Issue trackers typically live outside of your workflow, with poor ergonomics. Epiq aims to solve that, bringing issue tracking into your terminal. Multi-user collaboration is achieved via git using user-scoped immutable event logs that converge in memory. Put my all into it. Let me know what you think.
Enrichment
- Theme
- git and repository workflow tools
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- distributed git-based issue tracker
- Manually corrected
- False
Could you build this?
Partial Creating a standard TUI is easy, but implementing a robust distributed CRDT/event-sourcing model that reliably converges conflict-free via user-scoped Git commit histories requires non-trivial distributed systems engineering.
What it would actually take: A real version requires building a local event-sourced store with conflict-free convergence (such as CRDTs or operational transforms) mapped deterministically to Git reflogs/branches and worktrees. The core challenge is guaranteeing convergence across out-of-order pulls, concurrent agent edits, network partitions, and merge conflicts without corrupting the issue state. This demands specialized knowledge of distributed systems, convergence invariants, and deep Git plumbing internals.
Discussion
20 comments analyzed.
Competitors mentioned: Git-based issue tracking projects (historical ETF flow data tools), MCP (Model Context Protocol) servers, Traditional issue tracking tools (Jira, GitHub Issues, etc.), Custom git-based agents
Concerns raised: Copycat design reduces project seriousness, MCP has high token overhead and isn't pipeable, Lacks enterprise security and compliance features, npm dependency as installation first step is problematic, Browser can't execute git commands from local HTML files
Feature requests: Add agent-friendly output flag/option, Web/browser-based UI for TUI interface, Diff/split-pane view for comparing previous versions, Enterprise trust center/compliance verification
Competitors
Other products that read as similar to this one — 74 launches clear the similarity bar, closest 8 shown.
Attention rank: #7 of 75 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 194 days after the earliest competitor.
- Effective Git · hn · 2026-03-01 · 37 upvotes · similarity 0.45
- Serie · hn · 2025-11-03 · 18 upvotes · similarity 0.44
- 49IDE · hn · 2026-08-08 · 11 upvotes · similarity 0.44
- 49Agents · hn · 2026-04-28 · 21 upvotes · similarity 0.41
- LiveIssues · ph · 2026-09-30 · 1 upvotes · similarity 0.40
- Ec · hn · 2026-02-04 · 18 upvotes · similarity 0.39
- Git-native-issue · hn · 2026-02-24 · 9 upvotes · similarity 0.38
- Lazyworktree, a TUI manager for Git worktrees · hn · 2026-01-03 · 9 upvotes · similarity 0.38
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.