Feature verification checks the behavior of a specific feature. Environment commands check whether the project can be installed, built, run, or subjected to end-to-end checks. They serve different purposes.
Configure commands as needed in harness.config.json:
Every key is optional. The current CLI runs configured commands in bootstrap, verify, e2e, and health order during env check, stopping at the first failure. start and cleanup document workflow and project runtime conventions; env check does not automatically orchestrate them as background processes.
List and run checks
Options: List environment commands · Run environment checks
When no commands are configured, env check reports that there is nothing to check and exits successfully. Once configured, each item shows the actual command, PASS/FAIL result, and exit code.
Close a session
See the session close command →
This command:
- Runs repository-level
validate.
- Runs the configured environment checks.
- Summarizes the current commit and the number of uncommitted files.
- Reports feature status and suggested next steps.
Validation or environment-check failures produce a nonzero exit code. Uncommitted changes are reported explicitly but are not failures by themselves, because a session may intentionally leave uncommitted work for handoff.
session close is a read-only report. It does not commit automatically, change feature state, release a claim, or delete a workspace. Perform those actions as appropriate based on the report.
