>>wild_e+(OP)
why should people use this as opposed to https://github.com/git-bug/git-bug?

>>khimar+Qr5
or if that's not similar enough, how about https://github.com/dspinellis/git-issue?

>>wild_e+(OP)
Nice solution, I had some success with https://www.task-master.dev/ it's a bit more complex though

>>wild_e+(OP)
I have been looking at this problem space, including beads recently.

I wasn't able to find something AI-native that supported subissues, and worked across projects. I require git worktrees on my programming work now, and I want it to be able to handle integration with systems like Linear or even GH issues (which was my preferred ticketing system before CLIs emerged)

The idea is in part, ~I have 15 minutes right now, what is the most important thing to put attention to? Be routed to the project and go immediately to work with a CLI.

I'm using Claude Code and codex for programming and administrative chores now. For example, managing the process of finding and selecting an arborist.

My main personal project, focuses on making Claude Code and Codex conversations useful (https://Contextify.sh). I use uses pure markdown (TODOS.md) for issue management and it is at its limit.

I'm less concerned about the DB's storage location. I don't think it needs to be stored with each project, but each project does need to be able to access it.

I suspect that I'll ultimately want to host it.

>>neuman+YM5
Good question though I expect it'll get buried amongst all the other comments. Maybe create an "Ask HN" post.

I asked Google/Gemini about a tutorial and it responded with several YouTube videos and also produced this subreddit: https://www.reddit.com/r/AI_Agents/

Found this too: https://nitter.net/bcherny/status/2007179832300581177#m

>>skrebb+VT5
you can use https://git-scm.com/docs/git-worktree to have many "views" of a single git repo.

For more complex environments, use multiple VMs (common to have large VMs running in AWS/GCP for development and only use your laptop or phone as a thin client)

>>wild_e+(OP)
There's also Beans, doing MD-based ticketing in your project. It's really good. (Disclaimer: I've contributed a few of the agent rules.)

https://github.com/hmans/beans

> Beans is an issue tracker for you, your team, and your coding agents. Instead of tracking tasks in a separate application, Beans stores them right alongside your code. You can use the beans CLI to interact with your tasks, but more importantly, so can your favorite coding agent! > > This gives your robot friends a juicy upgrade: now they get a complete view of your project, make suggestions for what to work on next, track their progress, create bug issues for problems they find, and more.

Much, MUCH less invasive than beads (basically just a CLI tool and a `.beans.yml` & `.beans/` in your project, and a joy to work with. CLI, TUI, labels, status, types (epic, feature, task etc.), GraphQL query interface (agents love that).

It's good.

>>wild_e+(OP)
I've found Backlog.md quite nice

https://github.com/MrLesk/Backlog.md

has a nice tui/webui for me, and mcp for the agent.

>>skrebb+VT5
Git worktrees for parallel repo clones on different branches, a worktree setup script that runs when a worktree is created (npm install etc) and vibe-kanban [0] to visually create, monitor and approve parallel work

0 https://www.vibekanban.com/

>>skrebb+VT5
Some people use git worktrees so each agent is working in a separate directory.

Some people have multiple agents working in the same directory, and allow the agents to tell each other what they're doing and which files they're editing: https://github.com/Dicklesworthstone/mcp_agent_mail