Introduction

If you've been running cron + claude -p (or a Codex script, or a Cursor Automation, or a hand-rolled MCP server) and it's starting to feel like infrastructure, Mobius is what you were probably about to build.

It's an agent automation platform. You define automations as ordered steps, attach triggers (cron, Slack/GitHub/Linear/email events, inbound webhooks), and let runs execute durably across restarts, human approvals, and multi-minute sleeps. Each run is a real, inspectable record with a state machine, an event stream, and an audit trail.

trigger fires
  → agent step (bounded turn with tools)
    → action step (worker or platform-provided)
      → interaction step (human approval)
        → run completes with artifacts

That's the whole product surface, more or less. The rest is what you'd expect from infrastructure: persistence, concurrency policies, retries, secrets, roles, audit logs.

How you'll interact with it

Three surfaces, depending on what you're doing:

• The app (/app/projects/{handle}) for building automations, watching runs, approving interactions, and managing access.
• The mobius CLI for everyday operations: starting runs, streaming events, registering workers, rotating secrets. Install instructions and the full command list live in the mobius repo.
• The SDKs and HTTP API for embedding Mobius in your code. See the interactive API reference when you need a specific request shape.

If you're not sure where to start, the CLI is usually the right answer.

Picking the next page

• Want to see it run? Quickstart. Sign in, install the CLI, start an automation.
• Want the product model? Start with Automations, then Runs.
• Building a worker? Workers covers the decision points (concurrency, queues, environments).
• Writing API code? API overview, or jump straight to the interactive reference.

Where things live