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

# Run Scout as an Atlas worker

> Let Atlas assign discovery jobs to a trusted local Scout process.

Worker mode lets a logged-in Scout installation claim Atlas discovery jobs,
process them locally, and return source-linked results for review.

Use worker mode only on a computer you intend to leave running. For one-off local
research, use `scout run`.

## Requirements

* Atlas login on this computer.
* A local model provider or configured model provider.
* Search-backed discovery access for exploratory jobs.
* `scout doctor --worker` passing before long-running work.

Check readiness:

```bash theme={null}
scout doctor --worker
```

## Start A Worker

```bash theme={null}
scout worker start
```

Change the idle polling interval:

```bash theme={null}
scout worker start --interval 30
```

Pass a search key in scripts when needed:

```bash theme={null}
scout worker start --search-api-key "$SEARCH_API_KEY"
```

Normal interactive use should prefer:

```bash theme={null}
scout search connect
```

## Check Or Stop Worker Mode

Show tracked worker state:

```bash theme={null}
scout worker status
```

Stop the tracked worker process:

```bash theme={null}
scout worker stop
```

## What Worker Output Means

Worker output is not a direct publish path. Returned results still need the same
evidence review and visibility decision as other Scout or hosted discovery runs.

If the worker is revoked in Atlas, active leases should be released and the
computer should stop claiming new jobs.