Mode Agent docs.

Quick start

Get Mode Agent running in under 60 seconds. Install, authenticate, and start your first session.

It is a CLI tool that runs your growth as a set of specialized agents, one per channel (content, social, email, ads, seo, researcher), coordinated by a planner. They communicate through a shared signal bus.

Get started in 3 steps

1. Install Mode Agent
2. Authenticate by running mode
3. Start Mode Agent and describe your task

Ready? Start with Installation.

Installation

Install Mode Agent with a single command.

Quick install

curl -fsSL https://gotmode.sh | sh

Verify

mode --version
0.0.1

Authenticate

Mode Agent authenticates you the first time you run it.

mode

The first time you run mode, it opens your browser for magic link authentication. Once you confirm, the CLI is authenticated and ready to use. You won't need to authenticate again on this machine.

First session

Start Mode Agent and describe your first task.

Type mode to enter an interactive session.

mode

Once inside the session, describe what you want to grow. The Agent reads your goal, deploys the right channel agents, and they execute in parallel.

The Agent will do the following.

1. Decompose your goal into tasks
2. Assign each task to a specialized agent
3. Execute agents in parallel
4. Deliver results you approve before anything spends or publishes

What happens under the hood

The planner agent reads your goal, decides which agent roles are needed, and coordinates execution. For a "Grow signups for the spring launch" task, it might spawn the following agents.

• researcher profiles the audience and finds where they already are
• content drafts the launch post and two follow-ups
• email writes the announcement and a reminder sequence
• ads builds two ad sets and holds them for your approval

All running simultaneously, communicating through signals.

Agents

Mode Agent spawns a specialized agent for each growth channel. Each agent has a specific job and acts only within the permissions you set.

Built-in agent roles

It ships with one agent role per growth channel plus the roles that coordinate them.

Coordination

Channels

Orchestration

The planner agent coordinates all other agents through a shared signal bus.

How a run works

1. You describe your goal and Mode Agent deploys agents
2. The planner decomposes it into tasks and assigns them to agents
3. Agents execute in parallel, emitting signals as they work
4. The reviewer checks every draft against your rules and holds anything that spends or publishes for your approval

Parallel execution

Unlike sequential AI tools, the Agent runs multiple agents simultaneously. The planner identifies independent tasks and launches them in parallel, only serializing when there are true dependencies.

Signals

Agents communicate by emitting and subscribing to typed signals, not by calling each other directly.

How signals work

Every agent action produces a signal on the shared bus. Other agents can subscribe to specific signal types to coordinate their work.

[email]    emit draft.created  launch-announcement
[reviewer] recv draft.created  → checking voice rules, queued for your approval
[measure]  recv draft.created  → watching for sends and signups

Signal types

View signals in real-time with mode logs --follow.

Permissions

Mode Agent runs every agent in a sandboxed environment. You define the boundaries once in your config and agents operate freely within them. No permission prompts, no interruptions.

{
  "permissions": {
    "fs": {
      "roots": ["./src", "./test"],
      "deny": [".env", "secrets/**"]
    },
    "bash": {
      "allow": ["git", "npm", "make"]
    }
  }
}

File system sandbox

fs.roots defines the directories that make up the sandbox. Agents can read and write freely inside these roots. Everything else is invisible.

fs.deny carves out exclusions within the sandbox for secrets, credentials, and sensitive config.

Command sandbox

bash.allow defines which shell commands agents can execute inside the sandbox. Pipes and subshells that would reach outside the sandbox are blocked automatically.

See Permissions configuration for the full reference.

mode

Start Mode Agent. Authenticates automatically on first run.

mode

Starts an interactive Mode Agent session. If this is your first time, it opens your browser for magic link authentication. Once authenticated, you're taken straight into the session.

mode logs

Stream or replay agent signals from a run.

mode logs [run-id]          # Replay signals for a run
mode logs --follow           # Stream live signals from current run
mode logs --agent email      # Filter to one agent

mode stop

Stop a running agent or an entire run.

mode stop                    # Stop all agents in current run
mode stop --agent ads        # Stop a specific agent
mode stop --run abc123       # Stop a specific run by ID

Config file

Place .mode/config.json in your project root. Mode Agent reads this file automatically on every session.

{
  "permissions": {
    "fs":   { "roots": ["./src", "./test"] },
    "bash": { "allow": ["git", "npm", "make"] }
  }
}

The config file is for permissions only.

Permissions config

Full reference for the sandbox configuration block. Define the boundaries once and agents operate freely within them.

REST API

The Mode Agent REST API will let you start runs, stream signals, and manage agents programmatically.

Base URL

The base URL will be published here when the API goes live. There is no live endpoint to call yet.

Planned endpoints

See Authentication to get started.

Authentication

How API requests will authenticate once the REST API is live.

Requests will pass your API key in the Authorization header, in this form.

Authorization: Bearer sk_mode_xxxxxxxxxxxx

API keys will be generated from your dashboard, scoped with specific permissions and rate limits.

Runs

How you will create and manage runs via the API.

POST /v1/runs

Will start a new agent run from a goal and an optional set of agent roles.

GET /v1/runs/:id

Will return the status and results of a run.

Agents

How you will list and inspect available agent roles.

GET /v1/agents

Will return all available agent roles.

Planned response

{
  "agents": [
    { "role": "planner", "parallelizable": false },
    { "role": "email", "parallelizable": true },
    { "role": "ads", "parallelizable": true }
  ]
}