Skip to main content
Configure Namespace agents with an agents block. A top-level block sets defaults for every command step in the pipeline. Add an agents block to an individual step to override those defaults for that step.
The nsc-* tags below configure the Namespace instance created for the job.

Compute tags

See Machine Shapes for guidance on selecting resources.

macOS base images

For macOS images, it is possible to choose base image selectors with the nsc-image-selectors agent tag. Multiple selectors may be separated by a comma. For example, to use a base image with Tahoe slim, include the agent tags

Linux on Apple Silicon

Linux on Apple Silicon is in early access. Reach out to enable it for your workspace.Contact support →
Set the nsc-prefer-sku agent tag to m4pro, m5, or m5max to prefer an Apple Silicon machine for a Linux job.
See Linux on Apple Silicon machine shapes for the available shapes.

Caching

Attach a Cache Volume to preserve dependencies and other build outputs across jobs. Jobs using the same cache tag access the same cache contents.
Use a stable tag when jobs should share a cache. Use distinct tags to isolate caches between repositories, branches, or toolchains.

Verifying signed Buildkite pipelines

Namespace-managed agents support verification of signed Buildkite pipelines with self-managed keys. To get started:
  1. Follow Buildkite’s guide for setting up signed pipelines.
  2. During this process, you will create a public/private key pair. Save the resulting public key set (the entire contents of the resulting <key>-public.json file as a secret in Namespace, using either the Vault dashboard or CLI command
Note the ID of the secret, which is of the form sec_<my-secret-id>.
  1. Update the agent tags in your Buildkite pipeline:

Additional tags

Use these tags to configure repository mirrors, container storage, the Linux agent container, and local Docker builders. The nsc-features tag accepts a comma—separated list of feature assignments. Some examples are shown below. Enable the Git mirror, container image cache, and privileged containers together:
Combine multiple nsc-features assignments into one comma-separated value when a job needs more than one feature. For example, to use a local Docker builder with a persistent 50 GB cache:
Last modified on August 21, 2026