# Contacting support

Search relevant documentation, prepare the redacted diagnostic bundle, describe impact and the smallest reproduction, include identifiers and time, then use the official support channel.

## Where this lives

Open the failing surface and preserve the exact error before changing configuration.

Troubleshooting starts by identifying the failing layer: installation, runtime, account, local project, agent configuration, tool, browser, automation, or external connection.

> **Safety:** Redact tokens, passwords, private prompts, personal data, local paths, and proprietary file contents before sharing diagnostics. Avoid resets until evidence and local exports are preserved.

## Steps

1. Open the failing surface and preserve the exact error before changing configuration.
2. Search relevant documentation.
3. Prepare the redacted diagnostic bundle.
4. Describe impact and the smallest reproduction, include identifiers and time.
5. Use the official support channel.
6. **Confirm the result.** Repeat the identical minimal test, confirm the error is gone and the original workflow works, and remove any temporary diagnostic access or configuration.

## Choose the right path

- Use `foxora doctor` for CLI, engine, runtime, and authentication checks.
- Use run or task logs for agent and automation failures.
- Use connection tests for plugins, channels, MCP, browser, and providers.


## Confirm it worked

- Repeat the identical minimal test, confirm the error is gone and the original workflow works, and remove any temporary diagnostic access or configuration.
- The screen, command, file, run, or destination named in this guide reflects the expected state.