Repository Layout
A practical map of the main folders and what each one owns.
This is how we organize the repository:
src/gym_anything/ core runtime, remote stack, dashboards
benchmarks/cua_world/ benchmark environments, tasks, splits, registry, reports
agents/ reference agents and evaluation programs
tests/ automated tests
docs/ Mintlify docs project
website/ project website source
legacy/mkdocs/ archived older docs site
examples/tutorials/ small example environmentssrc/gym_anything/
This is the framework itself.
It contains:
- environment loading and lifecycle
- runner implementations
- verification code
- remote client, master, worker, and dashboard apps
- packaged dashboards
If a change affects how environments are defined, started, stepped, or closed, this is usually the right place.
benchmarks/cua_world/
This is our main benchmark suite.
It contains:
environments/: environment folders and task folderssplits/: named task lists such astrain,test,all, andverifiedregistry/: helpers that load and resolve split informationreports/: generated benchmark reportshistorical/: archived older material
If a change is specific to one benchmark environment or one benchmark task, it should usually stay here.
agents/
This is our reference agent layer.
It contains:
agents/: agent classesevaluation/: programs such asrun_singleandrun_batchshared/: shared prompt and model-client helpers
If a change affects how reference agents decide actions or how the agent loop is run, it belongs here.
tests/
The test suite is organized mostly by behavior:
- public API and CLI contracts
- environment lifecycle
- verification and benchmark registry
- remote cluster behavior
- runner execution contracts
- agent evaluation loop behavior
When you change behavior, update the nearest existing test before adding a new file.
docs/ and website/
These are separate on purpose:
docs/is the Fumadocs docs projectwebsite/is the landing site source
The older MkDocs site is kept under legacy/mkdocs/.