Epiq, a distributed Git-based issue tracker TUI.

@jolaflow looks great. What motivated you to build this? If you wanted TUI issue tracking and CLI/MCP interfaces, I imagine there's already a lot of tools for that.To be clear, I'm really into this. I'm using a custom git-based agent and this is a viable replacement for its issue tracking.

As a web developer, the local web server UI idea sounds like the natural next step. Since you're already using Ink/React for the TUI, the component model should map well to a browser-based UI. The git-as-database approach is elegant — curious to see how it evolves.

Excellent concept

Looks good, i will try this out

> Conflict handling model: Later events take precedence when conflicts occurDo I understand correctly that if 2 people add a lot of information to one issue only one of them 'wins' and becomes visible? Or is it more subtle?If only the latter one becomes visible, how do you get to the edits of the other person and 'merge' it again?

Really elegant solution to the distributed issue state problem. Using user-scoped immutable event logs to prevent git conflicts is a clever architectural choice. Congrats on the launch!

You have my upvote because I love Git-based apps. There’s something cool about Git being an effective database with loads of free hosting options.I’d (re)consider a couple of things if you intend to work on it and make it viable for a wider audience.1. Who is it aimed for? If product managers and designers _are_ in scope e.g. you imagine full engineering teams using it, then a TUI isn’t gonna cut it. It’s a great interface choice for devs but I don’t think it’s organizationally viable to force everyone else in the terminal.2. I’d think about either having a central issues repository as a default / recommended option or creating an easy way for linking issues together across repos. To me, as appealing as it sounds to have your code and issues together, these things often evolve at a different pace. If I want to edit an issue I’m working on to add some new info or address changing requirements, I almost definitely don’t want to commit and push it with my local WIP version of the code.

> Agent interactions> The MCP server lets AI tools interact with Epiq in a predictable way.Or maybe just publish a skill for the agent to use your CLI? The agent alredy uses CLI commands to interact with git itself

It’s very slick, but I would be interested to know how separable the UI and the data layer are. I love vim but asking a collaborative group to all use a TUI is difficult. A local web server would be a nice alternative UI

There was a small surge in popularity in distributed git issue trackers a bit over a decade ago, and all of them had some sort of problem baked in to the design that made them not very good.Two weeks ago I had listed out the problems I could remember offhand: https://news.ycombinator.com/item?id=47956979It sounds like there's intentionally no attempt to handle the last one (that this is by devs for devs), and points 3 and 4 might be addressed somehow since it mentions syncing automatically. Does it store data separate from git to avoid the first two?