gage.toml

Gage configuration is defined in a file named gage.toml.

Configuration consists of a list of profiles. A profile defines a set of environment variables that are applied used for Gage commands.

Use profiles to apply configuration when Gage commands are run:

Profile attributes

Name	Description
`help`	Profile description, used in listings and status
`secrets`	Path to secrets file used for profile env
`log_dir`	Inspect log directory
`env`	Map of profile environment variables

A profile is activated by running gage profile use <profile> first. The active profile is defined in .env.

Profile environment variables may include references to secrets. A secret is defined in a sops encrypted file.

Here’s a gage.toml file that defines a single dev profile with support for OpenAI.

gage.toml

[profiles.dev]

help = "Local dev support"
secrets = "secrets.json"

[profiles.dev.env]

OPENAI_API_KEY = "{openai}"
GAGE_MODEL = "openai/gpt-4.1"

The value for OPENAI_API_KEY contains a reference to the openai secret, which must be defined in a sops-encrypted file named secrets.json.

secrets.json

{
  "openai": "*****"
}

See secrets.json for help creating a secrets file.

To activate the dev profile, use gage profile use.

$ _

gage profile use dev