Skip to main content
Connecting an application needs three files: an Adapter calls the application, an Experiment fixes the subject under test and run count, and an Eval defines assertions. The steps below provide the shortest complete path, covering both automatic setup through a Coding Agent and manual setup.
1

Set up

Send the following instruction to the Coding Agent you use, such as Codex, Claude Code, or another Agent that can modify the current project:
2

Run evals

Use the Experiment ID listed by the Agent. If it did not list one, first run pnpm exec niceeval exp list to see available Experiments.
3

View results

Set up manually

First start your application under test and confirm that it has a callable interface. The example below assumes POST http://localhost:3000/chat, whose request body accepts message and model and whose JSON response has a string reply field. If your interface differs, change the Adapter URL, request body, and response-reading code. If you do not yet have an application to start, choose a runnable project from Examples.

Adapter

An Adapter connects an Agent to NiceEval. The three integration tiers range from a non-invasive connection to modifying the Agent configuration, and unlock different Eval capabilities. See Tier.

Experiment

Eval

At this point, the first Eval has run successfully. This minimal Adapter supports only single-turn calls; a second turn does not include the first turn’s history. Multi-turn sessions, tool-call events (for t.calledTool()), HITL, and tracing are optional capabilities you can add later. Existing Evals do not need to change when you extend the setup by following Connect Your Agent.

Compare with a complete project

After the first Eval succeeds, go to Examples and choose a complete project by subject under test. Those pages provide runnable source code. General operating steps are in the matching Tutorials task page.

Put it in CI

Read Author Evals and Evaluation Kinds and Assertions, then replace the example with a real scenario.