Use PromptBeat when
- you need to test prompt injection, jailbreak, refusal, harmful-content, or policy behavior;
- you want to compare a model, Prompt, or provider change on the same cases;
- you need a versioned dataset and repeatable regression workflow;
- the claim you need to make is scoped to model/provider requests and responses.
One product loop
Describe the evaluation
A PromptBeat project defines the model Target, Scenarios, Seeds, Provider roles, and Promptfoo backend configuration.
Validate before calling a model
promptbeat validate checks the project structure and referenced files. Validation does not prove that a remote model is reachable.Preview deterministic cases
promptbeat generate deterministically produces local JSON cases without running Promptfoo red-team generation or calling the Target.Run the full pipeline
promptbeat run compiles Promptfoo configuration, runs Promptfoo red-team generation, validates generated cases, evaluates configured targets, and parses the result.Inspect and retain artifacts
The output directory contains the generated backend artifacts, raw result, normalized
evaluation_result.json, and report.html.Current capabilities
Scenario-driven projects
Keep target definition, risks, expected behavior, and seeds reviewable in source-controlled files.
Promptfoo execution
Compile and execute the current red-team pipeline through the pinned Promptfoo backend.
Provider roles
Configure generator, Judge, and target providers independently through environment-backed values.
Inspectable artifacts
Retain raw backend output, normalized results, and an HTML report under the run directory.
Dataset versioning
Build versioned candidate, evaluation, promotion, lineage, and report artifacts.
Source or release use
Run from a complete release bundle or build the Go CLI from source and supply the required evaluation backend separately.
Runtime boundary
RunAgentEvaluation path and does not evaluate HTTP Agent tool use or environment state.