Setting up local development

Run the Seal CLI on a developer's machine using a development token.

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. 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 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.

3. Set environment variables in the developer's shell (typically through .bashrc, .zshrc, or the equivalent for the shell of choice):

   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:

   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 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: production versus development tokens and what each is tracked against.

• Token security best practices: where to keep the development token.