# CLI troubleshooting

Use the CLI’s built-in checks before resetting configuration or reinstalling the runtime.

## `foxora` is not found

Open a new terminal after installation, then run:

```bash
foxora --version
```

If the command is still unavailable, confirm that the installer’s binary directory is included in your user `PATH`.

## The runtime does not start

```bash
foxora setup
foxora doctor
```

`setup` provisions the engine, Memory Den, and Bun runtime. `doctor` reports which of the engine, runtime, or authentication checks failed.

## Authentication fails

```bash
foxora login
foxora whoami
```

Complete the browser flow, then use `whoami` to confirm which account is active. Use `foxora logout` before signing into a different account.

## Unknown command

```bash
foxora --help
```

CLI v5.0.3 uses plural list commands: `foxora sessions`, `foxora crews`, and `foxora agents`. One-shot prompts must use `foxora run`; a bare quoted prompt is not a command.

## Version or update problems

```bash
foxora --version
foxora update
foxora doctor
```

Record the exact command, version, and diagnostic output before contacting support. Avoid deleting `~/.foxora` as a troubleshooting step because it may contain sessions, runtime state, and Memory Den data.