# AgentClash > AgentClash runs agents against repeatable challenge packs, captures replay evidence, and shows where a run won, failed, or drifted. Use this index when you want the shortest machine-readable map of the public docs. Fetch `/llms-full.txt` for the bundled corpus, or use the `/docs-md/...` links below for page-level markdown exports. ## Core entrypoints - [Docs home](https://agentclash.dev/docs-md) - overview, navigation, and starting points. - [Quickstart](https://agentclash.dev/docs-md/getting-started/quickstart) - fastest path to a real run. - [Self-Host](https://agentclash.dev/docs-md/getting-started/self-host) - local stack and service dependencies. - [First Eval](https://agentclash.dev/docs-md/getting-started/first-eval) - end-to-end walkthrough of one eval path. - [CLI Reference](https://agentclash.dev/docs-md/reference/cli) - generated command reference. - [Config Reference](https://agentclash.dev/docs-md/reference/config) - generated environment and precedence reference. - [Full bundle](https://agentclash.dev/llms-full.txt) - all shipped docs in one file. ## Getting Started - [Quickstart](https://agentclash.dev/docs-md/getting-started/quickstart) - Use the hosted backend and validate auth, workspace access, and run creation. - [Self-Host](https://agentclash.dev/docs-md/getting-started/self-host) - Bring up the local stack with Postgres, Temporal, API server, worker, and web app. - [First Eval](https://agentclash.dev/docs-md/getting-started/first-eval) - Walk through the current happy path from seeded data to live run events and ranking output. ## Concepts - [Runs and Evals](https://agentclash.dev/docs-md/concepts/runs-and-evals) - Understand the difference between a run, a ranked result set, and the broader eval concept. - [Agents and Deployments](https://agentclash.dev/docs-md/concepts/agents-and-deployments) - See how runnable agent targets are modeled before they can participate in an eval. - [Challenge Packs and Inputs](https://agentclash.dev/docs-md/concepts/challenge-packs-and-inputs) - Understand how tasks, input sets, and scoring context are grouped into repeatable workloads. - [Replay and Scorecards](https://agentclash.dev/docs-md/concepts/replay-and-scorecards) - Learn how canonical events become timelines, evidence, and comparison-ready outputs. - [Tools, Network, and Secrets](https://agentclash.dev/docs-md/concepts/tools-network-and-secrets) - See how pack-defined tools delegate to primitives, how outbound internet is controlled, and where secrets resolve. - [Artifacts](https://agentclash.dev/docs-md/concepts/artifacts) - Understand stored files, pack assets, run evidence, and signed downloads. ## Guides - [Write a Challenge Pack](https://agentclash.dev/docs-md/guides/write-a-challenge-pack) - Author a bundle YAML file, validate it, publish it, and understand the IDs AgentClash returns. - [Configure Runtime Resources](https://agentclash.dev/docs-md/guides/configure-runtime-resources) - Create secrets, provider accounts, model aliases, runtime profiles, and deployments in the order the product expects. - [Interpret Results](https://agentclash.dev/docs-md/guides/interpret-results) - Read timelines, scorecards, and ranking changes without getting lost in raw event volume. - [Use with AI Tools](https://agentclash.dev/docs-md/guides/use-with-ai-tools) - Use llms.txt, the full bundle, and per-page markdown exports with assistants and coding agents. ## Reference - [CLI](https://agentclash.dev/docs-md/reference/cli) - Commands, flags, and command groups generated from the Cobra source tree. - [Config](https://agentclash.dev/docs-md/reference/config) - Current environment surface pulled from the API, worker, CLI, and example config sources. ## Architecture - [Overview](https://agentclash.dev/docs-md/architecture/overview) - Web, API, worker, Postgres, Temporal, sandbox, and artifact storage in one picture. - [Orchestration](https://agentclash.dev/docs-md/architecture/orchestration) - How API requests become Temporal workflows and how the worker executes them. - [Sandbox Layer](https://agentclash.dev/docs-md/architecture/sandbox-layer) - Why execution is isolated behind a provider boundary and how E2B fits today. - [Data Model](https://agentclash.dev/docs-md/architecture/data-model) - The core entities behind workspaces, deployments, challenge packs, runs, and evidence. - [Evidence Loop](https://agentclash.dev/docs-md/architecture/evidence-loop) - How run events, artifacts, and scorecards move from execution into replay and review. - [Frontend](https://agentclash.dev/docs-md/architecture/frontend) - How the Next.js app is split between public product pages, authenticated app routes, and docs. ## Contributing - [Setup](https://agentclash.dev/docs-md/contributing/setup) - Clone the repo, boot the local stack, and choose the fastest dev loop for your task. - [Codebase Tour](https://agentclash.dev/docs-md/contributing/codebase-tour) - Map the top-level modules before you start changing APIs, workflows, or the web app. - [Testing](https://agentclash.dev/docs-md/contributing/testing) - Pick the smallest useful validation loop and use review checkpoints for scoped changes.