Birbla

Discussion summary

A new OfficeCLI tool aims to help AI agents read and edit Microsoft Office files, reflecting growing interest in automating document creation. Discussions highlight the importance of Office in corporate environments and explore related tools and models.

What the discussion says

  • Office automation is increasingly relevant for AI agents.
  • Many see Microsoft Office as essential in workplaces.
  • Some compare Office automation to LaTeX or LibreOffice alternatives.
  • Developers are working on models to interact with DOCX files.
  • Questions about handling Excel formulas and macros.
“Office documents have been notoriously difficult to automate for years.”
— charlieyu1
“Most corporate workplaces are super dependent on the Microsoft Office suite.”
— karado

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Feel like overnight I suddenly started seeing so much stuff and comments on here concerning generating Office documents with the LLMs. What could be driving this? Doesn't latex or similar seem like a better fit here?
    by beepbooptheory
  • Nice! i'm making the same - interesting that so many ideas converge. Hopefully we can soon point an GPT6 at all of them and have a super tool. Or else GPT6 can do it without all our helpers...

    https://github.com/odcpw/ooxml-cli

    Glad to get feedback on what doesn't work or is missing.

    I'm also making one for PowerBI - it's in testing. Drop me a line if you're interested.

    by jbgt
  • If you don't need interactive/animated features, I can absolutely recommend to have the agent build slides in HTML and convert it to PDF. Has been a game changer for me.
    by pietz
  • Recently, my experience is that the hardest part of writing Enterprise document by AI is not how to generate a word or excel, but to generate a office document that is accountable. First draft generation is just a small part of the whole wore,more time consuming work is validation: whether citation , number,format, or semantic assume is right.

    So i think enterprise office AI suite may need 2 layers: First is document editing, and second is revision / attribution / validation, or an unaccountable document is not applicable for real enterprise usage.

    by StahlGuo
  • Is it better than letting claude code use python directly ? Especially on those 3 metrics: 1. better prompt adherence 2. visually more pleasing 3. token consumption

    Especially as I think claude code got some reinforcement learning on these use cases ?

    by allan_s
  • > OfficeCLI is the first and best Office suite purpose-built for AI agents to read, edit, and automate Word, Excel, and PowerPoint files. Free, open-source, single binary, no Office installation required.

    1. Calling Microsoft Office simply "Office" without qualification treats it like a trademark, rather than a generic term that was in use for this class of product before MS appropriated it.

    2. If you're going to treat it like a trademark, don't violate it in the same sentence.

    by neilv
  • I went in the opposite direction and built https://smalldocs.org/, which is an office suite AI agents (and humans - including SWEs!) like to use.

    I say it’s as if “Claude Code & Microsoft Office had a baby...”

    Code available: https://github.com/espressoplease/smalldocs

    Discord: https://discord.gg/txjATTsDaq

    Sample document: https://smalldocs.org/blogs/what-is-a-smalldoc

    Invoked via Claude Code by saying stuff like: “sdoc me the plan for this feature”, or “dig into our logs and sdoc me a report on our latency”

    by FailMore
  • Nice, but I don't see a lot of ECMA 376 test cases. Both https://github.com/rcarmo/python-office-mcp-server and https://github.com/rcarmo/go-ooxml are ECMA 376 compliant (I made sure), because for headless generation and handling that's kind of important :)

    Oh, and you're not the first, I started this a year ago. :)

    by rcarmo

Explore Birbla archives