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

# Run tasks locally

> Run Octoparse tasks locally, choose a browser, stream JSONL events, detach execution, control active runs, inspect history, and export results.

`octoparse run` starts local extraction with the embedded Octoparse engine. It does not require the desktop application.

## Start a foreground run

```bash theme={null}
octoparse run <taskId>
octoparse run <taskId> --max-rows 100
octoparse run <taskId> --timeout-ms 600000
octoparse run <taskId> --headless
```

Use a local task definition instead of fetching a remote task:

```bash theme={null}
octoparse run local-task --task-file task.json
```

Functional commands require credentials, including local task-file runs.

## Select a browser

```bash theme={null}
octoparse run <taskId> --browser independent --headless
octoparse run <taskId> --browser user --browser-id chrome --profile "Default"
```

See [Choose a browser mode](browser-modes) for setup and selection priority.

## Stream machine-readable events

```bash theme={null}
octoparse run <taskId> --json
octoparse run <taskId> --jsonl
```

`--jsonl` streams row, log, CAPTCHA, proxy, download, and lifecycle events. See [Output and exit codes](../reference/output-and-exit-codes).

## Start a detached run

```bash theme={null}
octoparse run <taskId> --detach --output ./runs
```

Pass the same `--output` directory when checking history or exporting results.

## Control a local run

```bash theme={null}
octoparse local status <taskId> --output ./runs
octoparse local pause <taskId>
octoparse local resume <taskId>
octoparse local stop <taskId>
octoparse local history <taskId> --output ./runs --json
octoparse local cleanup --json
```

Local status is tracked by this CLI and is not synchronized with the desktop app.

## Export local results

Prefer the unified data command:

```bash theme={null}
octoparse data export <taskId> --source local --output ./runs --format xlsx
octoparse data export <taskId> --source local --lot-id <lotId> --format csv
```

`octoparse local export` remains available for compatibility.

<Note>
  The `runs` command group is intended for internal artifact inspection. User workflows should use task IDs with `local` and `data`, or lot IDs with `data export`.
</Note>