OfficeCLI for AI Agents: Automate Word, Excel, PowerPoint
iOfficeAI/OfficeCLI
Reach for OfficeCLI if you want an AI agent to build or edit Office files and actually check the result — its built-in renderer turns a .pptx or .docx into HTML or PNG so the agent can look at its own work and fix a title that overflows. Skip it if you only need to pull text out of documents, where a lighter converter like MarkItDown does the job, or if you need guaranteed pixel-perfect fidelity against desktop Office, since the rendering engine is written from scratch rather than being Microsoft's.
Agents That Edit Office Files Blind
Getting an AI agent to produce a real .docx or .pptx has been awkward. The usual route is 50 lines of python-pptx or openpyxl per document, and even then the agent works blind — it can manipulate the OOXML but can't tell whether a title overflows or two shapes overlap. OfficeCLI exists to collapse that into single commands and to give the agent a way to view the rendered page, closing the render-look-fix loop that document generation otherwise lacks.
One Binary, Full Read/Edit/Create Control
OfficeCLI for AI agents is an open-source (Apache-2.0) C# CLI tool giving an AI agent full read, edit, and create control over Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) files. It ships as a single self-contained binary with the .NET runtime embedded — nothing to install, no Microsoft Office needed. A built-in rendering engine turns a document into HTML or per-page PNG so a multimodal agent can see its own output and fix layout issues.
Render-Look-Fix: The HTML/PNG Feedback Loop
- ✓Single self-contained binary with the .NET runtime baked in — no Microsoft Office and no separate runtime to install
- ✓Built-in HTML rendering engine that outputs standalone HTML or per-page PNG, plus a `watch` mode with a live-refreshing preview at localhost:26315
- ✓Path-addressable editing: target any element like `/slide[1]/shape[1]` and read it back as structured JSON
- ✓Excel formula engine with 350+ functions evaluated on write, dynamic-array spilling, and native OOXML pivot tables
- ✓Word support for tables, styles, LaTeX equations, mermaid diagrams, tracked changes, and RTL/i18n
- ✓`merge` fills `{{key}}` placeholders from JSON, and `dump`/`batch` serialize a document to replayable JSON
- ✓One-line agent install via SKILL.md that wires the tool into Claude Code, Cursor, Windsurf, and Copilot
A Skill File for Claude Code, Cursor, and Copilot
Agent tooling is the current wave, and Office documents are a format nearly every knowledge worker still lives in. OfficeCLI leans into that with a one-line install aimed straight at agents (`curl -fsSL https://officecli.ai/SKILL.md`) that drops a skill file into Claude Code, Cursor, Windsurf, and Copilot. The README also markets it as "the world's first and the best Office suite designed for AI agents" — that's a marketing claim, not a verified fact — but roughly 15k GitHub stars show the idea is landing.
Installing the OfficeCLI Binary
OfficeCLI ships as a single self-contained binary. Install with the one-liner `curl -fsSL https://raw.githubusercontent.com/iOfficeAI/OfficeCLI/main/install.sh | bash` on macOS/Linux, or `irm https://raw.githubusercontent.com/iOfficeAI/OfficeCLI/main/install.ps1 | iex` on Windows PowerShell. Package managers also work: `brew install officecli`, `scoop install officecli`, or `npm install -g @officecli/officecli`. Prebuilt binaries for macOS, Linux, and Windows on x64 and ARM64 are on GitHub Releases. Verify with `officecli --version`.
Building a Deck From the Command Line
Create and edit from the command line. `officecli create deck.pptx` makes a blank file; `officecli add deck.pptx / --type slide --prop title="Q4 Report"` adds content; `officecli view deck.pptx html` (or `screenshot`) renders it; `officecli get deck.pptx '/slide[1]/shape[1]' --json` reads an element back. `officecli watch deck.pptx` opens a live preview that refreshes on every edit. For AI agents, running `curl -fsSL https://officecli.ai/SKILL.md` in the agent chat installs the skill so the agent learns the commands itself.
From Report Automation to CI/CD Pipelines
- •Having an AI agent generate a full PowerPoint deck from a prompt and check its own layout via the PNG render
- •Automating report generation from a database or API into templated .docx and .xlsx files
- •Batch document work in CI/CD or Docker — no display and no Office install needed
- •Extracting structured data from an existing document to JSON for downstream processing
- •Filling one designed template N times with `merge` for deterministic, consistent output
Why Teams Pick OfficeCLI
- ✓No Microsoft Office or .NET install — one binary runs headless in CI, Docker, or a display-less server
- ✓The render-to-PNG step gives multimodal agents a real feedback loop instead of guessing from XML
- ✓Replaces multi-library Python scripts (python-pptx + openpyxl + python-docx) with single commands
- ✓Broad format coverage: formulas, pivot tables, charts, LaTeX equations, mermaid diagrams, tracked changes, RTL
- ✓Works as a plain CLI too, so you're not locked into using it through an agent
Where the Rendering Engine Falls Short
- △Value is highest when paired with an AI agent; on its own it's a verbose path-selector CLI with a learning curve (`/slide[1]/shape[1]`, chained `--prop` flags)
- △The rendering engine is written from scratch, not Microsoft's, so output fidelity is only as good as that engine — don't assume pixel-identical results against desktop Office
- △Contributing to the source means C#/.NET, a smaller pool than the Python document-tooling ecosystem it competes with
- △The README's "first and best" / "world's first" framing is marketing, not independently verified — judge the tool on its actual output
- △Everything runs through one binary and its own OOXML implementation; unusual or niche Office features may not round-trip perfectly
OfficeCLI vs MarkItDown, python-pptx, and Pandoc
Who Actually Needs This
Developers building agent workflows that need to produce or edit real Office files — decks, reports, spreadsheets — and want the agent to verify its own output visually. It's a strong fit for headless CI document pipelines and for anyone tired of stitching together python-pptx and openpyxl. If you only need to extract text from documents, a lighter converter like MarkItDown is enough; if you need certified pixel-perfect fidelity with desktop Office, test the renderer against your own files first.
OfficeCLI FAQ
OfficeCLI is an open-source command-line tool that lets AI agents (or you) read, edit, and create Word, Excel, and PowerPoint files without installing Microsoft Office. It ships as a single self-contained binary and includes a rendering engine that outputs HTML or PNG so an agent can see the result of its edits.
No. The binary is self-contained with the .NET runtime embedded and implements its own OOXML read/write and rendering, so it runs on servers, in Docker, and in CI with no Office install and nothing else to set up.
Running `curl -fsSL https://officecli.ai/SKILL.md` in the agent's chat installs a skill file that teaches the agent the commands. The README says its installer also wires the skill into Claude Code, Cursor, Windsurf, and Copilot.
The README calls it "the world's first and the best Office suite designed for AI agents," but that's a marketing claim, not a verified fact. Libraries like python-pptx and converters like MarkItDown have handled parts of this for years; OfficeCLI's distinct angle is unifying read/edit/create plus rendering behind one CLI.
It's written in C# and Apache-2.0 licensed, with prebuilt binaries for macOS, Linux, and Windows on both x64 and ARM64.
Related repositories
Is OfficeCLI worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of OfficeCLI.