> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gainable.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Gaia Autopilot

> The autonomous runtime that watches your data, drafts work, and lands it in your inbox for approval

## What is Gaia Autopilot?

Gaia Autopilot is autonomous. It runs on its own. It watches data against objectives Gainable infers from your app, drafts work when something needs attention, and lands that work in your inbox for you to approve, edit, or skip.

Internally, Autopilot is a fleet of small, scope-bounded agents (one per objective). The umbrella, the inbox, the activity feed, and the playbook editor are all Autopilot.

If [Gaia Copilot](/copilots/overview) is "the user asks, the Copilot answers," Autopilot is "work shows up before anyone asks." Two halves of the same intelligence layer. The Copilot is reactive. Autopilot is proactive.

<Info>
  **Apps that work for you, not apps you work with.** Autopilot does the thinking in the background. You stay in control through the inbox. Draft-and-approve is the default, so nothing leaves the building until you say so.
</Info>

## Test for which one applies

> Does the user have to ask first?
>
> * **Yes** → [Gaia Copilot](/copilots/overview)
> * **No** (work shows up before they ask) → Gaia Autopilot

## What Autopilot does

<CardGroup cols={2}>
  <Card title="Watches data" icon="eye">
    Subscribes to change streams, schedules, webhooks, and explicit clicks. Reacts when something matches.
  </Card>

  <Card title="Maintains objectives" icon="bullseye">
    Inferred goals like "every claim resolved in 14 days" or "follow up on stalled deals."
  </Card>

  <Card title="Drafts work" icon="pen-line">
    Composes emails, Slack messages, status updates, summaries, and SLA escalations.
  </Card>

  <Card title="Lands in the inbox" icon="inbox">
    Drafts arrive in the [Autopilot inbox](/autopilot/inbox) with full reasoning, ready for one-click approve, edit, or skip.
  </Card>
</CardGroup>

## How Autopilot comes to life

Every Gainable app moves through a five-phase build contract:

```
data → derives → seed → ui → autopilot → built
```

The **autopilot** phase is where agents are inferred from your schema and intent. Gainable reads your data model, looks at how the app is shaped, and proposes objectives, playbooks, tools, and risk tiers. You review the autonomy contract, edit it, and ship.

<Steps>
  <Step title="Data is connected">
    Datasets and data models give Gainable the schema to work with.
  </Step>

  <Step title="UI is built">
    Tables, forms, dashboards, and the Autopilot inbox are added to the app.
  </Step>

  <Step title="Autopilot is inferred">
    Gaia proposes objectives ("keep claims moving"), playbooks ("nudge after 7 days idle"), tools ("send\_email"), and risk tiers ("draft, don't auto-send").
  </Step>

  <Step title="You approve the contract">
    Edit anything you want. Disable any objective. Tighten the risk posture.
  </Step>

  <Step title="Autopilot goes live">
    The runtime starts watching change streams, schedules, and webhooks. Drafts begin landing in the inbox.
  </Step>
</Steps>

## Two scopes

Each agent runs in one of two scopes. The difference matters for permissions and visibility.

| Scope        | Runs as         | Visibility                                   | Use for                                                     |
| ------------ | --------------- | -------------------------------------------- | ----------------------------------------------------------- |
| **App-wide** | The org         | Drafts visible to anyone with the right role | Stalled-deal chasers, SLA enforcers, digest publishers      |
| **Personal** | A specific user | Drafts visible only to that user, RBAC-bound | Daily briefings, personal follow-ups, my-pipeline summaries |

See [scopes](/autopilot/scopes) for the full boundary rules.

## What Autopilot does *not* do

Autopilot is not a magic wand. By default it:

* Doesn't send anything to a customer without approval
* Doesn't take destructive write actions without explicit graduation
* Doesn't run outside the risk tier you signed off on
* Doesn't see data the configured scope doesn't allow

All of this is enforced by the [risk tiers](/autopilot/risk-tiers) and [tool registry](/autopilot/tools), not by hope.

## Autopilot at a glance

| Concept                                   | What it is                                                                                        |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------- |
| [Objectives](/autopilot/objectives)       | What an agent maintains, e.g. "every claim resolved in 14 days"                                   |
| [Playbooks](/autopilot/playbooks)         | The trigger → steps → guardrails recipe inside an agent                                           |
| [Triggers](/autopilot/triggers)           | The four ways a playbook starts: schedule, data change, webhook, user-triggered                   |
| [Tools](/autopilot/tools)                 | The fixed registry agents call: `query_collection`, `send_email`, `draft_for_approval`, and so on |
| [Risk tiers](/autopilot/risk-tiers)       | Trust posture: draft-and-approve by default, graduation, undo windows                             |
| [Inbox](/autopilot/inbox)                 | The user-facing inbox, ambient strip, and dashboard widget                                        |
| [Action log](/autopilot/agent-action-log) | The audit trail. Every trigger, tool call, and outcome is recorded                                |

## Prompt examples

You can describe Autopilot agents in natural language:

```text theme={null}
Add a stalled-deal chaser. Watch the deals collection.
If a deal hasn't moved stage in 14 days and the amount is
over $5,000, draft a follow-up email to the contact and
land it in the deal owner's Autopilot inbox.
```

```text theme={null}
Add a daily briefing for each sales rep. At 8 AM in their
timezone, summarize: deals closing this week, deals with no
activity in 7+ days, top 3 deals by amount. Personal scope,
draft to their inbox.
```

```text theme={null}
Add an SLA enforcer for tickets. If a ticket has been "open"
for more than 24 hours with no response, escalate to the
team lead and draft a status update for the customer.
```

## Learn more

<CardGroup cols={2}>
  <Card title="Objectives" icon="bullseye" href="/autopilot/objectives">
    What agents are trying to maintain
  </Card>

  <Card title="Playbooks" icon="book-open" href="/autopilot/playbooks">
    Trigger, steps, and guardrails
  </Card>

  <Card title="Triggers" icon="bolt" href="/autopilot/triggers">
    Schedule, data change, webhook, user-triggered
  </Card>

  <Card title="Tools" icon="screwdriver-wrench" href="/autopilot/tools">
    The fixed tool registry
  </Card>

  <Card title="Risk tiers" icon="shield-check" href="/autopilot/risk-tiers">
    Draft-and-approve by default
  </Card>

  <Card title="Inbox" icon="inbox" href="/autopilot/inbox">
    Where drafts land
  </Card>

  <Card title="Recipes" icon="lightbulb" href="/autopilot/recipes">
    Worked examples of common playbooks
  </Card>

  <Card title="Gaia Copilot" icon="comments" href="/copilots/overview">
    Looking for the conversational side?
  </Card>
</CardGroup>