Obsidian Bridge¶
HTTP bridge to Obsidian — eval_js, latency handling, timeout retry rules
Ports¶
27125
Entry points¶
work_buddy.obsidian.bridge
Details¶
The obsidian-work-buddy plugin exposes an HTTP bridge on port 27125. Key functions: bridge.eval_js(code) executes JavaScript inside Obsidian with access to the app object, bridge.require_available() checks connectivity.
Latency: The bridge has intermittent latency spikes (up to ~4s). is_available() handles this with a 10s timeout and 15s fallback on first contact. Do not reduce these timeouts.
Critical — do not bypass the bridge on timeout: 1. Retry the same call — it will almost certainly succeed 2. Do NOT fall back to the Local REST API (port 27124) — same latency behavior 3. Do NOT write directly to vault files — causes sync conflicts 4. If 2-3 retries fail, then Obsidian is genuinely not running — report the error