IdeaWell

Project ideas from Hacker News discussions.

The ChatGPT/Codex app bundles a full copy of LibreOffice

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Bloat and performance concerns
Many commenters criticize the size of the bundled LibreOffice headless runtime and its impact on disk usage, startup time, and overall system responsiveness.

  • “Bundling all of LibreOffice seems like a pretty huge dependency.” – pseudosavant
  • “libreoffice‑headless still shows as 429.7 MB.” – zamadatix
  • “I think it's overbloating my computer.” – winstonp
  • “2 gb is crazy town, these things could be around 100 mb.” – cpursley

2. Preference for lighter or native alternatives
Several users suggest that OpenAI could avoid the heavyweight dependency by using headless CLIs, native libraries (e.g., Apache POI, Pandoc, Rust), or relying on the user’s existing Office installation and its APIs/CLIs.

  • “Why not computer use or using the tools the user prefers instead? The primary office suites have APIs/CLIs now.” – verdverm
  • “That's where the CLIs come in for me, I'm not going to waste tokens on screenshots and input device manipulation.” – verdverm
  • “Apache POI” – simongg (mentioned as a lighter alternative for reading/writing Office files)
  • “I still don’t understand why with all their cash these companies dont redo their apps in Rust or native.” – cpursley
  • “I have a skill that instructs ChatGPT/Codex to verify the rendering using the Mac versions of Microsoft Office.” – telotortium

3. Licensing and distribution compliance
A notable thread discusses whether bundling LibreOffice respects its open‑source licenses (MPL/GPL), whether the binary is truly bundled or downloaded on demand, and the need to provide proper attribution.

  • “Curiously, I didn't find any reference in the Open source licences section of the codex app. Is this a MPL 2.0 violation?” – vb‑8448
  • “Despite the title, I'm not sure it's actually bundled. Some of the skills plugins will download it on the first run.” – zamadatix
  • “I finally did find the license in …” – zamadatix (showing the license file location)
  • “The license itself may be present in the cache folder.” – TZubiri
  • Discussion of needing to “provide attribution (in a way that doesn't bother the user)” to stay compliant.

🚀 Project Ideas

Generating project ideas…

OfficeLite: Rust/Wasm Headless Office Manipulation Library

Summary

  • A lightweight, cross‑platform library that lets AI agents read, write, convert, and render thumbnails of Word, Excel, and PowerPoint files without bundling a full LibreOffice installation.
  • Core value proposition: sub‑50 MB binary size, fast startup, and native performance via Rust compiled to Wasm or native code.

Details

Key Value
Target Audience Developers building AI‑agent tooling, IDE plugins, or desktop apps that need programmatic Office file handling
Core Feature Unified API for docx/xlsx/pptx parsing, conversion to PDF/PNG, and data extraction (tables, text, shapes)
Tech Stack Rust core, wasm‑bindgen for web bindings, optional native CLI wrapper; uses quick‑xml and zip crates for parsing
Difficulty Medium
Monetization Hobby

Notes

  • HN users complained about the 429 MB LibreOffice headless bundle slowing Codex (e.g., "bundling all of LibreOffice seems like a pretty huge dependency").
  • Provides a practical alternative that agents can call via CLI or Wasm, satisfying the desire for headless, token‑free automation expressed by commenters like verdverm and tyres.

DocAgent Hub: On‑Demand Document Processing SaaS

Summary

  • A micro‑service API that AI agents call to perform heavyweight Office operations (conversion, rendering, data extraction) on remote workers, eliminating the need to ship large binaries locally.
  • Core value proposition: pay‑per‑use scaling, zero local bloat, and guaranteed up‑to‑date compatibility with the latest Office formats.

Details

Key Value
Target Audience SaaS platforms, AI agent frameworks, and enterprise developers who want to offload Office processing from client devices
Core Feature REST/GraphQL endpoints for convert‑to‑PDF, extract‑table, render‑slide‑as‑png, and merge‑docs, backed by a pool of cached LibreOffice‑headless workers
Tech Stack Go or Rust API gateway, Docker‑containerized LibreOffice‑headless workers, Redis job queue, Kubernetes for autoscaling; optional Wasm edge workers for lightweight tasks
Difficulty High
Monetization Revenue-ready: usage‑based pricing (e.g., $0.001 per conversion)

Notes

  • Commenters noted the pain of large local dependencies and the desire for CLI‑based solutions ("Why not computer use or using the tools the user prefers instead?"). This service offers exactly that—remote CLI‑style processing without local install.
  • Enables discussion around secure, agent‑friendly APIs and could become a de‑facto standard for AI‑driven document workflows.

OfficeShim: Smart Local Office Runtime Detector

Summary

  • A thin launcher that first checks for a user‑installed Microsoft Office (via COM/CLI) or LibreOffice, then exposes a standardized headless CLI; if none are found, it downloads a minimal, version‑pinned portable runtime only once.
  • Core value proposition: eliminates duplicate bundling of large Office runtimes while guaranteeing agents have a reliable backend when needed.

Details

Key Value
Target Audience Desktop app developers, AI agent toolkits, and power users who frequently automate Office files but want to avoid bloat
Core Feature Auto‑detection layer + fallback to a ~30 MB portable LibreOffice‑headless shim, exposing commands like officeshim convert input.docx output.pdf
Tech Stack Rust or Go for detection logic, thin wrapper around existing Office CLIs; portable runtime built from upstream LibreOffice‑headless with UPX compression
Difficulty Low
Monetization Hobby

Notes

  • Several users highlighted the inefficiency of bundling LibreOffice per app ("If you have word you can instruct to use word via com or AppleScript") and wished to reuse existing installations.
  • OfficeShim directly addresses this frustration, likely earning appreciation from commenters like telotortium and verdverm who prefer leveraging user‑preferred tools.

Read Later