-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No — the .rm v6 format is only on reMarkable 2 and Paper Pro. The
old v5 format isn't supported by rmscene.
Only where you tell it to. reMarkable Cloud is required (it's how we read the notes); OCR may send page images to Google Vision or a VLM if you configured those; the processing pipeline calls Anthropic's API for actions/tags/summaries; optional integrations (Notion, OneNote, Teams) send to those services.
Nothing else leaves your infrastructure. The state DB is local.
Partially. The reMarkable Cloud sync itself requires the Cloud — there's no LAN-only path to the tablet. Once notes are downloaded, you can run fully offline if you use:
-
ocr.primary: remarkable_builtinwithocr.fallback: none -
processingdisabled (setextract_actions: false,extract_tags: false,generate_summary: false) — which leaves the notes as raw OCR text without enrichment -
search.backend: localwithsearch.synthesize_answer: false
Obsidian's "vault is just files" model is what makes this possible —
the bridge writes Markdown with YAML frontmatter, git does the
rest. You can mirror into Notion as well (see the Notion
integration). Logseq-compatible output is mostly working but
untested; file issues if you try it.
Not for the processing pipeline yet. The tagger/structurer prompts assume Claude-style tool-use semantics. Patches welcome.
No — reverse sync renders Obsidian notes as printed PDFs (or native empty notebooks) and uploads those. Your handwriting on those pages gets OCR'd back on the next sync cycle as normal.
No. Multi-device puts each tablet's notes under its own
vault_subfolder. Existing single-device notes stay where they
were (no device_id set, effectively the "default" device). If you
want them under a subfolder too, move the files manually and adjust
sync_state.vault_path rows in the state DB.
Tested up to ~2k synced notes on a 2-core VPS. Bottleneck at that
scale is the OCR step (network + compute on fallback engines), not
the SQLite layer. Semantic indexing is the other slow step — batch
it overnight with remark-bridge reindex.
Technically yes (the state DBs are independent), but you'd get duplicate writes. Don't do it. One bridge per vault.
The web dashboard is a PWA — install it to your phone's home screen from the browser and you get a near-native UX. For Obsidian integration on mobile, use the same companion plugin; Obsidian mobile supports community plugins.
# Stop running processes
pkill -f remark-bridge
# or: sudo systemctl disable --now remark-bridge-sync.timer remark-bridge-web.service
# or: docker compose down -v
# Remove state + tokens (reversible — back up first if you want to keep history)
rm -rf ~/.remark-bridge/
# Uninstall the package
pip uninstall remark-bridgeThe Obsidian vault contents are yours to keep.
CC BY-NC 4.0. Non-commercial use, attribution required. Commercial licensing available — open an issue or email the author.
reMark Bridge · v0.7.0 · CC BY-NC 4.0 · author BGGBTAC · contributions welcome — see Contributing
Home · v0.8.0
Getting started
Features
- Multi-Device
- Search
- Templates
- Plugins
- Bridge-API
- Obsidian-Plugin
- Web-Dashboard
- Users
- Audit-Log
- Reports
Ops
Dev