Use Author with your AI

Author has no built-in AI. Your own AI, Claude, ChatGPT or Grok, works on your books through Geenius OS: it reads the outline, asks for a character's state before drafting a scene, writes scenes into your manuscript and runs the continuity checks afterwards.

Connect in three steps#

In Geenius OS, an owner or admin adds Author to the workspace (Apps, Add to this workspace). Each workspace keeps its own apps.
In your AI, add the Geenius OS connector and sign in with your Geenius OS account. In Claude: Settings, Connectors, Add custom connector. In ChatGPT or Grok: add a remote MCP server. Geenius OS shows you the address.
Ask your AI to use Author. It now has a tool called geenius_author.

How a call looks#

The tool takes a tool (the area), an action (the verb) and args.

A character's state at a scene

{ "tool": "story", "action": "state", "args": { "book_id": "<book>", "profile_id": "<character>", "scene_id": "<scene>" } }

Every call acts in the Author workspace of your Geenius OS workspace, after the plan check.

Your first ask#

A first ask

Use Geenius OS and my Author account. Open my book, read the outline and the state of the main character at the end of chapter 8, then draft scene 9.1 as Markdown with every event it implies, save a version first, and run the continuity checks afterwards. Tell me what they found.

The tools#

Tool	What it is for	Actions
`books`	Books, novellas and short stories	`list` `get` `create` `update` `delete`
`manuscript`	The manuscript tree	`tree` `add` `update` `move` `remove` `shift`
`scenes`	Scene text	`read` `write` `append` `patch`
`cast`	The cast	`list` `link` `unlink`
`strands`	Strands	`list` `add` `update` `reorder` `remove`
`events`	Events	`list` `add` `update` `move` `remove`
`story`	Story views and checks	`state` `state_diff` `timeline` `checks` `issues` `issue_dismiss` `outlines` `outline_apply`
`maps`	World maps	`list` `get` `create` `update` `delete` `pin` `unpin` `route` `unroute` `draw`
`versions`	Versions	`list` `get` `save` `diff` `restore` `delete`
`readers`	Beta readers	`share` `shares` `revoke` `comments` `reply` `resolve` `delete_comment`
`export`	Export	`run`
`profiles`	Profile snapshots from Geenius OS.	`sync` `list` `status`

Ask for the actions of an area with action: "help", and for one action's rules and arguments with action: "help" and of.

Habits that protect your book#

Save a version first. Before your AI rewrites prose a person wrote, versions save a named version. restore brings it back.
Read before you write. To replace text written in the app, read the scene and pass its revision as expect_rev, so a newer edit is never overwritten.
Facts live in profiles, story changes live here. Characters, places and weather are Geenius OS profiles or your own cast entries; what happens to them is an event in Author.
Readers' comments are yours. Ask your AI to summarise them; do not let it resolve them for you unless you say so.

What your AI cannot do#

It cannot make Author write: there is no model inside. A beta-reader link shows its address once, when it is made. And on Pro it cannot connect at all.