Macmo

Macmo

AI Agent Command Center
for macOS.

  • See what your AI agents are doing.
  • Control them when it matters.
  • Give every agent an identity.
Explore MacmoView ArchitectureEarly Development

Not an AI chatbot, model, or cloud platform — a local observation and control layer for AI agents.

Agent Visibility

Your agents are scattered across terminals and IDEs.

AI agents run fragmented across terminal windows and editors. It is hard to tell which agent is working, which is waiting, and which is blocked waiting for you. Macmo is designed to make that state visible in one place.

PRD §3 Problems · §17 Main Dashboard

Agents

Concept UI
Macmo — Agents
  • Claude CodeWORKING
  • CodexIDLE
  • Gemini CLIWAITING
  • HermesOFFLINE

Concept UI — illustrative example of Macmo agent cards.

Macmo Island

Concept UI

Claude Code

WORKING
Compact

Refactoring auth/session.ts

Approval Request

Approval

Claude Code wants to execute:

npm install

Concept UI — Macmo Island is in early development.

Macmo Island

A compact floating interface that stays out of the way.

Macmo Island is a lightweight floating panel showing the agent avatar, current state, current task, and any approval request. It is designed to remain non-intrusive while keeping the important moment — a permission request — within reach.

PRD §16 Macmo Island

  • Agent avatar
  • Current state
  • Current task
  • Approval request

Universal Agent Protocol

Different runtimes. One normalized system.

Agent-specific behavior belongs in adapters. Macmo operates on normalized events and states, so each runtime becomes interchangeable from Macmo’s perspective.

PRD §5 Product Architecture · §8 Universal Agent Protocol

  1. 01

    Agent Runtime

    Claude Code, Codex, Gemini CLI, Hermes, custom agents

  2. 02

    Adapter

    Runtime-specific behavior and event parsing

  3. 03

    Universal Agent Protocol

    One normalized internal event model

  4. 04

    Event Engine

    Validated, normalized events flow through Macmo

  5. 05

    State Engine

    Source of truth for UI, avatar, and notifications

  6. 06

    UI · Avatar · Notification

    Dashboard, Macmo Island, avatars, macOS notifications

This separation is critical: agent-specific behavior belongs in adapters, while Macmo operates on normalized events and states — so adding a new runtime does not mean redesigning the core.

Human-in-the-Loop

You stay in control.

Permission handling is a first-class feature. When an agent wants to act, Macmo is designed to surface the request so you can approve or reject it — and every decision is logged locally.

PRD §15 Permission Gateway · §22 Security

Permission Gateway

Concept UI

Claude Code wants to execute:

npm install

Decision logged locally — audit trail

Concept UI — permission gateway is in early development.

  • Permission requests

    Agents request before acting

  • Approve

    Allow the requested action

  • Reject

    Refuse the requested action

  • Audit trail

    Decisions logged locally

Avatar System

Your agents have an identity.

Every agent can carry a persistent visual identity. Avatar behavior derives from the normalized agent state, so what you see always reflects what the agent is actually doing.

PRD §18 Avatar System

  • IDLE

    Neutral

  • THINKING

    Thinking

  • WORKING

    Active

  • WAITING

    Waiting

  • NEEDS_APPROVAL

    Attention

  • COMPLETED

    Success

  • ERROR

    Error

  • OFFLINE

    Sleeping / inactive

Avatar behavior shown only where defined in PRD §18.

Local-First

Your agents. Your Mac. No mandatory cloud.

Macmo V1 is designed around a local-first model. The core product does not depend on a cloud backend, and telemetry is not required.

PRD §22 Security · §23 Privacy

  • Local-first

    Runs on your Mac

  • No mandatory cloud backend

    V1 requires no cloud service

  • Local IPC

    Unix Domain Socket, local-only

  • SQLite

    Local application state

  • Keychain

    Secure credential storage

  • Human-controlled permissions

    Explicit approvals

Default model

Your Agents ↓
Your Mac ↓
Macmo

No mandatory cloud service. Telemetry is not required for V1.

Read the privacy page

Supported / Planned Agents

Agent-agnostic by design.

Macmo is built to work across agent runtimes through an adapter system. The runtimes below are planned targets for early development — none are presented as shipped integrations.

PRD §2 Target Users · §9 Adapter System

  • Claude Code

    Planned

  • Codex

    Planned

  • Gemini CLI

    Planned

  • Hermes

    Planned

  • Custom Agents

    Via GenericAdapter

    Planned

Planned targets for early development. Adapter support is not shipped yet — no integration is presented as production-ready.

Your agents.
One command center.

Follow Macmo's development

Macmo is in early development.