pi-mono/packages/evals
2026-07-25 08:22:32 +02:00
..
scripts feat(coding-agent): add vitest eval harness (#7085) 2026-07-25 08:22:32 +02:00
src feat(coding-agent): add vitest eval harness (#7085) 2026-07-25 08:22:32 +02:00
package.json feat(coding-agent): add vitest eval harness (#7085) 2026-07-25 08:22:32 +02:00
README.md feat(coding-agent): add vitest eval harness (#7085) 2026-07-25 08:22:32 +02:00
tsconfig.json feat(coding-agent): add vitest eval harness (#7085) 2026-07-25 08:22:32 +02:00
vitest.config.ts feat(coding-agent): add vitest eval harness (#7085) 2026-07-25 08:22:32 +02:00

Pi evals

Behavioral evaluations for Pi using vitest-evals and its Pi harness.

Running

From the repository root, run with an explicit provider and model:

npm run eval -- --provider openai-codex --model gpt-5.4

When invoked from a Pi Bash tool, the current session supplies PI_PROVIDER and PI_MODEL, so this is sufficient:

npm run eval

The runner requires both values and never falls back to another model. Additional arguments are forwarded to Vitest, for example:

npm run eval -- -t "capital of France"

Authentication is resolved by Pi's normal ModelRuntime. Subscription-backed providers such as openai-codex use credentials from the user's Pi configuration. API-backed providers use their standard environment variables, such as OPENAI_API_KEY for openai.

Pi harness compatibility

@vitest-evals/harness-pi-ai 0.15.0 still declares and imports the former @mariozechner/pi-ai and @mariozechner/pi-agent-core package names. The eval package provides aliases at the current Pi version and routes the legacy AI import through src/pi-ai-compat.ts. Keep those alias versions synchronized with the Pi workspace version until the upstream harness supports the current @earendil-works packages.