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

# Getting started checklist

> Connect your system, confirm events and run your first evaluation.

For setup and management entirely from a coding agent, see the [headless workflow](/guides/headless) and [SDK platform clients](/sdk/platform).

## Copy this into your coding agent

Paste into Cursor, Codex, Claude Code, or another coding agent in your project.

```text theme={null}
Help me connect this project to Bench using https://docs.usebench.ai/guides/getting-started.
Inspect the repository and explain the app's intended outcome and main AI entry point.
Check GitHub access, then help me set up SDK events and MCP using the linked guides.
Verify each connection with a real result. Tell me which steps still need my account access.
```

Open **Getting started** in Bench to see the connections and results already received
for your account. Steps update automatically while the page is open.

<Steps>
  <Step title="Connect your repository">
    Connect GitHub and select a repository. Bench scans its code for AI systems,
    prompts and tools. You can also begin with SDK events without GitHub.
  </Step>

  <Step title="Check your system’s business outcome">
    Open an AI system’s **Understanding** page. Add or correct what success means:
    for example, “refund an eligible order exactly once” and the relevant refund
    policy. Bench uses this context to make evaluation criteria relevant.
  </Step>

  <Step title="Confirm your SDK connection">
    Choose an environment, install the SDK and run a synthetic request. The step
    completes after Bench receives an event. Creating a key alone is not evidence
    that instrumentation works. Follow the [SDK quickstart](/sdk/quickstart).
  </Step>

  <Step title="Run and inspect a Bench">
    Select **Start benching** on a system to compare prompts and models. Inspect
    failed cases and the evidence behind recommendations. Use **Real app testing**
    to inspect tests of application behavior and tool effects. See
    [real app testing](/sdk/system-evaluation).
  </Step>

  <Step title="Connect your coding agent, optionally">
    Connect [MCP](/mcp/overview) with sign-in, then ask your agent to list your Bench
    systems. The checklist confirms a successful authenticated MCP request. An API
    key created for an agent does not by itself confirm MCP connection.
  </Step>
</Steps>

SDK progress reflects retained events from the last 30 days across your deployments. Choose the environment during SDK setup.
It is not a live heartbeat or a claim that every code path is instrumented.