LMOS VOID Beta 0.41.0: Real Save-Back, Font Fidelity Guardrails, and LM Text to Phone
LM Office can now retain writable local-file handles and save Word, Slides and Sheets back to the user’s own file, update compatible files in Google Drive, warn when required fonts are missing, and LM Communications gains prepaid outbound SMS infrastructure.
What changed
Open local DOCX/PPTX/XLSX files through a permission-scoped file handle when the browser supports it.
Save LM Word, LM Slides and LM Sheets back to the same local file after explicit write permission.
Save As links the newly chosen local file for future Save-back.
Update compatible Office files back to the same Google Drive file.
Protect Google-native Docs/Slides/Sheets from lossy overwrite by saving a converted copy until native write APIs are enabled.
Share the media-preserving LM Slides PowerPoint serializer with the source Save-back pipeline.
Read DOCX default/style fonts before run-level overrides.
Record referenced fonts and warn when the current device cannot render a requested family.
Add outbound LM Text → phone SMS through Twilio with wallet reservation/failure release/final charge semantics.
Price SMS per segment and show the estimate before Send.
Never store the SMS body inside billing ledger metadata.
Why this matters
A creator should be able to keep a real file on their own Mac, Windows PC or Google Drive, open it in LMOS, work, and save it without surrendering the file to a proprietary LM storage silo. The same rule applies to communications: external carrier services should be optional bridges behind LMOS, with visible costs and explicit provider boundaries.
Still deliberately gated
Exact Apple Pages, Keynote and Numbers round-trip remains assigned to the macOS NativeProvider. Google-native Docs/Slides/Sheets are currently imported through Google export and saved as converted Office copies rather than destructively rewritten. Incoming carrier SMS, phone-number provisioning and production voice calling remain later communications gates.
Use the beta on real work.
The most useful feedback is not “I like it.” Tell us where you hesitated, what took too many clicks, what did not save the way you expected, and what would make this useful enough to return to next week.