ancha env

An environment is a live copy of a scene’s world on a server. ancha run creates one per trial for you. Use ancha env to create one by hand, for example to develop against a scene’s data while you write the agent. Start a server first with ancha serve, or configure one.

ancha env up

ancha env up [options] <scene>

Argument	Description
`scene`	Scene YAML file

Option	Description
`--seed <seed>`	Seed for ids and randomness (default: “<scene id>:1”)
`--ttl <duration>`	Wall-time lease from 1s to 24h (default: 30m)

ancha env up scenes/starter/scene.yaml

Output

env opz1zm6z (scene starter)
  slack: http://127.0.0.1:4400/e/opz1zm6z/slack/api/  token <fake token>
  github: http://127.0.0.1:4400/e/opz1zm6z/github  token <fake token>
  datadog: http://127.0.0.1:4400/e/opz1zm6z/datadog  token <fake token>
  pagerduty: http://127.0.0.1:4400/e/opz1zm6z/pagerduty  token <fake token>

The environment expires after its lease, 30 minutes by default. --json returns the IDs, URLs and credentials for scripts.

ancha env list

ancha env list [options]

Output

env opz1zm6z (scene starter)  created 2026-10-31T07:50:45.244Z  expires 2026-10-31T08:20:45.244Z

Sandboxes appear here too, with a sandbox-… scene ID.

ancha env reset

ancha env reset [options] <id>

Argument	Description
`id`	Environment id

Output

reset env opz1zm6z in 2.6987499999813735 ms

Restores the environment’s initial data. It keeps the same URLs and credentials.

ancha env down

ancha env down [options] <id>

Argument	Description
`id`	Environment id

Output

env opz1zm6z destroyed

Exit codes

0 on success. 2 for an invalid scene. 3 when the server cannot be reached or the environment does not exist (ENV_NOT_FOUND).

Get started

Guides

Concepts

Tools

CLI

Reference

Cloud

Help

ancha env up

ancha env list

ancha env reset

ancha env down

Exit codes

​ancha env up

​ancha env list

​ancha env reset

​ancha env down

​Exit codes

ancha env up

ancha env list

ancha env reset

ancha env down

Exit codes