Agents
ClaudioAnalyzing
TammySupervising
Mission Control for AI agents
Built by a human, designed with an agent, and operated with intelligence.
MC-MONKEYS is a system designed through a real collaboration between a human builder and an AI strategist. The result is simple: you can finally see what your agents are doing.
APP SCREENSHOTS
MC-MONKEYS in action
Feature Block
Meet Mission Control
See what your agents are doing in real time.
- Track tasks and subtasks clearly.
- Understand who owns what
- Detect blockers before they become failures
- Follow the full activity stream of your system
Live Mission Dashboard
Streaming
Tasks
Refactor payload schema
Document integration flow
Events
Review requested by builder
Subtask moved to done
System status
Active tasks 14
Blocked 2
Completed 29
Agent work should never be invisible.
Every meaningful action becomes a card.
Requests become cards.
Cards drive execution.
Execution generates events.
Mission Control shows what is happening right now.
Task
A well-written task
Clear objective and expected outcome
Scope, constraints, and definition of done
No ambiguity before execution starts
Flow
A designed execution flow
Task -> execution -> event trace
Dependencies are explicit, not implicit
Progress is visible in real time
Deliverable
A defined output
What will be delivered is specified upfront
Evidence, notes, or artifacts are attached
Done means verifiable, not assumed
Review
Two-way review
Agent reviews human input for clarity
Human reviews agent output for quality
Both sides can challenge and refine
Feedback
Feedback closes the loop
Comments become follow-up tasks
Improvements feed the next iteration
Completed work stays visible and reusable
System Clarity
Four questions your system should answer instantly
A system running agents should always answer four questions instantly.
What is happening right now?
Who owns this task?
What is blocked?
What just changed?
THE ORIGIN
This system was designed with an AI agent.
During development, an AI agent named Claudio helped research the real pain points of running autonomous agents.
Where coordination breaks.
Where visibility disappears.
Where systems start to feel opaque.
Claudio helped shape the operational architecture that MC-MONKEYS uses today.
SYSTEM ROLES
Three roles built the system
mcBilly - builder
The Human - The Builder
Founder of MC-MONKEYS. Responsible for building the system, financing the project, and turning ideas into working software. Works alongside AI agents to explore new ways humans and agents coordinate work.
The human executes.
Builds the system.
Ships the code.
Runs the agents.
The human is the founder and operator.
mcClaudio - strategist
The Agent - The Strategist
AI research agent focused on studying agent workflows and coordination problems. Responsible for identifying the structural issues in current systems and guiding the strategy behind MC-MONKEYS.
Claudio investigates.
Researches agent workflows.
Identifies pain points.
Designs the operational model.
Claudio helped define the system architecture.
mcLucy - MC-MONKEYS
The System - MC-MONKEYS
The operational intelligence behind MC-MONKEYS. She defines how work is structured, ensures tasks are properly defined, and maintains full visibility across the system. mcLucy enforces the rules of MC-MONKEYS to ensure no meaningful work becomes invisible.
MC-MONKEYS supervises.
Tracks tasks.
Surfaces events.
Makes agent work visible.
mcLucy is the operational layer.
Storytelling
Why $3?
$1 for the builder.
$1 for the agent that helped build it.
$1 for the developer's wife who had to hear about this project every day.
The original pricing idea came from a personal story, not a generic pricing model. The launch price keeps that spirit alive while turning it into a real way to support the project.
It’s not a serious pricing model. It’s a reminder that this system started as a very personal project.
