What Multi Agent Manager does

What MAM tracks

Eleven surfaces, one queue.

MAM detects chats from the browser, from native desktop apps, and from your terminal. Each one shows up in the same queue with the same statuses and the same actions.

The queue

One row per chat. Everything you need on it.

Every tracked chat — browser, desktop, or terminal — gets a row in the same queue. The same four statuses, the same actions, the same filters.

Statuses

• Generating The AI is producing output. Detected from the Stop / Interrupt button on web, log-based turn markers on desktop, and process output on CLI.
• Ready The turn finished and you haven't viewed it yet. Counts toward the green badge on the floating icon.
• Waiting The session is paused on a permission gate, approval prompt, or CLI choice prompt. Needs you to make a decision.
• Idle You already saw it. Stays in the queue so you can find it again.

Per-row actions

• Go Jumps back to the right place — see the next section for what that means per source.
• Share One-click share link, copied to your clipboard. CLI sessions export to a Markdown file instead.
• Save to project A dropdown on each row lets you save the chat into a Personal or Team Project — or spin up a brand-new project inline.
• Pin Star important chats and they stick to the top of the queue, even across filter and sort changes. Pinned order persists across restarts.
• Notes A short freetext note on any row — useful for "blocked on the API key" or "waiting on Sarah's review". Carries through if you save the chat into a project.
• Tags Freetext tags on saved sessions for filtering and grouping.
• Remove Drop a row from the queue without affecting the original chat in the source app.
• Bulk select Tick multiple rows and apply Save-to-project or Remove in a single action.

Toolbar

• Filter By status, source (browser / desktop / CLI), project, or agent. Multiple filters stack.
• Sort By recency, status, or title. Pinned rows always stay at the top regardless of sort.
• Connection status A pill in the toolbar shows whether the Chrome extension is connected so you always know if your browser side is live.
• Two tabs Switch between the live Queue and your Projects without leaving the window.

How you see the queue

Always there. Never in the way.

A small floating icon stays out of the way until you need it. Pop the queue open in a tight popup for a quick peek, or pop it out into a full-size window beside your work.

• Floating icon A draggable, always-on-top icon. Snaps to the nearest screen corner when you drop it. Right-click for a context menu (Open Queue, Pop Out, Settings, Quit).
• Live badges on the icon A green badge shows how many chats are ready. An amber badge shows how many are still working. A small red dot warns you if auto-update has been failing.
• Popup window Compact and transient — opens when you click the floating icon, hides automatically when you click away.
• Pop-out window A full-size persistent window for when you want the queue beside your work all day. MAM remembers whether you prefer popup or pop-out.
• Desktop notifications When a share link is ready and the popup is hidden, you get a quiet OS notification so you don't miss it.
• Light and dark themes A theme toggle in the top-right of the popup. Your choice is saved.

Get back to your chat

One Go button. Knows where everything lives.

Click Go and MAM brings the right thing forward — the right Chrome tab, the right desktop window, even the right tab inside Windows Terminal.

One-click sharing

From any chat to a shareable link in a click.

Hit Share on any row and MAM mints a real, public share link for you. No copy-paste from the source app. CLI sessions export to Markdown instead because they're local files.

• Share a single chat The Share button on every row mints the link, copies it to your clipboard, and shows a confirmation toast. Works whether the chat is open in the browser or sitting in your queue from earlier.
• Share an entire project In any project, hit Share All and MAM mints a link for every chat in the project — concurrently where it can, serially where the app needs it — and gives you back one tidy, grouped, ready-to-paste text block.
• Markdown export for CLI sessions There's no public share API for terminal sessions, so MAM exports the full transcript to a Markdown file at the location you pick, complete with a "Show in folder" shortcut.
• One-time sign-in for desktop chats The first time you share a desktop Claude or ChatGPT chat, a small browser window pops up so you can sign in. It auto-closes the second your session is captured, and subsequent shares are silent.

What sharing produces, per app

Personal Projects

Keep your work grouped. On your machine.

Saved chats persist across tab closes and app restarts. Personal Projects live entirely on your computer — they never touch a server.

