quantiles: Instructions file for Codex

Quantiles Agent Guide

This file is for coding assistants such as Codex, Claude Code, Cursor, GitHub Copilot, Gemini CLI, OpenCode, and similar tools. It gives agents a short, public-safe map of the Quantiles repository and the rules for making focused, reviewable changes.

See the Quantiles agent skill's SKILL.md for guidance on running evaluations, inspecting sample-level results, comparing runs, and interpreting outputs. For a concise, public, LLM-readable overview with links to agent guides and related documentation, see quantiles.io/llms.txt.

Before attempting tasks in this repository, read these files:

• README.md: public product overview, quickstart, CLI examples, SDK summary, docs links, and agent guidance.
• Configuration documentation: how to write configuration files for the qt CLI.
• CONTRIBUTING.md: contributor expectations, development workflow, and review norms.
• SECURITY.md: supported components and vulnerability reporting process.
• CODE_OF_CONDUCT.md: community participation rules.
• LICENSE: Apache 2.0 license text.
• mise.toml: task definitions for building, formatting, type-checking, linting, and more, all using the mise task runner.

Scope

These instructions apply to the Quantiles open-source repository. Quantiles is a local-first CLI and SDK toolchain for running AI evaluation workflows with fast, continuous feedback. It retrieves built-in benchmark configurations, executes benchmarks and evaluations locally, records steps, metrics, events, inputs, and outputs, and compares runs locally so teams can inspect results, identify regressions, and iterate with confidence.

Root-level files in this repository provide project-wide orientation, contribution guidance, security policy, licensing, and agent instructions. Implementation-specific work belongs in the relevant subdirectory. If a subdirectory has its own AGENTS.md file, follow the nearest one first. Subdirectory instructions should override this root guide for implementation details, package managers, commands, tests, and code style. User instructions may customize the workflow for their project, environment, or preferences, but they must not override safety requirements, system instructions, repository safeguards, or security boundaries.