evaly config

View and manage Evalytic configuration.

evaly config <SUBCOMMAND>

The config command group provides tools to inspect and debug your Evalytic configuration. Useful for verifying API keys are loaded, checking which config file is active, and understanding where settings come from.

Subcommands

Subcommand	Description
`show`	Display active configuration, API key status, and config file path.

evaly config show

Displays a table of all active settings with their values and sources:

evaly config show

Example output

$ evaly config show

           Active Configuration          
   Key / Setting      Value           Source         
   ─────────────────────────────────────────────────
   FAL_KEY            fal1***abcd     .env
   GEMINI_API_KEY     AIza***wxyz     evalytic.toml
   OPENAI_API_KEY     (not set)       --
   ANTHROPIC_API_KEY  (not set)       --
   ─────────────────────────────────────────────────
   judge              gemini-2.5-flash  default

  Config file: /home/user/project/evalytic.toml

Understanding sources

Source	Meaning
`.env`	Key was loaded from a `.env` file in the current directory.
`evalytic.toml`	Key or setting was loaded from your config file.
`environment`	Key is set as an environment variable (e.g., `export FAL_KEY=...`).
`default`	Using the built-in default value.
`--`	Not set anywhere.

Key masking

API keys are always displayed masked for security: the first 4 and last 4 characters are shown, with *** in the middle. For example, AIzaSyBtest1234567890abcdef appears as AIza***cdef.

Use Cases

Verify setup after `evaly init`

# Set up your project
evaly init

# Verify everything is configured
evaly config show

Debug "API key not set" errors

# See which keys are loaded and from where
evaly config show

# Use a specific config file
evaly --config path/to/evalytic.toml config show

Verify CI/CD environment

# In CI, verify secrets are available before running benchmarks
evaly config show
evaly bench -m flux-schnell -p "A cat" -y

evaly init Judges