If the local proxy or the cloud behind it is not reachable, an assistant simply cannot act on your project - and that is the safe outcome, not a broken one.
Why work pauses
The assistant only reaches your files through the proxy on 127.0.0.1 and SyncNow's cloud executor. If either is down, there is no path to your FTP host. Rather than let a change slip through uncoordinated, SyncNow blocks writes while the cloud is unreachable, so your site is never touched outside the proper channel.
Common causes
- SyncNow is not running, so the local bridge is not listening.
- The cloud is temporarily unreachable (a network or service hiccup).
- The session ended, expired, or was revoked, so the proxy details rotated.
How to get going again
- Confirm SyncNow is open and the project shows as observed.
- Wait for the cloud connection to recover - work resumes automatically.
- Have the assistant re-read
agent_bridge.jsonand, if needed, request a fresh Grant to START again.
SyncNow