# jan-cli current behavior
This file previously captured a June 2026 implementation snapshot. It described
removed spec flags, environment variables, cwd discovery, and a well-known
fallback directory as if they were current interfaces. They are no longer
supported.
The current model has one spec-selection mechanism:
```bash
jan use /path/to/reviewed-tree
jan --help
```
`jan use` persists the selected directory. The tree's entry YAML and reachable
`include:` files define the live command set. `jan bundle` and `jan alias`
operate on that preferred tree; generated aliases invoke bare `jan` command
chains and do not embed spec-selection flags.
Bundle installation verifies archive structure, member hashes, and sizes, but
does not authenticate the publisher and does not activate the extracted tree.
Review it before explicitly running `jan use`.
For maintained documentation, use:
- The MkDocs site (`./serve.sh` from `jan-cli/`) — full reference
- [README.md](../README.md) — concise front door
- [PORTABLE_SCRIPTS.md](PORTABLE_SCRIPTS.md) — export and import workflow
- [SECURITY.md](../SECURITY.md) — trust model and security findings
A preferred jan tree can execute arbitrary programs with the current user's
permissions. It is not sandboxed configuration.