More agents.
One focus.

Keep your coding agents moving without watching every terminal.

Private beta with external testers · Local-first · Claude Code + Codex

53 seconds, recorded in the real product. English narration, subtitles on (toggle with CC).

The agents work in parallel.
Your attention doesn't.

Agents wait

One session needs a permission, another a decision, while you're focused somewhere else.

Focus breaks

Every terminal switch means reconstructing what that agent was doing.

You become the scheduler

Instead of building, you check tabs and decide which agent gets you next.

Stay in your tools.
MAICA handles the attention.

01

Attention Queue

MAICA watches your sessions locally. Permission requests, decisions, failures and finished reviews land in one queue. Normal activity stays quiet.

02

Context

Each item shows what was asked, what the agent wrote, its recommendation and the open risks. No rereading the whole session.

03

Decisions

Allow or deny, pick an option or answer in your own words. MAICA sends it back to the session, or takes you there.

MAICA is not another coding agent and does not start or schedule agents. It is the layer between you and the sessions you already run.

What the beta does today.

Now

The attention queue: every session that needs you, across repos, with what it needs and since when.

Go to session · Send to session

Jump to the right terminal tab or tmux pane, or send your answer straight into the waiting session.

Agents and Parked

All workstreams in one list: running, waiting, ready for review. Park what can wait, mark what is done.

Verified done

In a MAICA task run, a task closes only when each check has evidence, such as test output or a screenshot. Corrections go into the template for that task type.

Canary

MAICA notices when a session has lost its context and recommends a fresh one. Nothing is stopped.

Report and Coach

Report shows agent runtime, concurrency and your interventions. Coach shows what stops your rounds most often, with a ready prompt from the Toolbox.

Your code is not the product.

MAICA runs on your machine and keeps its state there. This stays local:

  • source code
  • prompts
  • agent conversations
  • repository names
  • file contents
  • git diffs
  • secrets

The beta benchmark is separate and opt-in: weekly numbers only, never development content. Details: MAICA beta privacy.

Works where your agents already run.

Supported coding agents and operating systems
Claude Code in the terminalSupported
Claude Code in the Claude desktop appSupported Go to session cannot open one specific session in the app.
Codex CLI in the terminalSupported
Codex desktop appNot supported It keeps its sessions to itself, so MAICA cannot see them.
macOSTested platform
Linux, WindowsNot verified yet

Separate terminals, tmux panes, iTerm2 tabs and git worktrees stay as they are. MAICA needs Node.js 22.18 or newer.

Run more agents.
Keep one focus.

MAICA is in private beta with external testers. Request access if you already run several Claude Code or Codex sessions at the same time.

Not a fit yet if you are looking for an agent orchestrator, an enterprise rollout or a replacement for your IDE.

No pricing yet: MAICA is not commercially released. Docs and the issue tracker for testers are public on GitHub.

Which coding agents do you use? *
Operating system *

* Required. Your details are only used to handle your beta request.

What developers ask about MAICA

Does MAICA work with the Claude and Codex desktop apps?

Claude Code in the Claude desktop app: yes. MAICA sees its sessions like those in the terminal, but cannot jump into one specific session of the app. The Codex desktop app: no. It runs its sessions privately, so MAICA cannot see them. Codex in the terminal (the codex CLI) works fully.

Is MAICA a Claude Code dashboard?

In part. MAICA gives you one place for every Claude Code and Codex session that needs you: permission requests, decisions, failures and finished reviews. It is not a live view of every agent step. Normal activity stays out of your way.

Does MAICA notify me when Claude Code needs permission?

Yes. When a session waits for a permission or a decision, fails, or finishes a review, MAICA notifies you and shows which workstream it is. A plain sound or push alert only tells you that something happened. MAICA tells you where you're needed and brings you back to that session. For the built-in options, see Claude Code notifications: hooks, bells and their limits.

Can I run multiple Claude Code agents and Codex sessions in parallel?

That is what MAICA is built for. You start Claude Code and Codex the way you already do, in as many sessions as you work with. MAICA watches them locally in the background, so you don't have to become the scheduler.

Does MAICA work with tmux and git worktrees?

Yes. MAICA doesn't replace your terminal setup. Sessions in separate terminals, tmux panes or git worktrees stay where they are. MAICA follows the workstreams and brings you back to the right one.

Is MAICA a session manager or an agent orchestrator?

Not in the classic sense. MAICA doesn't start, schedule or orchestrate your agents. It manages your attention across the sessions you already run.