Troubleshooting
Start from the component that owns the failure, then recheck current truth without deleting durable state.
Agent not found or not signed in
- Open Setup or Doctor and distinguish not installed, unsupported version, misconfigured, and unavailable states.
- Confirm the provider works for the same operating-system user that runs CodeTether.
- Use the provider’s own supported login flow; do not paste credentials into CodeTether.
- Run the explicit provider check again after correcting the installation or login.
Machine is offline
- Confirm the execution machine is awake and its CodeTether Desktop or Node service is running.
- Check whether the displayed status is current or only last known.
- For Relay use, verify both peers are enrolled and the machine path passes its authenticated qualification check.
Connection or pairing fails
Use one fresh pairing session and verify the exact target surfaced by the product. Pairing codes expire and must not be invented, reused, or replaced with a guessed Relay address.
A session cannot continue
Confirm the original project location, machine, provider installation, and native session still exist. CodeTether will preserve readable history but will not fork or replay the session when native resume is unavailable.
Notifications do not appear
- Check the operating system notification permission for CodeTether.
- Review the Desktop notification preferences for approvals, completed review, and failed turns.
- A focused visible window may suppress a notification when the exact attention is already on screen.
- Inbox history remains the durable place to inspect attention even when native delivery is unavailable.
CodeTether never treats a lost network response as permission to replay provider work automatically. When execution ownership is uncertain, inspect the conversation before starting a fresh task.