# CLI troubleshooting

Use version, environment, account, and doctor output to isolate a CLI failure before reinstalling or touching local data.

1. If `foxora` is not found, open a new terminal and confirm the package manager’s binary directory is on `PATH`.
2. Run `foxora --version` and `foxora env` to record the installed client and selected environment.
3. Run `foxora whoami`; if needed, use `foxora logout` followed by `foxora login`.
4. Run `foxora doctor` to check engine, local runtime, authentication, and gateway.
5. If the runtime is missing, run `foxora setup`; if a command is unknown, run `foxora --help`.

Do not delete `~/.foxora` or `%USERPROFILE%\.foxora` as a quick fix: it can contain sessions, memory, settings, and login state. Preserve the exact failing command and output for support.

**Expected result:** one failing layer is named, and the same command succeeds after a single targeted repair.
