Troubleshooting
Find the reason a task is blocked and the next step to fix it.
Start with the exact message in Work, Review, or Setup. A failed check and a failed Apply need different fixes.
Common problems
| Problem | Next step |
|---|---|
| An agent is missing or its sign-in is unknown | Finish the agent's installation or sign-in, then recheck in Setup |
| OpenCode reads "No OpenCode provider connected" | Store a provider with opencode auth login; agents do not receive API keys from your shell |
| A worker card shows "No changes" | The agent finished and passed its checks without editing files. Make that task's prompt name the file and the change |
| A plan cannot run | Read the blocker, fix its configuration, and build a fresh plan |
| No verification command was found | Add a test or build command that works in this project |
| Checks fail | Read the recorded command output; passing worker text is not a check result |
| Review is stale | Refresh the candidate and review the new files and checks |
| Apply was interrupted | Read the recorded recovery state before retrying |
| The installed app looks different | Check its version in Setup; these guides describe the release on Download |
For Desktop setup issues, see Desktop setup. For stale, blocked, or interrupted Apply, see Review and Apply.
CLI and editor issues
Run pytxo doctor if you have the CLI installed. It checks local setup; it does not prove a task or Apply succeeded.
Ask for help
Include your Pytxo version, operating system, the action you tried, and the exact error. Remove keys, tokens, and private repository content from anything you share.