Troubleshooting

Start with the dashboard. Devices shows pairing, Online, Offline, Revoked and Update required states. Repositories shows pending, applied and rejected configuration.

For advanced local diagnostics, run:

repohop doctor

Device stays offline

Choose Open RepoHop Local again. Confirm the RepoHop Local service can make outbound HTTPS and WebSocket connections. If needed, restart it:

repohop service restart

If the dashboard says Revoked or Update required, pair again or update instead of repeatedly restarting.

Pairing code expired

Create a new code from Devices. Codes are short-lived and single-use. A consumed or expired code cannot be restored.

If the installed launcher does not open, expand Use the terminal instead and run the displayed fallback command on that computer.

A setting is pending

Look for the RepoHop Local confirmation on the selected computer. Reductions do not need approval. If no graphical confirmation or folder chooser is available, use the fallback commands:

repohop repos
repohop add WORKSPACE_ID /path/to/repository

Use the workspace ID shown by the first command. The path remains local. If the configuration changed after the prompt opened, return to the dashboard and submit the current settings again.

Write reports a stale SHA

Another process changed the file. Ask the agent to read it again and apply a new patch to the current SHA. RepoHop does not overwrite a changed file.

Push is rejected

RepoHop only pushes fast-forward changes. Fetch and reconcile the remote changes locally, review the result, then try again. Force push is not available.

Need an immediate stop

Run repohop freeze, then revoke the connection or device in the dashboard if needed.