Use case
Manage multiple Claude Code sessions without checking every terminal
Three terminals, a VS Code window and a thread on your other laptop, and the one that matters is the one waiting for a yes. AgentMingo puts your Claude Code sessions (threads, as the app calls them) on one page in the browser, waiting ones first, with your teammates' threads alongside.
Free during the open beta. Works with Claude Code today; Codex and more are next. On macOS or Linux.
One list, waiting threads first
- Threads stopped on a permission prompt or a question go to the top.
- Each row shows the thread's title, repository and branch, its task, its pull request's status, and its tokens and cost at API prices.
- The tab title and a badge count the threads that need you, and the page can alert you while it's open.
- Switch between your own threads and the whole team's.
- Threads come from every computer you connect, in every connected repository: the terminal, VS Code, Cursor or the desktop app.
Live now
Yours:1 needs your answer1 working1 replied, your turn- Needs your answer
Add saved carts
Youacme/web · saved-carts · VS Code
Permission to use Bash · waiting 3m for your answer
Work on the branch, needs your answer
- Tokens
- 3.4M tokens
- Read from cache
- 95% cached
- Cost at API prices
- $1.57
- Working
Fix the login redirect
Youacme/web · fix-login · VS Code
Working for 12m
Work on the branch, the thread is on it
src/cart.ts is also being edited by Add saved carts (you)
git 11% of tool calls · ~1.8k tokensgit habits- Tokens
- 2.5M tokens
- Read from cache
- 95% cached
- Cost at API prices
- $1.12
- Replied — your turn
Rate-limit the public API
Youacme/api · rate-limit · Terminal
Replied 4m ago: it waits for your next message
Work on the branch, replied — your turn
- Tokens
- 1.1M tokens
- Read from cache
- 95% cached
- Cost at API prices
- $0.50
- Working
Write the migration guide
Joacme/docs · migration-guide · VS Code
Working for 26m
Work on the branch, the thread is on it
- Tokens
- 2.0M tokens
- Read from cache
- 95% cached
- Cost at API prices
- $0.90
When parallel threads touch the same files
Know who else is in the file before your branches meet
Two threads editing the same file each hear about the other. Main changing a file a thread edited, or a merge conflict on its pull request, is told to that thread.
- Your thread and Jo's both start editing src/cart.ts
- With its next message, each is told who else is in the file, and on which branch
- Main changes a file yours edited: it's told to bring that in at a good stopping point
- A merge conflict on its pull request reaches it too, waking it if it's idle (up to 8 hours after its last reply, longer while its work is open)
- Worktrees keep your own threads' files apart on one computer. They can't tell you that a teammate's thread is editing src/cart.ts too.
- With edited file paths shared (on by default), a thread gets one short note when another live thread in the repository edits a file it edited, and the Sessions page flags the overlap.
- When main changes a file a thread edited, that thread is told with its next message. A merge conflict on its pull request goes to it as something to fix. Both need the GitHub App and review results on; main's changes also need edited file paths shared (on by default).
- When two people's threads are on the same task, each hears about the other once and is asked to check with them first.
Answer from the list
Open a waiting thread's page and answer its permission prompt or question there, or reply when its turn has ended, while its computer is on. This is on per computer, through the setup command's box “Answer prompts and reply to threads from AgentMingo” (ticked by default). Some prompts still need the terminal (a subagent's, for one), and the page says so. How notices and answers work.
Alongside Claude Code's own tools
Claude Code has an agent view for the background sessions on your computer (claude agents, a research preview)[1], and Anthropic's Remote Control continues Claude Code sessions on your computer from the Claude app or claude.ai/code, several at once in its server mode[2]. Use them. AgentMingo is for your team's threads in one list, with their tasks, pull requests and review results.
Sources
Checked November 3, 2026, on each product's own pages. Products change: the links say what they say today.
- Claude Code: Agent view (claude agents, a research preview) is one screen for the background sessions on your computer. code.claude.com
- Claude Code: Remote Control continues Claude Code sessions running on your computer from the Claude app or claude.ai/code, and in server mode one process serves several sessions at once; its docs list the plans that include it. code.claude.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
Does every Claude Code session show up?
Every thread in a repository your organization connects, or one you add with repos add, on computers where you ran the setup command. Threads anywhere else send nothing about themselves.
Can my teammates see my threads?
Your organization sees each thread's title, branch, state and counts. With edited file paths shared, teammates' threads are told when they edit the same files as yours. Untick that box and your threads aren't named in their notes.
Does it slow Claude Code down?
Each hook runs a small script and sends in the background. Lookups give up after 1 second and the thread carries on.
Does it work on Windows?
Not natively yet. A computer needs macOS or Linux, Node.js 18 or newer, and Claude Code.
See every Claude Code thread in one list.
Sign up, run one command on your computer, and keep working. Free during the open beta.