More agents.
One focus.
Let your agents work in parallel. MAICA tells you when — and where — you're needed.
Run Claude Code and Codex in parallel without constantly checking terminals. MAICA gets your attention when an agent needs you and brings you back to the right session with the context you need to continue.
Local-first · Claude Code + Codex · Private Beta
Running more agents is easy.
Keeping track of them isn't.
One agent is editing. Another is waiting for permission. A third finished ten minutes ago. A fourth needs a decision.
The models can work in parallel. Your attention can't.
Once you start running several coding agents at the same time, the bottleneck moves: from writing code to knowing where you are needed next.
Waiting agents
An agent can sit blocked while you're focused somewhere else.
Context switching
Every terminal switch costs time because you first have to reconstruct what the agent was doing.
Human scheduling
Instead of coding, you end up watching terminals and deciding which agent deserves attention next.
Don't manage the terminals.
Manage your attention.
MAICA runs quietly beside your existing tools. You keep starting Claude Code and Codex the way you already do. MAICA observes what happens and steps in only when a human is actually required.
- Claude Code / Codex
- MAICA watches in the background
- Human attention required?
-
No stay quietYes notify → return to the right session
MAICA is not another coding agent. It's the layer between you and the agents already doing the work.
Stay in your tools.
MAICA handles the attention.
Start your agents
Use Claude Code and Codex normally. No MAICA-specific prompt window and no new coding interface.
Keep working
MAICA observes workstreams locally in the background. Normal activity stays out of your way.
Get pulled in when needed
Permission request, decision, failure or completed review: MAICA tells you which workstream needs you.
Go straight back to the work
Answer a structured decision directly or jump back to the correct terminal session instead of hunting through tabs.
One place for the moments that need you.
Human Attention Queue
Permissions, decisions, failures and reviews from different agents are ordered by what actually needs human attention.
Context Capsules
See what was asked, what changed, relevant checks and why the agent needs you, without rereading an entire conversation.
Return to Session
MAICA brings you back toward the correct terminal, tab or agent session instead of leaving you to find it yourself.
Structured Decisions
Simple questions can be answered through MAICA and routed back to the correct agent.
Cross-agent Telemetry
See agent runtime, concurrency, human interventions, reviews and your own corrected work time across Claude Code and Codex.
Local-first
Your development workflow stays on your machine. MAICA is designed around local state rather than uploading your coding activity to a central service.
Hours worked no longer tell the whole story.
AI changes how much engineering work one developer can deliver in an hour. But most development businesses still measure value almost entirely in human time.
MAICA already captures the underlying signals of AI-assisted work: human attention, agent runtime, concurrency, interventions, reviews, checks and completed workstreams.
The longer-term goal is to turn those signals into defensible productivity evidence, without pretending that tokens, lines of code or agent runtime equal engineering value.
First: measure honestly.
Then: learn what productivity actually means.
Eventually: prove what that productivity is worth.
Productivity methodology is under development and is not part of the current beta promise.
Your code is not the product.
MAICA needs to understand the state of your development workflow. That does not mean your development content needs to become cloud data.
MAICA development data stays local, including:
Future benchmark telemetry will be separate, aggregated and explicit opt-in. Using a Free or paid plan will never automatically mean sharing development telemetry.
For developers already pushing AI coding tools hard.
MAICA is currently aimed at developers who already use Claude Code, Codex or both and are beginning to run more than one coding workstream at a time.
Good fit
- You regularly have multiple coding-agent sessions open
- You lose time checking which session needs you
- You want to increase parallelism without increasing mental load at the same rate
- You're interested in understanding what AI is doing to your real engineering productivity
Not yet
- Teams looking for centralized enterprise orchestration
- Developers looking for another autonomous coding agent
- People expecting MAICA to replace their IDE or terminal
MAICA is being built in the workflow it is designed to improve.
The first private beta is currently being dogfooded on real software-development work before external access opens.
The initial focus is macOS with Claude Code and Codex. Linux support is being validated as part of the same architecture.
What developers ask about MAICA
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.
Run more agents.
Keep one focus.
If you're already working with multiple AI coding agents and want to help shape MAICA, request access to the private beta.
Request private beta accessNo public launch yet. No lifetime-free promise. Early testers get beta access while the product is being validated.