5 ms·
Yeah, I think as a general direction we need to allow a useful collaboration with the agents on the issue board. This is btw why Epiq was developed, to keep th
by samuell 6d ago
Yeah, I think as a general direction we need to allow a useful collaboration with the agents on the issue board.
This is btw why Epiq was developed, to keep the board as code, git-backed, distributed (via an event log mechanism), and with the ability to replay the board, to see what agents actually did:
https://ljtn.github.io/epiq https://ljtn.github.io/epiq
- gps372 6d agothanks for sharing, going through your blog about cognitive debt.
- samuell 6d agoSorry, I might not have been clear, but the tool and blog is by @jolaflow (my brother) and I'm so far mostly involved as a reviewer and early adopter, but glad you like it. I might be biased, but I think the tool provides something really useful for agentic coding and hoping it can grow into a thriving open source project.
- neal_jones 6d agoThis looks very cool
- VulgarExigency 5d agoHow does this compare to Beads, if you don't mind me asking? https://github.com/gastownhall/beads https://github.com/gastownhall/beads
- samuell 5d agoI hope @jolaflow can chime in here eventually, but from a brief look, my impression, besides the fact that Epiq is based on git as opposed to beads where it is optional, is that Epiq seems to be much more optimized for interactive collaboration between the user and the agents. The graph visualization in beads surely is a neat thing for showing things, but the replay feature in Epiq should provide a similar understanding of what happened. But again, it seems to me Epiq is the tool that better allow the user to jump right in and collaborate with the agents on the board. (Again, this is from a brief look, so I could be missing things).