# RX is not found

If your shell reports that `rx` is not found, first check command discovery. This symptom occurs before provider sign-in or model execution; changing credentials will not fix it.

## Preserve the useful evidence

Keep the exact non-secret shell error, terminal type, and installation method. Do not paste your entire environment or process inventory into a support request.

## Check the command location

1. In the same shell that failed, run:

   ```bash
   command -v rx
   printf '%s
' "$PATH"
   ```

2. Check whether the result names the intended installation. The [documented installer](https://raw.githubusercontent.com/Ouros-AI/rx/a0759a2dd969bd15c83f74b2557a4e8b520281a9/README.md) places RX under `~/.local/share/rx` and links `~/.local/bin/rx`. If that link exists but its directory is absent from `PATH`, use your shell's normal startup configuration to add the directory. Preserve unrelated configuration; do not replace the entire `PATH`.
3. Open a fresh terminal after changing shell startup configuration. Run `command -v rx` again, then:

   ```bash
   rx --version
   rx --help
   ```

If the command path is missing or broken, return to the maintained [installation instructions](https://github.com/Ouros-AI/rx#installation-and-update). Do not execute an installer copied from an untrusted error message or use `rx update` as a command-discovery diagnostic.

## Check the correction

The same shell must locate RX and display version/help without submitting a task. That establishes executable discovery, not provider access or completed project work. Continue with [Open a workspace](/docs/agent-rx/quickstart).

## If it still fails

Use this report template with the version left explicitly unavailable if RX cannot run. Attach only the relevant path/error excerpt, redacted where necessary.

```markdown
# Support report

- Product and installed version:
- Exact action:
- Expected result:
- Observed result and non-secret error:
- Relevant operation/run ID, if safe to share:
- Steps already tried:
- Work preserved before retrying:
```

Send the minimal report through [shared support](/docs/shared/support). Distinguish command-not-found from an executable that is found but fails to start.