We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
docs: correct stale resident-mode and batch claims Audit pass for statements that misrepresent current behavior: - Operating-modes tables labelled "Direct Mode (Default)", but auto-resident is the default. Recast as Resident (default) / Direct (OFFICECLI_NO_AUTO_RESIDENT=1) in command-reference and workflows. - "batch ... atomically": batch is not atomic — it continues on error by default and keeps succeeded changes (no rollback). Reworded across Home, workflows, troubleshooting, command-reference to "in one pass", with an explicit not-atomic note where useful. Fixed command-batch Notes that contradicted its own intro. - Idle timeout: stated a flat "12 minutes", but an auto-started resident uses 60s (12 min only after explicit open); also note the ~10s idle auto-save. Corrected in command-open, command-save, troubleshooting. - "one open/save cycle" -> "single pass" where a resident actually defers the flush.
docs: document the resident flush model (idle-autosave + save/close) A live resident defers the disk write, so a non-officecli reader that opens the file directly sees the pre-edit content until a flush. Document the four flush triggers and make the boundary rule explicit. - command-open: authoritative "When the file on disk is refreshed" matrix — idle auto-save (flush + keep), idle shutdown (flush + stop), save, close; OFFICECLI_RESIDENT_IDLE_SAVE_SECONDS to tune the auto-save. - command-save: new page for the save command; flush triggers comparison. - command-batch: standalone batch saves on its own; a batch forwarded into a live resident defers like single commands. - agent-guide / troubleshooting: officecli's own reads always see edits, so flush only matters before a non-officecli program reads the file; link to the command-open matrix instead of duplicating it.
docs: surface save/close deferred-flush for third-party readers While a resident process is alive, edits are applied in memory and the file on disk is only rewritten on save, close, or idle-timeout. OfficeCLI commands read the in-memory copy, but a tool that opens the file directly (python-docx, PizZip, openpyxl, pandas, Word, a renderer) sees the pre-edit file until a flush. The save command had no wiki page and was absent from the command table, so this case was undiscoverable. - Add command-save.md: save flushes to disk while keeping the resident running (mid-session reads); close flushes and stops; NO_AUTO_RESIDENT write-through. - command-reference: add the missing save row; clarify close flushes to disk. - command-open: add a Deferred-flush section and link save. - agent-guide: add a Flush workflow step and a Persistence section. - troubleshooting: add "edit reports success but a third-party tool reads the old file", leading with save.