An open-source, single-binary Office suite built for AI agents — it lets an agent read, edit, and automate Word, Excel, and PowerPoint files without any Office install.
Last verified · 2026-07-06 · by Moe Ameen
OfficeCLI is an open-source command-line Office suite built by iOfficeAI specifically so AI agents can read, edit, and automate Microsoft Office documents. It ships as a single self-contained binary — no Microsoft Office installation, no runtime dependencies — and gives an agent programmatic control over Word (.docx), Excel (.xlsx), and PowerPoint (.pptx). It is released under the Apache 2.0 license, is free, and is written in C#, with prebuilt binaries for macOS (Apple Silicon and Intel), Linux (x64/ARM64), and Windows (x64/ARM64).
The core loop it advertises is create, read, modify, and reorganize. An agent can build a document from scratch, read out its text and structure, change any element, and rearrange content. What makes it agent-friendly rather than just another Office library is a built-in HTML rendering engine that reproduces a document with high fidelity and can export pages to HTML or PNG — so the agent can actually "see" what it made and close the render → look → fix loop instead of editing blind. A watch command runs a local, hot-reloading browser preview that updates as the agent edits, so you can watch the work happen in real time.
Two design choices target agents directly. Every element has a stable, path-based address such as /slide[1]/shape[2], so an agent can navigate a file without understanding XML namespaces, and every command supports a --json flag with consistent schemas and structured error codes. On the spreadsheet side it evaluates 350+ built-in Excel functions (including VLOOKUP, INDEX/MATCH, and dynamic-array spills) on write, plus template merge that swaps {{key}} placeholders across paragraphs, tables, shapes, headers, and footers for batch document generation. It auto-detects installed AI tools — Claude Code, Cursor, Windsurf, GitHub Copilot — and installs a skill file, and it ships an MCP (Model Context Protocol) server.
The honest framing: OfficeCLI is a document-automation engine for agents, not a content-marketing or publishing tool. It produces and edits Office files — reports, decks, spreadsheets, letters — with high fidelity. It does not write your brand voice across a content week, it does not make social posts, captions, or short-form video, and it does not schedule or publish anything to your channels. Details like the exact function count and integration list move fast on an actively released open-source project, so treat specifics as a snapshot and check the repo for the current state.
OfficeCLI and Kompozy sit on opposite ends of the same pipe. OfficeCLI is where an agent builds the source document — the quarterly report, the sales deck, the research whitepaper, the data-filled spreadsheet — and it does that job with real fidelity and full programmatic control. What it never does is turn that document into content people actually see in a feed. That handoff is exactly where Kompozy takes over. Point Kompozy at the finished .docx or the deck's text, and the document becomes the raw material for a full content week: the whitepaper's key findings become a document-style Carousel Post and a set of Quote Graphics, the report's headline stats become an Infographic Photo and native Text Posts, and the whole thing gets rewritten into a Blog Article and an Email Newsletter — all held to one voice by your Persona Brief so a dense internal doc reads like your brand, not a PDF.
The distinction worth keeping straight: OfficeCLI is deterministic document tooling — same input, same file — and Kompozy is the generative-and-publishing layer that OfficeCLI has no notion of. Kompozy also makes the formats a document can never become on its own: Persona Shorts and HeyGen avatar video that narrate the report's takeaways with a face-locked recurring identity, Clipped Shorts, and Persona Frames. Then it does the part no Office tool touches — schedules and fans the whole package across nine social platforms plus blog and email from one queue, with Autopilot and a per-post review pipeline. Let your agent produce the authoritative document in OfficeCLI; let Kompozy turn that document into a week of on-brand posts and ship them everywhere.
OfficeCLI is an open-source, single-binary command-line Office suite from iOfficeAI, built so AI agents can read, edit, and automate Word, Excel, and PowerPoint files with no Microsoft Office installation required. It is Apache 2.0 licensed and free.
It auto-detects and installs a skill file for tools like Claude Code, Cursor, Windsurf, and GitHub Copilot, and ships an MCP (Model Context Protocol) server, so most agent environments can drive it. Every command also supports a --json flag with consistent schemas for programmatic use.
Yes. OfficeCLI is open-source under the Apache 2.0 license and free to use, distributed as a single self-contained binary for macOS, Linux, and Windows with no runtime dependencies.
No. OfficeCLI reads, edits, and renders Office documents — it has no brand-voice layer and does not generate social posts, captions, or video, and it publishes to nothing. A content engine like Kompozy turns a document into on-brand posts and publishes them across platforms.
Have your agent produce the document in OfficeCLI, then bring its content into Kompozy. Kompozy fans it into a carousel, quote graphics, text posts, a blog, and a newsletter in your voice via your Persona Brief, then schedules and publishes the set across nine platforms plus blog and email.