Whether an assistant is reading a file or saving changes, it always goes through SyncNow's proxy - never straight to your server.
The round trip
- The assistant sends a read or write request to the local proxy on
127.0.0.1, using its one-time password. - SyncNow forwards it to the cloud executor, which uses your vaulted credentials to act on your FTP host.
- The result comes back to the assistant, and the change is recorded on the shared timeline.
When a write is held back
Reads flow freely within a live session. Writes - create, modify, delete, rename, move, copy, restore - flow freely too, but pass through the safety guards first. A write is refused when:
- The target is outside the project root.
- A mass delete is attempted without a checkpoint.
- The cloud is unreachable, or the session is not live.
The point is not to slow good work - it is to make sure every change is coordinated, recorded, and reversible.
SyncNow