> 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.
MS doesn’t need a reason to take your code down from GitHub. If they don’t like what your code does, they can take it down no matter how you word your readme.
Notably the posted project is Apache licensed, and your project is Elastic licensed. Your project looks cool and you've clearly put a lot of thought into making it useful, but the license makes it a non-starter for me.
> Elastic License 2.0. The source is public and you may use, copy, modify, and redistribute it. You may not offer SmallDocs to third parties as a hosted or managed service, strip its licensing notices, or circumvent its license-key functionality.
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.
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?
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.
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 ?
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...
32 comments
[ 4.1 ms ] story [ 68.4 ms ] thread1. 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.
Oh, and you're not the first, I started this a year ago. :)
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”
It is not open source unfortunately.
im working on something similar. A fine-tuned model for agents to interact with docx over MCP. they wont have to deal with OOXML vespper.com
im working on something similar. A fine-tuned model for agents to interact with docx over MCP. they wont have to deal with OOXML.
we have a waiting list for beta-users: www.vespper.com
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.
Especially as I think claude code got some reinforcement learning on these use cases ?
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.