> ## Documentation Index
> Fetch the complete documentation index at: https://niceeval.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# NiceEval Examples

> Pick a runnable NiceEval example by subject under test: Agent Framework integrations, full AI agent evals, coding-agent extension benchmarks, and real projects.

Every example here has real, runnable source. Choose by subject under test — you don't need to read them in order.

If you haven't run your first eval yet, read [Quickstart](/docs/tutorials/quickstart) first. If you already know your task, go straight to the matching [Tutorials](/docs/tutorials/connect-your-agent) page.

## Connect an Existing Agent Framework

Each of the five examples below keeps both the plain application before integration and the full project after integrating NiceEval. The code diffs on each page are generated from those two sources.

| Subject under test                                    | Integration path                      | Example coverage                                                      |
| ----------------------------------------------------- | ------------------------------------- | --------------------------------------------------------------------- |
| [AI SDK v7](/docs/examples/integrations/ai-sdk-v7)         | Built-in `uiMessageStreamAgent`       | UI Message Stream, multi-turn, tools, HITL                            |
| [Claude Agent SDK](/docs/examples/integrations/claude-sdk) | `createClaudeSdkEventStream`          | Native event stream, multi-turn, tools, HITL                          |
| [Codex SDK](/docs/examples/integrations/codex-sdk)         | `createCodexThreadEventStream`        | Coding tasks, files and commands, usage; the SDK doesn't support HITL |
| [pi-agent-core](/docs/examples/integrations/pi-sdk)        | `createPiAgentEventStream`            | Native event stream, multi-turn, tools, HITL; the SDK has no OTel     |
| [LangGraph](/docs/examples/integrations/langgraph)         | Hand-written custom SSE frame mapping | Python application, multi-turn, tools, HITL                           |

Every example's source lives under [`examples/zh/origin/`](https://github.com/CorrectRoadH/niceeval/tree/main/examples/zh/origin) and [`examples/zh/tier1/`](https://github.com/CorrectRoadH/niceeval/tree/main/examples/zh/tier1). When you need OTel or Experiment Flags, follow the same project into `tier2/` and `tier3/`.

## Full Eval Projects

<CardGroup cols={2}>
  <Card title="Eval an AI Agent Application with a Hand-Written Adapter" icon="robot" href="/docs/examples/ai-agent-application">
    An AI SDK v6 web agent covering tool calls, image understanding, multi-turn sessions, model comparison, and dual observability.
  </Card>

  <Card title="Eval Coding Agent Extensions" icon="wand-magic-sparkles" href="/docs/examples/coding-agent-extensions">
    Use a real workspace and controlled experiments to measure how Skills, prompts, and plugin benchmarks affect task outcomes.
  </Card>
</CardGroup>

## Real Projects

### Coding Agent Memory Evals

[coding-agent-memory-evals](https://github.com/CorrectRoadH/coding-agent-memory-evals) uses the same batch of development tasks and the same model to compare task success rate, cost, latency, and behavior differences between a coding agent with persistent memory and one without.

* [View the live report](https://niceeval.com/showcase/memory)
* [View the source code](https://github.com/CorrectRoadH/coding-agent-memory-evals)

### Terminal-Bench

[terminal-bench](https://github.com/NiceEval/terminal-bench) runs the audited Harbor Terminal-Bench task set on NiceEval with the original `run-tests.sh` verifiers, and compares coding agents and models side by side.

* [View the live report](https://niceeval.com/showcase/terminal-bench)
* [View the source code](https://github.com/NiceEval/terminal-bench)

## Scope of Examples

* Single-snippet API usage belongs in a task tutorial or the Reference, not here.
* Toy projects without runnable source code are not included.
* Roadmap items and integrations that aren't implemented yet are not included.
* The same project doesn't get duplicated across multiple case pages just because it's also called a Skill, a Plugin, or a Hook.