# Overview

Diagnose Foxora systematically by isolating the failing layer, preserving evidence, applying one reversible fix, and verifying with the same test.

## 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. Diagnose Foxora systematically by isolating the failing layer, preserving evidence, applying one reversible fix, and verifying with the same test.
3. Reproduce once with the smallest safe input, capture exact time and error, preserve logs and project state, check versions and service status, then change one variable.
4. **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.