English · Français
Oxeegen's AI office suite.
Word, Excel, PowerPoint and PDF files, edited by you and your AI, saved back in the real formats —
running on Oxeegen's own models.
Download · CLI · MCP · Oxeegen · Privacy
OxeeOffice is a desktop office suite for Windows and Linux. It opens and saves
native .docx, .xlsx and .pptx files, edits PDF, Markdown and HTML, and puts
an AI agent next to every document — not a chat box bolted on the side, but an
editor that reads the file, makes the change, and shows you exactly what it
touched.
- Real formats, byte-preserving. Only what you edit is rewritten. Everything else in the file survives byte-for-byte, so documents keep working in Word, Excel and PowerPoint.
- AI you can review. Edits land as tracked changes and diffs with one-click rollback. Spreadsheets get live formulas, not pasted numbers. Decks and pages are generated onto the canvas and stay fully editable.
- Local by design. Files open, edit, save and convert on your machine. PDF → Word / Excel / PowerPoint, Markdown → Word and HTML → Word all run on-device. Only the AI calls leave the machine, to the provider you choose.
- Oxeegen models by default. AI runs on Oxeegen's self-hosted, OpenAI-compatible inference. You can also bring your own key for Claude, OpenAI, Gemini, DeepSeek, Mistral, OpenRouter and others, or any OpenAI-compatible endpoint, local servers included.
- Scriptable and agent-ready. The app ships a command line and a skill for Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf, so a coding agent can create, convert, read and edit real Office files on your machine without opening a window.
- Updates itself. Installed apps check this repository's releases and offer each new version.
Get it: Windows (x64) · Linux (deb, rpm, AppImage) — details and requirements in Download.
Six editors, one AI panel, and a command line for your coding agent.
Say what the page is for and who it is for. The AI proposes a design brief
first — hook, palette, typography and style directions — then builds a single
self-contained .html file against those tokens.
OxeeOffice ships a command line and an agent skill. Install the skill and Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode or Windsurf can create, convert, read and edit real Office files through the same engines as the apps, without opening a window.
![]() |
![]() |
One prompt to your agent — "Build an eight-slide deck about the Solar System." The agent reads the skill, writes a style sheet, an outline and one page spec per slide, and lets slides check reject anything that overflows or overlaps before create assembles the .pptx and slides render hands back a PNG per slide to look at. |
Install once, from Settings → Integrations — OxeeOffice lists the coding agents it finds on this computer and writes the skill into each one you pick. Or download the skill as a zip, or run npx skills add Oxeegen/OxeeOffice. See Command line and agent skill. |
Every command is also an MCP tool. Claude Code, Claude Desktop, Cursor and any other MCP client can start the server themselves, with no skill to install and no window open. A second, HTTP server inside the app lets an agent build a Word document in a visible editor tab while you watch.
![]() |
![]() |
One prompt, no shell — "Build an eight-slide investor briefing about renewable energy in 2026, with a real photo on the cover." The agent pulls figures and photos with search, checks each picture with media, builds the deck page by page with every page checked against the outline and palette, then renders each slide as an image it can look at and fixes the pages it does not like. |
Connect once, from Settings → Integrations — copy the claude mcp add line for Claude Code, or the JSON block into Cursor, Claude Desktop or any other MCP client. See MCP server. |
- Runs on Oxeegen. AI on Oxeegen's own inference, with the region endpoint configurable per user — no third-party account or subscription.
- Yours to run. Native apps for Windows and Linux; files stay on your disk and every edit, save and conversion happens on your machine.
- Real Office files. Native
.docx,.xlsxand.pptx, byte-preserving: the parts of a file you did not touch are copied exactly as they were. - An AI that edits the document itself. Tracked changes in Docs, live formulas and charts in Sheets, slides drawn onto the canvas, every AI turn a snapshot you can roll back.
- PDF done properly. Edit text inside the page, and convert PDF to Word, Excel or PowerPoint on-device, with system OCR for scans.
- Markdown and HTML too, with the same AI panel and local export to Word.
- Scriptable. A command line, an agent skill and an MCP server put every engine at the service of your coding agents, still on-device.
- Open source, Apache-2.0, and free.
Oxeegen is the default provider: chat, image and video analysis run on Oxeegen's models (Max, Pro, Flash, Instant) through its OpenAI-compatible endpoint. In Settings → AI Model, pick your region (US or EU — each has its own keys) and paste your Oxeegen API key; the endpoint is filled in for you. Switch models any time from the picker at the top of each editor's AI panel: that model plans with reasoning on, then writes slides, checks slide layout and writes long documents with reasoning off. Keys are never bundled, because releases are public.
Under AI Media & Search, web and image search run on Brave Search — paste a
Brave API key into the Oxeegen search entry — and image generation uses OpenAI
(gpt-image-2.5-flare, medium quality) with your OpenAI key, until Oxeegen serves its
own image models.
Or bring your own key. Settings → AI Model also lists Claude, OpenAI, Gemini, DeepSeek, Kimi, GLM, Qwen, Doubao, MiniMax, Grok, Mistral, OpenRouter, Requesty and OpenCode Zen/Go, plus a custom slot for any OpenAI-compatible endpoint (base URL + key), including local model servers. Search and media have their own per-capability providers under AI Media & Search.
The whole suite ships light, dark and system themes. Themes only change what is on screen: exports, prints and saved files always keep the document's own colors.
Everything the apps can do to a file, the command line can do from a terminal: inspect, convert, create, read and edit Word, Excel, PowerPoint, PDF, Markdown and HTML on the same engines, headless. It installs with OxeeOffice, needs no runtime of its own, and never sends a document anywhere. Paired with the bundled agent skill, it turns a coding agent into a document worker that produces real Office files instead of Markdown approximations.
The command is still called
genofficein this release; it becomesoxeeofficein an upcoming one, together with the MCP server name and the skill. The examples below use the current name.
Works with: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf out of the box, any other agent that reads skills, and, through the MCP server, Claude Desktop and every MCP client.
| How | What happens |
|---|---|
| Settings → Integrations in the app | Lists the agents found on this computer; one click writes the skill into each one you choose. An Update button appears when a release ships a newer skill. |
| Download as zip on the same page | The layout claude.ai, the Claude desktop apps and other assistants accept as an uploaded skill. |
npx skills add Oxeegen/OxeeOffice |
Installs from this repository into any skills-compatible agent. |
Then start a new chat and ask for a document. The skill teaches the agent when to reach for the command line, how to read a file before editing it, and how to check its own work.
genoffice --version
genoffice info report.docx --json # headings and blocks; or sheets, slides, pages
genoffice convert report.md --to pdf # md/html/docx/xlsx/pptx → pdf, pdf → docx/xlsx/pptx, …
genoffice create --type docx --from notes.md --out notes.docx
genoffice create --type xlsx --from table.json --out sales.xlsx # "=SUM(B2:B9)" cells stay live formulas
genoffice docs read report.docx --range 0-9 --json # then `docs apply --ops edits.json` edits in place
genoffice render report.docx --out shots/ # one PNG per page, to look at what you made
genoffice open sales.xlsx # hand the result to the editorEvery command prints a one-line summary, or a single JSON object with --json.
Edits are atomic: a rejected op leaves the file untouched and comes back with a
guided error. genoffice help lists the current command surface; the full
reference is packages/cli/README.md.
An agent following the skill's staged workflow runs something like this, and the command line checks every stage before the next one starts:
genoffice capabilities --json # which cloud tools are configured
genoffice guide slides design # the deck workflow and layout library
genoffice slides check deck/outline.json --json # outline checked
genoffice slides check deck/pages/01.json --json # builds one slide, audits overflow and overlap
… # one page file per slide, fixed until each check is clean
genoffice create --type pptx --spec deck/pages --outline deck/outline.json --out deck/briefing.pptx --json
genoffice slides render deck/briefing.pptx --out deck/shots --json
genoffice slides audit deck/briefing.pptx --json
genoffice open deck/briefing.pptxNo model call happens inside the command line: the agent does the thinking, the
command line does the building and the checking, and the result opens in
OxeeOffice or PowerPoint as an ordinary .pptx.
The same commands are available as Model Context Protocol tools, for assistants that cannot run a terminal or that you would rather not give one. There are two ways in, both shown with copy-ready snippets in Settings → Integrations → MCP:
| Way | What it is |
|---|---|
A · genoffice mcp (recommended) |
A stdio server the assistant starts itself; OxeeOffice does not need to be open. One tool per command (info, convert, create_*, docs_*, sheet_*, slides_*, render, guide, search, image, media, open) plus the staged deck flow deck_start → deck_page → deck_build → deck_replace. |
| B · Local HTTP server | Runs inside the app on http://127.0.0.1:3093/mcp. Its tools drive a visible Word editor tab, so you watch the document take shape. Off by default; switch it on in the same settings pane. |
# Claude Code
claude mcp add --transport stdio genoffice -- genoffice mcpgenoffice here is the command line shipped inside the app — on Windows
%LOCALAPPDATA%\Programs\OxeeOffice\resources\cli\genoffice.cmd, on Linux
/usr/bin/genoffice; the settings pane prints the exact path for your install.
Cloud features (search, image, media) go through the provider configured in
OxeeOffice; everything else runs locally, and GENOFFICE_ALLOWED_ROOTS confines
every tool to the folders you list.
The Windows installer and the AppImage update themselves; deb and rpm installs update through the package manager. The installers are unsigned: on first run, Windows SmartScreen warns — choose More info → Run anyway. macOS is not built, because without an Apple Developer certificate Gatekeeper refuses the app.
What changed in each version is in CHANGELOG.md.
Installing on Linux
The deb installs with apt — it pulls in the dependencies and adds OxeeOffice to the applications menu:
sudo apt install ./oxeeoffice_<version>_amd64.debOn Fedora / RHEL-family / openSUSE, install the rpm instead:
sudo dnf install ./oxeeoffice-<version>.x86_64.rpm # Fedora / RHEL family
sudo zypper install ./oxeeoffice-<version>.x86_64.rpm # openSUSEThe AppImage runs in place: install the FUSE 2 runtime (sudo apt install libfuse2;
on Ubuntu 24.04 the package is libfuse2t64), make the file executable, then run it:
chmod +x OxeeOffice-<version>.AppImage
./OxeeOffice-<version>.AppImageSeven Electron apps — Docs, Sheets, Slides, PDF, Markdown, HTML and the tabbed
shell — share one engine layer of pure TypeScript packages plus a Rust sidecar
for .xlsx. The original file is always the source of truth: edits are applied
as narrow patches, and everything the editor did not touch survives the round
trip untouched.
open docx ─► archive original by hash (never touched)
─► parse word/document.xml into a block tree, each block anchored to its original XML
─► Tiptap editor (manual + AI editing, dirty tracking)
save ─► dirty blocks → OOXML fragments (referencing existing styles only)
─► splice into the original document.xml; untouched blocks keep their bytes
─► repack the zip; every other entry is copied byte-for-byte
npm install
npm test # engine + app unit tests
npm run typecheck # tsc --noEmit across every workspace
npm run dev # all six editors + shell against Vite dev servers
npm run dev:docs # a single app (same pattern works per workspace)The Sheets app needs a Rust toolchain for its xlsx sidecar (cargo on PATH).
Installers are built by the release workflow. Setup, checks, releases and pull
requests are in CONTRIBUTING.md.
- Report a bug or request a feature in GitHub Issues.
Is OxeeOffice free?
Yes. The apps are free and open source under the Apache-2.0 license. AI features use Oxeegen inference or the provider key you configure.
Can OxeeOffice open Microsoft Word, Excel and PowerPoint files?
Yes. OxeeOffice opens and saves native .docx, .xlsx and .pptx files. Saving is
byte-preserving: parts of the file you didn't touch are written back byte-for-byte,
so documents keep working in Microsoft Office.
Does OxeeOffice work offline?
Document editing is fully local — files never leave your machine to be opened, edited, saved or converted. The AI features need a network connection to Oxeegen or to the provider you configured.
Can OxeeOffice edit PDF files, or convert them to Word?
Yes to both: real PDF text and image editing that rewrites the page content stream with the original fonts, and PDF → Word / Excel / PowerPoint conversion entirely on-device, with system OCR for scanned pages.
Can I use a different AI model or my own API key?
Yes. Oxeegen is the default, and Settings also accepts keys for Claude, OpenAI, Gemini, DeepSeek and others, or any OpenAI-compatible endpoint, including local model servers.
Can I drive OxeeOffice from Claude Code, Codex, Cursor or a script?
Yes, through the bundled command line and agent skill, or the MCP server. See Command line and agent skill.
Does OxeeOffice collect any data?
No. OxeeOffice builds send no usage analytics: they are never given analytics credentials, and the release workflow fails if a package carries them. Documents stay on your machine; only the AI requests you make are sent, to the provider you configured. See PRIVACY.md.
See SECURITY.md for how to report a vulnerability, the process security posture (renderer sandboxing, IPC validation, external-link gating) and the threat models for AI-generated content.
OxeeOffice is open-source software under the Apache License 2.0. Attribution and third-party notices are in NOTICE.
The ee/ directory is covered by a separate license (ee/LICENSE) and
is not part of OxeeOffice builds.
Maintained by Oxeegen.






















