agents-last-exam AGENTS.md

Development Rules

Repository layout

agents-last-exam/
├── ale_run/                  Framework code (python -m ale_run is the entry point)
│   ├── agents/                 Agent deployers: claude_code, ale_claw, …
│   ├── base_interface/         The contracts: Provider / Executor / Deployer / Trajectory
│   ├── environments/           Providers (gcloud, static) + image registry
│   ├── executors/              Where a deployer runs: sandbox / local / docker
│   ├── orchestration/          Run lifecycle, config loader, factories
│   └── tasks/                  Task discovery + driver
├── tasks/                    Task packages, grouped by domain (demo/ has the templates)
├── configs/                  Reusable agent + environment configs (referenced by path)
├── selected_tasks/           Curated task lists (cli, full, unlicensed)
├── secret/                   .env + GCP key + per-judge eval keys (real values gitignored)
├── docs/                     Setup/task/extension guides + the docs/ale-docs-site/ HTML site
├── example_exp.yaml          The minimal experiment; start here
└── pyproject.toml            uv workspace; Python ≥3.12, <3.14

Conversational Style

• Keep answers short and concise
• No emojis in commits, issues, PR comments, or code
• No fluff or cheerful filler text
• Technical prose only, be kind but direct (e.g., "Thanks @user" not "Thanks so much @user!")
• When the user asks a question, answer it first before making edits or running implementation commands.
• In docs (README, docs/, user-facing markdown), avoid em dashes (—) when possible; prefer periods, commas, colons, or parentheses instead.

Code Quality

• Read files in full before making wide-ranging changes, before editing files you have not already fully inspected, and when the user asks you to investigate or audit something. Do not rely only on search snippets for broad changes.
• Single-line helper functions with a single call site are forbidden; inline them instead.
• Always ask before removing functionality or code that appears to be intentional.
• Do not preserve backward compatibility unless the user explicitly asks for it.
• Check installed package source (.venv/lib/python*/site-packages/<pkg> or the editable submodules/cua/... paths in pyproject.toml) for external API shapes instead of guessing.
• NEVER remove or downgrade code to fix errors from outdated dependencies; upgrade the dependency instead.