developers

Bring the story into the tools you write in.

The Word and Google Docs add-ins connect a draft to the same CharacterOS workflow as the app. Both are in pilot. This page maps what they do; the developer guide covers the integration path.

Integration Map
Two add-ins on the same story runtime
Canon in view

CharacterOS

One cast and one canon, whichever tool you write in.

Word

Authoring add-in

Bootstrap, sync storyworld, chat, scene, story Q&A, continuity, audio-link, and dashboard flows.

The most complete add-in, in pilot.

Google Docs

Controlled rollout

OAuth validation, sync, ghostwrite, continuity, chat, story Q&A, events, dashboard, and audio-link routes.

A controlled pilot.

What the add-ins call.

Real route families, with state called out. Both add-ins ship under a controlled rollout, so the page labels them as a pilot rather than a finished platform.

pilot
route familiesbase: /api
  • POST/api/addons/word/*Word add-in flows, controlled rolloutpilot
  • POST/api/addons/google-docs/*Google Docs add-in, pilot rolloutpilot

Two add-ins, one story.

Each surface routes through the same character and canon system, so an integration inherits the story instead of forking it.

Word add-in

Work on the book inside Word

Canon-grounded character chat, Story Q&A, scene review, continuity checks and storyworld sync, beside your Word document. In pilot.

Google Docs

The same workflow from a Google Docs sidebar

Sync, canon chat, Story Q&A and continuity checks through Google sign-in. A controlled pilot.

Pick the surface that fits the build.

This page keeps the map short. Start here, then read the developer guide.

Developer guide
start here

Start with the guide.

The developer guide walks the integration path for both add-ins.