I reviewed an open-source Office suite without opening it once. GenOffice, 10.… · @ReignSwords · TwKit

@ReignSwords

I reviewed an open-source Office suite without opening it once. GenOffice, 10.7k stars, trending on GitHub this week. I skipped the apps and went straight for the CLI — because the apps are for humans, and the CLI is for the agents doing my work. What I ran, on my own machine: 1. md → .docx in 3.8s. Valid OOXML, 5 blocks, opened fine. 2. JSON → .xlsx in 0.9s. My SUM formula came back live — cached value 42, exactly right. 3. .docx → PDF. Failed twice. The exporter needs a display server; it worked once I gave it Xvfb. The part that matters: byte-preserving edits. Only what you change gets rewritten. Everything else survives byte-for-byte, so the file still opens clean in Word. Plus a skill file your coding agent can read, so Claude Code or Codex can build a real .pptx without opening a window. 29 MCP tools, same deal. Cold water: the 188MB download filled my 512MB /tmp and killed the first install. The PDF path drags Electron along. And 'AI edits your files' is still a trust leap — tracked changes and one-click rollback are the whole answer to that, and they have to work every time. Verdict: if your agents already write your docs as markdown soup, this is the first open-source suite that meets them where the work actually lives — inside a real .docx. Would you let an agent edit your actual work files, or is that the one place AI doesn't get to touch? 🔵 Fellow Premium members, let's connect! I post about AI & tech — follow for more 👥

曝光 69 · 评论 9 · 点赞 0 · 书签 0