Saving and offline use
Edits save automatically
Section titled “Edits save automatically”You do not need to press a Save button after typing. Cmd/Ctrl+S recompiles the document; it does not confirm that the server received the latest text.
In account mode, supported changes are saved locally before being sent to the server. Watch the sync status to distinguish a local save from a completed sync.
| Status | What to do |
|---|---|
| Saving or queued changes | Keep the workspace open while changes sync. |
| Offline, with queued changes | Reconnect on this device so the pending changes can upload. |
| Sync error | Read the error and use the available retry/recovery controls. |
| No pending changes | You can proceed to check the document on another device. |
Work offline with care
Section titled “Work offline with care”Previously loaded project data may be available offline. A file, font, package, or service that has not been downloaded can still require a connection. Sharing, personal copies, and server AI/Git operations are online workflows.
Do not clear site data, use a cleanup tool, or discard the browser profile while it holds unsynced work. If sync is blocked, download a project ZIP before troubleshooting when possible.
Switch devices
Section titled “Switch devices”- Reconnect the device where you last edited.
- Wait for pending changes to finish syncing.
- Open the project on the next device and check your latest text.
A remote edit from another device, CLI, or integration can conflict with pending local edits. Read any conflict or reload message before continuing. History may contain a checkpoint of the remote version preserved during conflict handling; do not assume all simultaneous edits were merged.
Connected documents normally receive notifications when saved files change elsewhere. A safety check runs every two minutes while notifications are healthy, or every twenty seconds when they are unavailable. Returning to the tab or reconnecting checks promptly. A missed notification can therefore delay a remote-update message; it does not delay your local save or replace conflict handling. Live collaborative text continues to use its own synchronization.
Local mode
Section titled “Local mode”Local-mode projects belong to this browser profile. They are not uploaded to an account. Use project ZIP exports as backups and for transfer to another browser.
See sync and account problems if saving does not settle.
Sign out on a shared device
Section titled “Sign out on a shared device”Choose Account → Sign out. Tylor checks this browser for queued changes, device-only projects, local packages, and saved drafts or imports across all accounts. If none are found, the dialog says so. This is a check of saved browser work at that moment, not a guarantee that another tab has finished syncing.
- Clear browser data and sign out removes this browser’s Tylor documents, cached copies, collaboration snapshots, offline changes and settings for every account. Server documents remain saved. If the dialog lists local work, cancel and sync or export it first.
- Keep browser data and sign out retains recovery data. Use this only on a private device: someone with access to the same browser profile can inspect stored document contents.
The check runs again before clearing. If the counts changed, review the updated message and choose again. If Tylor cannot check or save local work, clearing is unavailable; keep the data or cancel and retry.
Cancel returns without removing anything. If another tab prevents cleanup, close all other Tylor tabs and retry; you can also clear the site’s data in your browser settings. A failed cleanup is reported explicitly. Clearing Tylor does not remove downloaded files, screenshots or browser/OS backups.
Account switches keep offline file caches separate. A server refusal (401, 403 or 404) no longer falls back to cached document content. A genuine network outage still permits recovery of the signed-in account’s cached files. The storage upgrade preserves pending edits; reload older tabs when prompted.