• Save chats into named projects From the Save dropdown on any queue row. Or create a project and add chats to it from the Projects tab.
• Persists across restarts Close the tab, close MAM, restart your machine — your projects and the chats inside them are still there.
• Reopen with one click From a project, click any chat and MAM jumps you back to the right place — same as the Go button on the queue.
• Description, notes, tags Per-project description and per-chat notes and tags carry over from the queue when you save.
• Quick filtering Filter the live queue to show only chats from one project — handy if you're heads-down on a single thread.
• Local-only Personal Projects are stored as a JSON file in your local app data folder. Nothing is uploaded.

Team Projects

Shared projects with real access controls.

Invite teammates to a shared collection of saved chats. Each person has a role at the project level, and each saved session has its own visibility — so a project can mix everything from metadata-only references to full read-write collaboration.

Project roles

Roles control what you can do in the project. They don't automatically grant access to every chat — that's a separate decision per session.

Per-session access

Every time you save a chat into a Team Project, you choose what each member gets. Use Simple Mode for one level for everyone, or Advanced Mode to set it per person.

More about Team Projects

• Future-member rule Every saved session also remembers what new members should get when they join. Add Sarah a month later and she immediately gets the right access to every old session, with no manual cleanup.
• Email invites Invite by email with a per-invite, one-hour-expiring link. Re-inviting resets the clock.
• Reusable invite links Generate a shareable link for the project with a default role. Disable it any time.
• Pending invitations are explicit When you sign in to an invite, you see who invited you and to what — and choose Accept or Decline. Nothing happens automatically.
• Real-time sync Members joining, roles changing, sessions being added or having their access updated — every member sees it live without a manual refresh.
• Per-tool capabilities Each tracked app declares whether it supports share links and collaboration, so the save modal only offers what will actually work.
• Save chat metadata Title, source app, environment, notes, tags, a summary, and a status snapshot at save time. The actual conversation body isn't uploaded — only the link and these metadata fields.
• Google sign-in Team Projects sign-in is Google OAuth. Your local session token is encrypted on disk.

Privacy & local-first

Most of MAM never leaves your machine.

The queue, your window positions, your tracked tabs, your Personal Projects, your recent chats — all of it lives on your computer and only on your computer. The only data that ever reaches our servers is what you opt into.

• Conversation contents stay private MAM never reads message bodies. The Chrome extension watches tab state — title, URL, ready/generating — and nothing more.
• Window titles stay local The desktop watcher reads window titles via Windows accessibility APIs to know which chat is in which window. Those titles never leave your machine.
• Chrome profile metadata stays local Profile directory names, Gaia IDs, and emails are read to route shares to the right profile when you have several. They stay on your device.
• Team Projects is the only cloud bit If you sign in, your projects, members, and saved chat metadata sync via Supabase. If you don't, nothing leaves your machine.
• Crash reporting is off by default Sentry support exists but is fully opt-in by dropping a DSN into a config file. Every event is locally scrubbed — URLs reduced to host-only, tokens redacted, cookies stripped — before anything is sent.
• Diagnostic logs are local When something goes wrong, MAM writes a log file under your local app data folder. It's never sent automatically — you choose if and when to share it.

The full breakdown is in our privacy policy.

Quality of life

The small things that add up.

• Auto-update MAM checks for updates in the background. If a download fails repeatedly, a small red dot appears on the floating icon and the Settings panel shows a banner with retry and dismiss.
• Guided first run A short wizard walks you through installing the Chrome extension and (optionally) hooking your terminal up to MAM, with live connection status indicators.
• Terminal connection panel A dedicated Settings section shows which of your shells (PowerShell, Bash, Zsh, WSL distros) are configured and lets you reconfigure or view manual instructions for edge cases.
• Multi-Chrome-profile support If you have several Chrome profiles signed into different Google accounts, MAM routes shares to the right one. Web shares race all connected profiles in parallel and the first profile with valid access wins.
• Deep-link invites Team invite emails land you in a small preview, then a single click opens MAM via mam://invite/ so you can accept in-app.
• Encrypted session storage Your Team Projects sign-in token is stored with Windows DPAPI via Electron's safeStorage.
• WSL path bridging CLI tracking handles the Windows ↔ Linux path boundary automatically, so a Claude Code session running inside WSL still gets a proper queue row.
• Per-session host detection MAM walks the process tree from a CLI session up to its host — so a Claude Code session in Cursor shows up as "Claude Code CLI - Cursor", not just "Claude Code CLI".