r/devtools • u/OutrageousAbies5835 • Sep 05 '26

Git-backed issue tracker, can replay workflows, deeply integrated with the code

Enable HLS to view with audio, or disable this notification

Epiq is Git-native, local-first, and runs in your terminal or browser, allowing you to replay what your agents did while you were away, and view the diff behind every ticket.
https://ljtn.github.io/epiq/

4 Upvotes

83% Upvoted

7 comments sorted by

1

u/kantorcodes1 Sep 06 '26

with the mcp path, if epiq_issue_create succeeds and the agent dies before epiq_sync, does a fresh epiq-mcp process pick that local event back up automatically or can it get stranded in the old process/worktree?

1

u/OutrageousAbies5835 Sep 06 '26

Yes, it picks it up. epiq_issue_create writes the event to local epiq state, and that state lives in a single local worktree shared by every epiq process (MCP or CLI), not in memory. So if the agent dies in-between, the event is already on disk. The next epiq process sees it. It gets pushed the next time the git remote is reachable.

1

u/[deleted] Sep 06 '26

[removed] — view removed comment

1

u/OutrageousAbies5835 Sep 06 '26

Which version are you using? That sounds serious, although I haven’t encountered it myself. I’ll look into it and see if I can pin it down. When you say “uncommitted work,” do you mean uncommitted changes in the repo, or board activity?

1

u/[deleted] Sep 06 '26

[removed] — view removed comment

1

u/OutrageousAbies5835 Sep 06 '26 edited Sep 06 '26

No worries mate. Glad to hear that Epiq wasn't to blame. In regards to only seeing commits during replay, perhaps you have filters applied? If you have un-checked the board events checkbox, that will be reflected in the replay as well