Epiq

“One benefit of persisting issues as code is traceability of intent and keeping track of vision drift.”

“agents can collaborate on issues locally without needing network access to an external tracker”

“That actually looks pretty incredible, including some features I never knew I wanted.”

“It is instant, as every write is local, synced over Git. It is built with engineers in mind.”

“It has way less fields and configurations per ticket”

“stores its state as an event graph in your repo, so it doesn't require a separate service or migration away from Github”

“If you prefer to keep things local and open source”

“an issue tracker that let's you replay the board and code”

“It stores issues as an immutable event log in your repo, so you can go back and inspect the context behind a change”

“This looks really nice and I'm definitely going to give it a go.”

“Oh shit, this looks incredible.”

“it is much more lightweight than Jira/Linear”

“It is git-native, lives in your repo alongside the code doesn’t require any external service.”

“Epiq seems to be much more optimized for interactive collaboration between the user and the agents”

“keep the board as code, git-backed, distributed (via an event log mechanism)”

“an issue tracker sourcing state from a log in state branch”

“I think Epiq does a decent job of addressing this.”

“allowing you to time-travel state in a filtered view to reconstruct what happened, when, by who”

“In practice, it's been a useful way to spot vision drift and understand why/when/how a feature changed direction.”

“It is git-native, vendor agnostic, and distributed.”

“It is also event sourced, and supports state replay from beginning to end, so very powerful for auditing workflows”

“Epiq also solves this with a git-native backend, so it is vendor agnostic and adheres to a issue-tracking-as-code paradigm”

“Epiq is a git-native (vendor agnostic) issue tracker you self-host”

“A self-hosted git-based issue tracker like Epiq seems more relevant by each day going forward.”

“focus on ergonomics (native to the terminal)”

“entirely git-backed, vendor agnostic and persists state as a versioned log in your repo”

“copycat design, which downgrade the seriousness of the project itself”

“It took me a year of on and off coding, but its been a great journey!”

“this is a viable replacement for its issue tracking”

“the installation instructions featuring "npm" as the first step, means a hard pass for me”

“The git-as-database approach is elegant”

“global npm install is a no for me”

“The TUI is so well made, it seems easily useable by anyone who seriously wants to.”

“Using user-scoped immutable event logs to prevent git conflicts is a clever architectural choice.”

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

“asking a collaborative group to all use a TUI is difficult”

“Multi-user conflicts are prevented because each user writes only to their own immutable event log file.”

“Avoiding the context switching to a web based tool is a nice plus.”

“It was born out of frustration and does just that.”

“has a more powerful UI story, being a TUI app, providing an issue board in the terminal”