this is awesome - I wonder how this would combine with DSL tools like https://slangify.org
Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
21–30 of 37 posts
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#22this is awesome - I wonder how this would combine with DSL tools like https://slangify.org
honestly, worth a try! might be easier for the LLMs than authoring CLI commands.
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#23I know that the office suite format is a relic which is hard to get rid of. But I can't help feeling that in these new AI era, that we should focus on leaving that proprietary format behind. It is one of the biggest facilitator of vendor lock in in the history of computing.
Hey, I'm building something a bit like that - please checkout https://smalldocs.org if you have time.
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"
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#24This is great - and another example of how much more efficient CLI tool use ends up being in actual day-to-day use. Claude Code and Hermes took it in and it runs great in my initial tries at it. Thanks for making and sharing it!
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#25I know that the office suite format is a relic which is hard to get rid of. But I can't help feeling that in these new AI era, that we should focus on leaving that proprietary format behind. It is one of the biggest facilitator of vendor lock in in the history of computing.
Realistically... everyone's using it from students, to lawyers, to academics, and so on and so forth.
And given that LibreOffice and Google Docs are pretty good nowadays and OOXML is an open standard now post the monopoly rulings of the 90s, it's not quite as bad as it used to be.
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#26There have been a few similar posts on HN recently for working with MS Office docs:
https://github.com/iOfficeAI/OfficeCLI
https://github.com/rcarmo/python-office-mcp-server
https://github.com/espressoplease/smalldocs
It would be great to see some benchmarks for token use, correctness, features etc.
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#27There have been a few similar posts on HN recently for working with MS Office docs: https://github.com/iOfficeAI/OfficeCLI https://github.com/rcarmo/python-office-mcp-server https://github.com/espressoplease/smalldocs It would be great to see some benchmarks for token use, correctness, features etc.
fair point! i've got some stats in the body of the github, and a skill that has the eval that i've built for it.
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#28I haven’t looked under the hood here but to make simple text replacement via command line is an LLM even required? A human driven command line tool to do basic substitution on batches of files reliably would be amazing.
sed, awk. docx is just zipped xml.
It is just zipped xml, but to do a search and replace while retaining document structure is very very complicated, and I’m struggling to think of how to combine sed and awk to achieve it.
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#29I've done many custom low token output CLIs like this for my day job and it's something I expect to see much more of.
How would you compare that approach to spawning sub agents to operate high-token tools?
Re: Show HN: Docx-CLI: agents read/edit Word docs using 1/2 the time and tokens
#30[flagged]