zlacker

>This is clearly going to develop the same problem Beads has. I've used it. I'm in stage 7. Beads is a good idea with a bad implementation. It's not a designed product in the sense we are used to, it's more like a stream of consciousness converted directly into code. There are many features that overlap significantly, strange bugs, and the docs are also AI generated so have fun reading them. It's a program that isn't only vibe coded, it was vibe designed too.

Yeah this describes my feeling on beads too. I actually really like the idea - a lightweight task/issue tracker integrated with a coding agent does seem more useful than a pile of markdown todos/plans/etc. But it just doesnt work that well. Its really buggy and the bugs seem to confuse the agent since it was given instructions to do things a certain way that dont work consistently.

>>ac29+(OP)
I tried using beads. There kept being merge conflicts and the agent just kept one or the other changes instead of merging it intelligently, killing any work I did on making tasks or resolving others. Still haven't seen how beads solves this problem... and it's also an unnecessary one. This should be a separate piece of it that doesn't rely on agent not funging up the merge.

>>laxori+iF
How long until Atlassian makes "JIRA for Agents" where all your tasks and updates and memory aren't stored in Git (so no merge conflicts) but are still centralized and shareable between all your agents/devs/teams..

And also auditable, trackable, reportable, etc..

>>sbarre+lta
you've already hooked up Jira access via MCP/skills jira-cli, yeah?

>>sbarre+lta
they already did, it's called 'JIRA'. not even joking.

>>fragme+qKa
Oh I don't use JIRA currently, but I used it at a previous job.

I was sort of kidding with "JIRA for Agents", obviously using the API and existing tool you can make agents use it.

We use Github at my current job and similarly have Claude Code update issues and PRs when it does work.