Good question. Atlassian MCP provides access to Jira. Anabranch focuses on orchestration, deciding when to act, estimating complexity, and attempting to automatically open PRs for low-complexity tickets.

The goal isn’t to replace existing agent setups, but to explore whether the “boring majority” of tickets can be automated without manually going into the IDE, prompting, waiting for a result, opening a PR, waiting for a review of a second team-member. It is asynchronous by nature, and you just need to review it. I would argue that at some points agent would be so good that you would trust it to auto merge the result as well.

It’s still experimental, and part of the project is validating how reliable this approach can be in practice.

Re: README tone agreed. It was auto-generated. I’ll update it to be more neutral.

I think you will find that people don't want an Ai per use case, but one Ai that can do it all. That's the whole premise, right?

What you built is probably the equivalent of config and markdown in openclaw, do you think?