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

# Rove mode

> Let the AI explore on its own, or tap through the app yourself while it captures.

There are two ways to map an app with Roveflow. Both end with the same Atlas, the difference is who does the tapping.

## Autopilot

This is rove mode: the AI explores the app on its own. It looks at each screen, decides where a real user would tap next, captures the screens it lands on, and names them as it goes. You don't touch the phone.

You steer it with a plain-English ask. In Claude Code:

```
/rove   map sign-up, the main action, and settings
```

Tell it which parts of the app to cover and it finds its own way through them.

## Assisted

Here you tap through the app yourself while Roveflow watches over your shoulder. As you move from screen to screen, it captures and names each one for you. When you're done, it builds the Atlas the same way.

## Which to use

<CardGroup cols={2}>
  <Card title="Use autopilot" icon="compass">
    When you want the app mapped hands-off, or you're exploring a competitor's app you don't know well. Just say what to cover and let it run.
  </Card>

  <Card title="Use assisted" icon="hand-pointer">
    When a flow needs a real login, a specific path, or steps the AI can't reach on its own. You drive; it captures.
  </Card>
</CardGroup>

Either way, the screens, journeys, and videos land in `roveflow-out`, and the finished `atlas.html` is yours to open and share.

<Card title="See what comes out" icon="map" href="/concepts/the-atlas">
  Read about the Atlas, the page both modes produce.
</Card>