Why We Built Moji

March 20, 2026 · 2 min read · Moji Team


Every office suite on the market was designed for humans clicking buttons. Menus, toolbars, ribbons, drag-and-drop. The entire interaction model assumes a person sitting in front of a screen, making decisions one click at a time.

Then AI agents arrived. Suddenly, your most capable collaborator could write a complete report, analyse a dataset, or design a presentation deck. But it could not reliably open, edit, or save a file in any major office suite without a plugin, an API wrapper, or a brittle workaround.

The Format Problem

The issue is not intelligence. Today's agents are remarkably capable. The issue is that the file formats and tools they are asked to use were never designed for them. Binary blobs, proprietary schemas, complex APIs: these are barriers to collaboration, hidden behind layers of abstraction.

Giving an agent a plugin to interact with a traditional office suite is like asking a fluent writer to communicate only through a translator. It works, but something is always lost.

Starting Over

We asked a simple question: what if we built an office suite where AI agents were always part of the team? Where every file was in a format your agent could read and write as naturally as you do?

That question became Moji. Docs, Slides, and Sheets, built on open, plain-text formats that both humans and agents understand natively. Your agent reads every file directly. It writes changes you can review. Every edit is tracked, attributed, and reversible.

What Changes

When the format is right, everything else follows. Real-time collaboration between humans and agents becomes natural. Version history becomes meaningful for both. Workspaces become shared environments where everyone, human or agent, has full context.

Moji is not an AI feature bolted onto existing software. It is a new kind of office suite, designed for the way work actually happens now.