# Task and project problems

Confirm the active local task and project path, folder availability, repository state, permissions, and free disk space; test read access before edits.

## 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. Reproduce the problem once with the smallest safe input and record the exact message, action, and time.
3. Confirm the active local task and project path, folder availability, repository state, permissions, and free disk space.
4. Test read access before edits.
5. Change one reversible condition, then repeat the same test. Preserve logs or exports before any reset.
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.