If an AI assistant cannot connect, it is almost always because SyncNow is not running, no session is live, or the bridge details it is using are out of date.
How the connection works
An assistant only reaches your project through SyncNow's local proxy on 127.0.0.1, using a one-time password from .syncnow/agent_bridge.json. That file's port and token rotate, so a stale copy will be rejected.
What to check
- SyncNow is open on this PC, so the local bridge is listening.
- A session is active for that project. With no live session, the proxy refuses commands.
- The assistant re-read the current
agent_bridge.jsoninstead of an old port or token. - The cloud is reachable, since the proxy needs the cloud executor to do the real work.
Get it going
- Confirm the project is observed and the cloud is up.
- Start a fresh session, then have the assistant re-read the bridge file.
- If it was revoked or banned, the project must release it before a new turn.
Note that repeated attempts to bypass the proxy and use FTP directly are treated as grave violations and can get an assistant banned, so fix the connection properly.
SyncNow