Top
Best
New

Posted by timpera 10 hours ago

The ChatGPT/Codex app bundles a full copy of LibreOffice(simonwillison.net)
333 points | 152 commentspage 3
dvduval 9 hours ago|
My agent did it? I didn’t do it.
trentor 10 hours ago||
I don't see the problem?
iAMkenough 10 hours ago|
Who said it was a problem? This looks like an observation to me, not an accusation.
robomartin 6 hours ago||
Last time I used the Windows version it pegged all my cores at 100% usage for some reason. The machine became unusable. Instead I used Codex with JetBrains Rider (doing a C# project) and it worked flawlessly.
FailMore 8 hours ago||
(I made a similar comment in a different post by Simon Willison yesterday about GPT Work)

I am unsure the direction that AI assisted document creation work will go in. I am opinionated and building something in the space. In this reply I discuss my view + what I have been building.

My opinion is: We now have AI, this new amazing flexible tool. We can throw it at any problem. But in terms of document creation we have a choice between old fashioned siloed document formats (.pptx, .pdf, .xlsx, .docx, etc.) and a freshly rendered - slightly randomly styled - html site with some basic javascript within it. I think these combinations are odd and do not maximise the powers of AI.

I've been building something called SmallDocs [0][1] which is a new take on work documents. It's all Markdown, but it always renders (100% privately) on the SmallDocs site. This means the SmallDocs renderer can convert recognised Markdown combinations into powerful traditional document formats [2]. For example, we convert a ```cells block into an in-line spreadsheet you can export to Excel.

This gives an agent the ability to express itself with a great deal of depth and flexibility. For example, your agent can produce a single data analysis "SmallDoc" with text, charts, spreadsheets, etc. [3] I find that combining formats quickens the speed I can understand a topic.

SmallDocs also have standardised and pretty boring styling. This means you spend less time understanding the layout of a flashy HTML page and more time on the content.

I also believe a pre-determined rendering engine has a lot of advantages over a freslhy built HTML artifact. It allows you to build in lot's of useful defaults that the agent doesn't have to code from scratch. These can be small things, for example, every time your agent renders a Markdown table in SmallDocs you can instantly copy it as a CSV or a PNG. And these can be bigger things, such as a rich slides DSL with solid styling defaults, which saves your agents a lot of tokens and results in consistently attractive HTML slides [4]. (Slides can also be automatically exported to .pdf and .pptx.)

I've been at it for a few months, and am still working on the project. I am looking for feedback and open source collaborators. Thanks for reading!

[0] https://smalldocs.org

[1] https://github.com/espressoplease/smalldocs

[2] https://smalldocs.org/blogs/what-is-a-smalldoc

[3] https://smalldocs.org/s/46fWiAyF77T9c7tqYwAQqp#k=j78ZEOOrgo8...

[4] https://smalldocs.org/s/QrmeWMsULGS871nXQYOacB#k=ubOHH9QtTWp...

(And something totally different, your agent can also use SmallDocs to walk you through code files: https://smalldocs.org/s/JsI_-tWSH0UpSd_YXxVLPm#k=G5jLCYA4JUX...)

wilg 8 hours ago||
Presumably this is for ChatGPT Work? https://simonwillison.net/2026/Aug/30/understanding-chatgpt-...
quotemstr 10 hours ago||
There's no security benefit to doing this versus demand-downloading hashed-locked components on need.
TZubiri 9 hours ago|
Ok, it's probably not a security decision. It's a common pattern with both storage and memory management to push most reservations to initialization, in order to cluster resource insufficiency errors to a specific install-time when the user or admin can do something about it. An excessive just-in-time approach in both storage and memory would cause OOM and Disk exhaustion to occur at many different times.
dvrp 10 hours ago||
And wait till you find out about @oai/walnut
bcanzanella 10 hours ago|
do tell!
djriley 9 hours ago||
Walnut is the .NET and OpenXML backend. I think the point parent was trying to make it that it shouldn't be surprising Codex bundles runtimes for damn near everything.
m3kw9 9 hours ago||
probably uses it extensively to convert between LLM working on a doc and exporting it out to excel, word etc
chemael 5 hours ago||
[flagged]
luciana1u 4 hours ago|
[dead]
More comments...