Your project is protected by a small set of structural safety guards. An AI assistant works freely inside a live session, and the guards only step in to stop a few genuinely risky moves.
What you can rely on
Inside a live work session, an assistant reads, edits, creates, renames, moves and restores files without asking you each time. SyncNow controls the overall flow, not every single file, so there is no per-file approval queue slowing things down.
The guards block only a handful of structurally unsafe operations, no matter who asks:
- Writing outside your project root
- Reading secrets, credentials or the vault
- Touching the
.syncor.syncnowcontrol folders - Mass deletes with no checkpoint
- Writes while the cloud is unreachable
- Changing server-owned files
- Any command when the session is not live
Each rule maps to a real risk, not to distrust. Today these guards are enforced through the SyncNow bridge: it coordinates what passes through it and can detect and ban bypass attempts.
SyncNow