Skip to main content
ancha scene works with scene files, the YAML files ancha run uses. See Test file for the format.

​
ancha scene new

Output
It writes scene.yaml, tasks.json and the reference companions oracle.mjs, oracle.ts, null.mjs and null.ts into scenes/<id>/. The scene starts as an access check, like the starter: a minimal seed for each tool and one trace check per tool. Replace the task and checks with your own. The ID must be lowercase letters, digits and hyphens. An existing destination is rejected. --twins accepts slack, github, datadog and pagerduty.

​
ancha scene validate

Output
Invalid files exit 2 and list every problem with its path:
Output

​
ancha scene simulate

Without a companion flag, simulate runs the world with no agent up to --until (default: the scene’s timeout) and shows how the checks stand. Use it to see what a living world does on its own. A preview exits 0 even when checks fail:
Output
--oracle runs the scene’s oracle companion as the agent, which should pass. --null runs the null companion, which should exit cleanly and fail the checks (exit 1). Together they show that the checks can tell a good response from a useless one. A .mjs companion is preferred over a .ts one with the same name.

​
ancha scene schema

Prints the JSON Schema of scene files, always as JSON. Point your editor’s YAML language server at it for completion and validation.

​
Exit codes

0 on success. 1 when a companion’s checks fail. 2 for invalid scenes or usage. 3 for infrastructure failures. 4 for coverage gaps in a companion run.