Sync and live updates
CLI refresh, extension imports, cloud sync, and conflicts.
Local persistence
Papers, notes, collections, PDF annotations, and local manuscript copies persist when you quit Avera. Open tabs may not restore, but data in the database remains.
CLI and desktop together
When the app is running:
avera import-doi 10.1038/nature12373The library usually updates without manual refresh.
To import silently:
avera --no-notify import-doi <doi>The paper is in the database; the UI refreshes on the next navigation or reload.
Browser connector
Imports from Chrome trigger a toast and library refresh similar to CLI imports.
Cloud sync (Pro)
Signed-in subscribers sync selected data to the cloud backend:
| Data | Behavior |
|---|---|
| Manuscripts | Edits sync between sessions after a short interval |
| Screening decisions | Teammates see progress and conflicts |
| Team notes | Visible to teammates on shared papers |
Offline screening and writing queue locally; sync catches up when online.
Note conflicts
Editing the same note in two places (two app sessions, or app + CLI) may trigger a conflict banner. Choose to reload the remote version or resolve manually.
The same concurrency rules apply to optimistic saves on collaborative team notes.
Annotation sync
PDF markup syncs for subscribed accounts when file hashes match. Replacing a PDF may hide old marks — re-annotate on the new file if needed.
See Offline and data for what requires network access.