Hacker News: jolaflow

New comment by jolaflow in "Plan mode is dead"

jolaflow — Sat, 26 Sep 2026 07:31:31 +0000

Spent the past 1,5 years building a tool that might be relevant, helping keep durable task state between agent sessions. It is an issue tracker persisting state as immutable event logs, allows you to inspect workflows after the fact, lets you inspect diffs inline in the tickets and it is much more lightweight than Jira/Linear. There is no central service to integrate with, as it is Git-backed and lives with your code in your repo.

https://ljtn.github.io/epiq/

Might be worth a look if you’re evaluating alternatives to Beads.

New comment by jolaflow in "Plan mode is dead"

jolaflow — Sat, 26 Sep 2026 07:19:56 +0000

> We still haven’t solved how to help people stay oriented as hundreds of increasingly capable agents change a system at once…

Building an issue tracker that addresses this. It can replay the workflow after the fact like a movie, and pin down the parts that require human input via tagging and inline diffs in the tickets. It is git-native, lives in your repo alongside the code doesn’t require any external service.

https://ljtn.github.io/epiq/

New comment by jolaflow in "The Cost of Cognitive Debt"

jolaflow — Wed, 26 Aug 2026 22:39:05 +0000

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 enable us to express ourselves in natural language, we lost the determinism along the way.

New comment by jolaflow in "[dead]"

jolaflow — Wed, 26 Aug 2026 21:17:08 +0000

An attempt to reason about risks introduced by agentic workflows in a structured way.

New comment by jolaflow in "AI usage patterns in software teams"

jolaflow — Wed, 19 Aug 2026 10:59:12 +0000

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 reconstruct what happened, when, by who, and where intent started drifting, while also allowing you to correlate the evolution of the board with the corresponding commits.

https://ljtn.github.io/epiq

New comment by jolaflow in "Ask HN: Alternatives to GitHub"

jolaflow — Mon, 17 Aug 2026 20:49:04 +0000

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 auditing workflows.

New comment by jolaflow in "Ask HN: Alternatives to GitHub"

jolaflow — Mon, 17 Aug 2026 20:46:51 +0000

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.

New comment by jolaflow in "Ask HN: Alternatives to GitHub"

jolaflow — Mon, 17 Aug 2026 20:41:06 +0000

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/epiq/

New comment by jolaflow in "Incident with Github.com"

jolaflow — Mon, 17 Aug 2026 20:27:38 +0000

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/

New comment by jolaflow in "Ask HN: What are you working on? (August 2026)"

jolaflow — Mon, 10 Aug 2026 14:45:28 +0000

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/

New comment by jolaflow in "GitHub has alternatives, but no replacement"

jolaflow — Sat, 01 Aug 2026 17:52:42 +0000

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.

New comment by jolaflow in "How much can you delegate to agents?"

jolaflow — Thu, 30 Jul 2026 08:59:09 +0000

That is also very true, and I think time-travel capabilities would help detect that too.

New comment by jolaflow in "How much can you delegate to agents?"

jolaflow — Thu, 30 Jul 2026 08:49:44 +0000

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 wile being able to traverse the time axis helps understand how the workflow evolved.

New comment by jolaflow in "How much can you delegate to agents?"

jolaflow — Wed, 29 Jul 2026 22:54:21 +0000

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 unsupervised for longer periods of time, the biggest questions tend to be "how did it arrive at this conclusion?" and "did we drift from the initial vision?". Typically these questions are hard to answer as you only review the final state of the workflow.

I recently built an issue tracker that does offer time-traveling as a core feature. Somewhat unexpectedly this turned out to provide a much sought for overview allowing for a better workflow audit, as detailed here: https://dev.to/ljtn/vision-drift-addressing-the-next-problem...

Would be interested to hear your thoughts. I guess vision drift would classify as something that is hard to reverse, because you often don't realize it has happened until much later.

New comment by jolaflow in "Handbook.md shows that long policy documents do not reliably govern agents"

jolaflow — Wed, 29 Jul 2026 22:19:05 +0000

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" gives you a clear overview of how the workflow has evolved over time, and you can checkout previous states at will.

Wrote more about it here:

https://dev.to/ljtn/vision-drift-addressing-the-next-problem...

New comment by jolaflow in "[dead]"

jolaflow — Wed, 29 Jul 2026 19:46:36 +0000

A gimmick feature turned out to be an essential capability in agentic workflows.

New comment by jolaflow in "Agent workflow audits to prevent Vision Drift"

jolaflow — Mon, 20 Jul 2026 02:03:11 +0000

How new ways of working asks for a new generation of issue tracking capabilities

Workflow time travel to prevent agent Vision Drift

jolaflow — Mon, 20 Jul 2026 02:03:11 +0000

Article URL: https://medium.com/@jonathan.lampa1/agent-workflow-auditing-to-prevent-vision-drift-daeec505dd40

Comments URL: https://news.ycombinator.com/item?id=48973620

Points: 1

# Comments: 1

New comment by jolaflow in "Show HN: Epiq – Distributed Git based issue tracker TUI"

jolaflow — Sat, 16 May 2026 17:31:32 +0000

Thank you for the kind words!

New comment by jolaflow in "Show HN: Epiq – Distributed Git based issue tracker TUI"

jolaflow — Sat, 16 May 2026 17:31:02 +0000

Thanks! Id be happy to hear what you think after trying it out!