2.5.1November 2026
Release on GitHub → (opens in a new tab)A patch for two mistakes of ours: the sidebar made Obsidian freeze while Claude Code was busy, and our poll guide for Windows opened a console window every 30 minutes.
Fixed
- Obsidian froze for seconds while Claude Code was busy. On every refresh the sidebar read and parsed all session logs in Claude Code's retention window again, on Obsidian's main thread, and smaller files even twice. The file watcher started such a refresh after every write to the session log, and a busy session writes many times a minute. On our own machine (245 log files, 1.1 GB, 120 days of retention) one refresh took about four seconds and came every four to six seconds, so Obsidian stood still most of the time. The longer your history and the busier your session, the worse it got, and with Claude Code running inside Obsidian it was at its worst. That was our mistake, and we had not noticed it before. Now each log is parsed once and kept in memory: unchanged files are not read again, and a log that grew is read only from where the last read stopped. Measured on the same machine: about 110 ms per refresh instead of four seconds. Only the first refresh after starting Obsidian still reads everything, once
- Our Windows guide for the poll opened a console window on every run. The Task Scheduler commands started
node.exedirectly.node.exeis a console program, so Windows opened a window every time, with the recommended variant every 30 minutes, even on runs that asked nothing. The guide now starts it throughconhost.exe --headless, which keeps the window away, and has one block that switches an existing task over without changing anything else. We tested this on Windows 11. Microsoft does not document this switch, and some security software reports hidden console starts as suspicious; for that case the plain start stays in the guide
Changed
- While a session is busy, the sidebar refreshes at most every 30 seconds. Up to 2.5.0 every write restarted a short wait of 0.6 seconds, so a busy session set off one refresh after another. The first response after a quiet spell still shows up after 0.6 seconds; while writes keep coming, the next refresh follows at the latest 30 seconds after the previous one and includes everything written until then. The refresh button and the interval in the settings are not throttled
- The settings text no longer says the file watcher reacts immediately to every response, in all five languages. With the 30-second limit that is no longer true; it now says "within 30 seconds at the latest". The help page says the same
- Every hour is enough for the poll that runs only while you work. We recommended every 30 minutes. That is twice the requests for a reading that is at most half an hour fresher. The guide, the cron line, the script header and the help page now say every hour