Anyone that can help me with this error. First time to see these:
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114257.105.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114301.589.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114306.013.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114311.787.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114341.794.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114346.928.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114352.067.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114421.594.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114426.747.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114431.924.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114336.632.txt’ instead of ‘uivision_log.txt’
Status=Error: localStorageExport: the browser saved the file as ‘uivision_log - 2026-08-27T114416.415.txt’ instead of ‘uivision_log.txt’
Thanks for the error log. Below is what our coding AI suggests as cause. Does that sound reasonable to you? Could that be? Do you have another tool that does a file rename?
Short version: Ui.Vision isn’t doing the renaming — something else in your browser is, and Ui.Vision only recently started noticing.
What the error means
localStorageExport (without XModules) asks Chrome’s downloads API to save the log as uivision_log.txt, suggesting exactly that name with conflictAction: ‘uniquify’ (bg.js:95). Since v10.0.131 the panel then verifies the actual on-disk name the browser reports back, because Chromium stopped reliably honoring requested filenames for blob: URLs. A plain (1) dedupe suffix is tolerated; anything else fails loudly (run_command.ts:1894-1904).
The files are being saved and contain the log - just under the wrong name, and now the extension reports that instead of silently claiming success. That’s why it’s “first time to see these”: before 10.0.131 the same rename would have gone unnoticed.
Who adds the timestamp
Nothing in our codebase ever produces a name - 2026-08-27T114257.105.txt pattern (ISO timestamp, colons stripped, milliseconds kept) — I grepped the whole source to confirm. That is the signature of a filename-rewriting browser extension or download tool resolving the name conflict its own way: each ~5-second loop iteration collides with the existing uivision_log.txt, and instead of Chrome’s normal (1) uniquify, something appends a timestamp. Chrome allows only one winner for onDeterminingFilename across extensions — the most recently installed extension’s suggestion overrides ours, which matches exactly this symptom. Typical culprits: download managers/organizers, “rename duplicate downloads”, “overwrite existing files” helpers, or a corporate-managed browser add-on.
The file is exported successfully each time — just renamed by something outside Ui.Vision.
Check chrome://extensions for any download-manager / file-renamer extension and disable it (or test in a fresh profile / another browser to confirm). Chrome only lets one extension control download filenames, and the newest-installed one wins.
Also check the browser’s download settings and any endpoint-security software if it’s a company machine.
Workaround: If a stable filename matters (e.g. a script picks the file up afterwards), installing the XModules FileAccess module sidesteps the browser’s download naming entirely (localStorageExport | path=… writes directly to disk).