Profiles

Profiles are a handy way to organize Gage and Inspect options during development. They let you define shared settings for projet. You can simply use a profile to active its settings and not worry about leaking secrets.

With a profile, you can define:

• Default model used for tasks
• API keyes
• Any other setting that is configured with an environment variable

See gage.toml for help on creating and using profiles.

See secrets.json for information on keeping secrets safe from unauthorized use.

List profiles

For example, when profiles are stored with a project, including secrets, you can discover which profiles are available using gage profile list.

gage profile list

Use a profile

To activate a profile, use gage profile use.

gage profile use

Once activated, all of the profile settings are applied whenever you use Gage commands. You have access to any models you’re authorized to use.

Profiles and source code

This pattern recommends storing shared settings in source code only when secrets are edited using SOPS.

Do not store profile secrets in source code if they aren’t encrypted using the sops command.