AgentMingo

Use case

Ticket to pull request: following WEB-12 from brief to merge

Here's one made-up ticket, WEB-12 “Add saved carts” in acme/web, followed through AgentMingo. Each step below is something the product does today; only the names are invented.

Sign up freeLink a ticket to a pull request

Free during the open beta. Works with Claude Code today; Codex and more are next. On macOS or Linux.

Nine steps

  1. The ticket

    WEB-12 is written in AgentMingo, or it's an issue in a Jira project you follow. It has a description and acceptance criteria: “Signed-in shoppers keep their cart across devices”, “An empty cart saves nothing”.

  2. A thread starts on it

    Ana presses Start on my computer on WEB-12's page (she's on a Mac), or runs node ~/.agentmingo/reporter.mjs start WEB-12. Either way, Claude Code opens in a folder of its own on a branch named WEB-12-…, and WEB-12 moves to In progress.

  3. The brief arrives

    The thread's first message carries WEB-12's title, description and acceptance criteria, and the team's rules. Nobody pastes anything.

  4. A plan, approved by a person

    The project's workflow hands the thread its first step: plan. The plan names the repositories the work touches and whether it needs an end-to-end test. Ana approves it on the thread's page or WEB-12's page, or asks for changes.

  5. Build and test

    The next steps come one at a time: build it, run the tests, and run the end-to-end test if the plan said so. A failing test goes back to the build step, for the number of tries the workflow allows. Then the change is checked against WEB-12's acceptance criteria.

  6. The pull request

    The thread pushes the branch and opens the pull request, and WEB-12 moves to In review.

  7. Reviews and CI come back

    Review bot comments and CI failures on the pull request go back to Ana's thread, sorted. If Jo's thread edits the same file, or main changes one that Ana's thread edited, her thread hears about it.

  8. You merge

    When the status says Ready to merge, Ana merges on GitHub, or from AgentMingo as herself. When the last pull request for WEB-12 merges, WEB-12 moves to Done.

  9. What it took

    WEB-12's page shows its threads and pull requests, the tokens they used and their cost at API prices, the automatic review rounds, and the time from the first thread to the last merge.
Example
WEB-12

Add saved carts

In progress
Replied — your turnAna's thread · web-12-saved-carts

Its processone step at a time

PlanDone
Approve the planNeeds your approvalApprove
Build itNot started
Run the testsNot started
Open the pull requestsNot started
Example: a made-up task, its steps as AgentMingo words them.

Change the steps

The workflow starts from a template you can edit: add a step, change the instructions for running tests, or drop the end-to-end step. Threads report each step through AgentMingo's MCP tool or the reporter's step command, and the thread's page shows where it is.

Without a workflow, a thread on the task still gets the brief and the review results, and the statuses still move; it just isn't handed steps.

Sources

Checked November 3, 2026, on each product's own pages. Products change: the links say what they say today.

  1. Jira: A work item's key in a branch name, a commit message or a pull request's title links that work to the item, once the tool is connected to Jira. support.atlassian.com

Jira, Linear, GitHub, Shortcut and other product names on this site are trademarks of their owners. AgentMingo isn't affiliated with or endorsed by them.

Questions

Who approves the plan?

The people or roles the workflow's approval step names; viewers never can. They approve on the thread's page or the task's page, or with the Approve button in a browser notice.

What if nobody approves for a while?

The plan step waits. While its computer is listening, the thread picks up the decision even hours later: up to 8 hours after its last turn, and longer while its work is open.

Can a ticket span several repositories?

Yes. The plan names them, each one gets its own folder and pull request, and review results from all of them come back to the same thread.

What if the work isn't a code change?

Set the task to be finished by marking it done. Its threads are told not to open a pull request.

Take your next ticket from brief to merge.

Sign up, run one command on your computer, and keep working. Free during the open beta.

Sign up free