jolaflow

5 ms·

1.
by jolaflow 21d ago
I think what is different from the assembly -> C analogy is that we are now non-deterministic. You could almost argue that going to C increased human understanding, as we could express problems in a more human way. And while agents enabl
2.
by jolaflow 21d ago
An attempt to reason about risks introduced by agentic workflows in a structured way.
3.
by jolaflow 29d ago
Once agents run autonomously for longer periods preventing vision drift becomes as important as correctness. Epiq solves this with an architecture that supports workflow auditing, allowing you to time-travel state in a filtered view to reco
4.
by jolaflow 1mo ago
For issue tracking you may also be interested in Epiq. It is git-native, vendor agnostic, and distributed. Comes with a command line TUI, a browser GUI, mcp, and more. Also event sourced state with replay, which is super powerful for auditi
5.
by jolaflow 1mo ago
It is also event sourced, and supports state replay from beginning to end, so very powerful for auditing workflows, whether that be your own or a swarm of agents.
6.
by jolaflow 1mo ago
Epiq also solves this with a git-native backend, so it is vendor agnostic and adheres to a issue-tracking-as-code paradigm. It is therefore distributed, has a TUI + browser GUI, mcp server, and so on. https://ljtn.github.io/
7.
by jolaflow 1mo ago
In regards to issue tracking there are alternatives. Epiq is a git-native (vendor agnostic) issue tracker you self-host: https://ljtn.github.io/epiq/
8.
by jolaflow 1mo ago
A modern issue tracker enabling replay for agentic workflows (via board time-travel) and focus on ergonomics (native to the terminal). https://ljtn.github.io/epiq/
9.
by jolaflow 2mo ago
As for issue tracking, there are also other git-native alternatives out there. Epiq is entirely git-backed, vendor agnostic and persists state as a versioned log in your repo. Im its creator, for full disclosure.
10.
by jolaflow 2mo ago
That is also very true, and I think time-travel capabilities would help detect that too.
11.
by jolaflow 2mo ago
I think behavior driven development probably can make intent more explicit and standardized. However, I think they operate at different levels, or on a different axis if you will. BDD helps make each point in time easier to reason about wil
12.
by jolaflow 2mo ago
Interesting. When it comes to auditing, I think there is also another layer to be verified - the intent. We have tooling for static analysis and automated tests, but drift in intent or vision is hard to detect. After leaving agents unsuperv
13.
by jolaflow 2mo ago
I have run into the same problem, and started calling the phenomenon vision drift. I noticed that the issue tracker I built was well suited to address this problem, as it handles board time-travel. So a simple command like ":replay 4h&
14.
by jolaflow 2mo ago
A gimmick feature turned out to be an essential capability in agentic workflows.
15.
Workflow time travel to prevent agent Vision Drift(medium.com)
1 points by jolaflow 2mo ago|1 comments
16.
by jolaflow 2mo ago
How new ways of working asks for a new generation of issue tracking capabilities
17.
by jolaflow 4mo ago
Thank you for the kind words!
18.
by jolaflow 4mo ago
Thanks! Id be happy to hear what you think after trying it out!
19.
by jolaflow 4mo ago
Thank you! I too am excited about next steps. There are a lot of interesting paths to explore still, and I do agree that the web interface would be a natural evolvement.
20.
by jolaflow 4mo ago
Thanks for the kind feedback! My initial motivation was of lack ergonomics in the tools I used. I had a vision of what I wished issue tracking was like, and the tools we were using were nothing like that. In my opinion they were hard to nav
21.
by jolaflow 4mo ago
That is a known limitation as of now. Text updates are currently handled as whole chunks, so Epiq does not implement character-level CRDT merging. In the event of conflicting updates to the same text block (currently title or description fi
22.
by jolaflow 4mo ago
Thanks for the encouraging input!
23.
by jolaflow 4mo ago
Thanks for the upvote! Let me address these: 1. I envision people already comfortable with the terminal as the first to pick it up, but as someone else pointed out, a considerable amount of effort has gone into lowering the threshold and ma
24.
by jolaflow 4mo ago
Thank you for the kind words!
25.
by jolaflow 4mo ago
They are not mutually exclusive. The MCP layer is there for deterministic outcomes, because there are times and places where that matters a lot.
26.
by jolaflow 4mo ago
It's mainly about robustness and deterministic outcomes. There is a small level of noise in TUI output, and structures that are easily parsed by a human can be ambiguous for an agent (for instance column layouts). You could definitely
27.
by jolaflow 4mo ago
Good point. A local web UI is probably one of the highest priorities from here. The UI, persistence and materialization layers are already fairly separated architecturally. The current TUI is built with Ink, which is a React renderer for th
28.
by jolaflow 4mo ago
Thanks!
29.
by jolaflow 4mo ago
Thanks for input. Interesting list. A few notes on that: - Issue state is not tied to commits in the checked out repo. Events live in append-only user-scoped logs and are materialized independently of the checked out branch, so switching br
30.
Show HN: Epiq – Distributed Git based issue tracker TUI(ljtn.github.io)
91 points by jolaflow 4mo ago|48 comments

More ›