AI has zero need to see the renders (you are just wasting tokens) and that is why I built the Go version - I patched a lot of the PPTX code in my MCP server, as it happens.
I have had a lot of experience creating and editing PowerPoint slides with Claude recently. It always converts the file to a PDF using LibreOffice and then renders the PDF into images to see if everything went right and that no text has overflowed.
while i appreciate that you are working on something to give away for free, providing your own little world of value... your comment makes it sound like you've never made powerpoints before. of course, there are a bajillion powerpoints out there in the wild that layer white rectangles to erase stuff from screenshots of charts, among numerous other atrocities
And if you task Claude with making a moderately sized powerpoint matching existing style guides, it will spend at most 30% of the time on the initial version. The remaining time is spent rendering out slides, looking at them and adjusting them
Of course AI can one-shot slides, but if you want good results where everything is aligned and has proper contrast you need a visual feedback loop
But bounding boxes don't always match what you want to do visually. Often you need to align to the baseline of text instead of its bounding box. And often you need to compensate for visual weight, making things different sizes so they appear more similarly sized to the eye
I'm not saying a pure API view won't work, but it will be a quality compromise compared to also having visual inspection
I have had a lot of experience creating and editing PowerPoint slides with Claude recently. It always converts the file to a PDF using LibreOffice and then renders the PDF into images to see if everything went right and that no text has overflowed.