I did naively in CoPilot as suggested here: https://steve-yegge.medium.com/the-beads-revolution-how-i-built-the-todo-system-that-ai-agents-actually-want-to-use-228a5f9be2a9
That did not produce the expected result, but was the start of a long conversation trying to get the agent to focus on beads as a product. I finally got it to accepts that, yes indeed, beads will be useful:
Would you like to proceed with installation, review bd command documentation, or start mapping your workflow needs to beads features?
I respond:
beads is not installed
Then I did not fall into the pit of success:
- It feels wrong that beads where cloned into my project repo
- Installing homebrew and go is necessary, but build and copy to /usr/local/bin is scary
- Most output in terminal is ok, but installing git hooks is scary
I aborted after there. I use git, but don't know about git hooks. All the loops the agent run through, in speed I cannot follow, scares me.
My main blocker is that beads is cloned into my repo. I don't mind experiment with beads, but no way I will force that decision upon anyone else.
I did naively in CoPilot as suggested here: https://steve-yegge.medium.com/the-beads-revolution-how-i-built-the-todo-system-that-ai-agents-actually-want-to-use-228a5f9be2a9
That did not produce the expected result, but was the start of a long conversation trying to get the agent to focus on beads as a product. I finally got it to accepts that, yes indeed, beads will be useful:
I respond:
Then I did not fall into the pit of success:
I aborted after there. I use git, but don't know about git hooks. All the loops the agent run through, in speed I cannot follow, scares me.
My main blocker is that beads is cloned into my repo. I don't mind experiment with beads, but no way I will force that decision upon anyone else.