5 ms·
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 d
by laxori666 9mo ago
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.
- sbarre 9mo agoHow 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..
- fragmede 9mo agoyou've already hooked up Jira access via MCP/skills jira-cli, yeah?
- sbarre 9mo agoOh 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.
- baq 9mo agothey already did, it's called 'JIRA'. not even joking.