> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/setup-apps-os/cli-in-cicd/local-development.md).

# Setting up local development

A developer can run the Seal CLI on their own machine, against the same Seal Project the CI/CD pipeline uses or against a separate one, using a [development token](/getting-started/tokens.md#development-token). Local activity is filtered out of the Protection page by default, so it does not pollute production-side metrics with churn from local builds.

## Steps

1. [**Install the Seal CLI**](/setup-apps-os/cli-in-cicd/installing-the-cli.md) on the developer's machine.
2. **Generate a development token** from **Settings > Tokens**, or reuse one your team already shares. See [Generating and revoking tokens](/getting-started/tokens/generating-tokens.md).
3. **Set environment variables** in the developer's shell (typically through `.bashrc`, `.zshrc`, or the equivalent for the shell of choice):

   ```bash
   export SEAL_TOKEN=<your development token>
   export SEAL_PROJECT=my-project-id
   ```
4. **Run the CLI** from the project's working directory the same way CI does:

   ```bash
   seal fix --mode all
   ```

## What changes versus CI

* The token is a development token, not a production token.
* Activity is filtered out of the Protection page by default. To see local-token activity in the Seal UI, switch the [Development token filter](/discovering/protection-page/vulnerable-packages-tab.md#filters) on the Vulnerable packages tab to include it.

The CLI's behavior is otherwise identical: same `seal fix --mode <mode>` invocation, same Sealing Rule lookup, same sealed-package replacement.

## Related

* [Token types](/getting-started/tokens/token-types.md): production versus development tokens and what each is tracked against.
* [Token security best practices](/getting-started/tokens/best-practices.md): where to keep the development token.