Native App Setup

Atlas is a native desktop app for macOS and Windows. The main setup path for Atlas Review is the desktop first-run flow.

First-Run Flow

The desktop onboarding flow is:

1. Welcome
2. AI Provider
3. MCP onboarding
4. Add first project

Atlas starts scanning for installed CLI tools as soon as the setup wizard opens, so provider detection can finish while you are still on the welcome screen.

What You’ll See

On the Welcome step, Atlas introduces the main product surfaces users will care about first:

• Branch Review
• PR Review
• Atlas MCP
• Fully Configurable

When you move to the AI Provider step, Atlas either:

• shows AI Provider Detected with providers it found on your machine
• or shows Set Up AI Provider with two clear paths: Install or detect a CLI tool and Add your API key

The MCP step is optional. It is there to help users connect Atlas to agent tools early, but it does not block the rest of onboarding.

The last step is Add Your First Project, with two main options:

• Open Local Folder
• From GitHub

If folder picking is not available, Atlas falls back to a manual path entry form.

Minimal Setup Expectation

For many users, setup is:

1. launch Atlas
2. let it detect available provider tools or subscriptions
3. pick an active provider
4. optionally connect MCP
5. add a local or GitHub project

In the happy path, a user with an existing supported CLI already installed reaches a runnable review setup without manual configuration.

Where To Change Things Later

After first run, the same controls remain available in:

• Atlas Settings > AI Provider
• Atlas Settings > MCP

When Manual Setup Is Still Needed

Manual configuration is usually only needed when:

• no provider was detected
• you want to use a specific API key
• you want to use OpenCode with a configured provider path
• you want to connect an agent client through MCP