Reference
Look-up documentation for the exact surface: tools, commands, keyboard bindings, configuration, environment, storage, CLI, and supported hosts. Use a guide when you want to finish a task and this section when you need the precise answer.
The generated pages are rendered from the code's registries by npm run docs:reference and checked by npm run docs:check. Do not edit a generated page by hand; change the owning catalog or the reference metadata and regenerate.
Generated reference
| Surface | Page |
|---|---|
| Six native tools: caller, gate, inputs, returns, examples, safety | Native tools |
| Eleven migration/legacy tools, separated from the native path | Migration and legacy tools |
All : commands and the separate / composer catalog | Command reference |
| Keyboard bindings by context | Keyboard reference |
Workspace .ensemble/config.json and stored settings | Configuration |
| Environment variables and state paths | Environment |
.ensemble, AGENTS.md, plugin storage, logs, and edit safety | Files and storage |
| Doctor, data, backup, support bundle, logs, and exit codes | Operator CLI |
| Supported hosts, Node, and contract constants | Supported hosts and versions |
Other reference sources
| Surface | Authoritative page |
|---|---|
| Platform boundary, live-suite prerequisites, and known limitations | Support matrix |
| Runtime requirements and install commands | Requirements and Install |
| Backup, restore, and rollback procedures | Backup and restore and Rollback |
| Workspace configuration, storage, and retention policy | Data classes and retention |
| Release history and current npm tags | Changelog |
| Domain terms | Glossary |
Historical compatibility
Historical host reports stay public as evidence but are not current support claims:
Next
- Concepts: why the surface is shaped this way.
- Operations: procedures that use these commands.
- Contributing: where generated reference and its contract tests live.