The working model
The document is the canvas
TextText does for writing what agentic design tools do for a canvas: the work stays visible while you and the agent act on the same source.
Open context, not hidden context
The context chip above the composer names the document, folder, or workspace the agent is working with. Open a document to make it the focus. Select text to give the agent a precise passage.
One document model, consistent rules
TextText Agent, the app UI, and hosted MCP agents share the workspace command surface. In the standalone Mac edition, the local Claude and Codex plugins use the bundled CLI adapter. Both paths use the same document model, permissions, validation, audit records, and conflict checks.
Changes remain legible
- The in-app assistant appears as a collaborator while it works.
- Writing happens in the document, not in a second copy.
- Rewrite and Summarize selection quick actions show the replacement before Apply and keep Undo beside the result. Freeform assistant turns may change the document directly.
- Local plugin edits appear in the document. Read the updated text, then correct it directly or ask for a smaller follow-up change.
Two ways to bring an agent
TextText Agent
The assistant lives inside the right sidebar. App Store and browser builds use a workspace OpenAI or Anthropic API key. The standalone Mac edition can also use an eligible local ChatGPT or Codex account. The API-key path handles tools without confirmation gates; the standalone native path can also ask before guarded comments, publishing, and access changes.
Your AI app
In the standalone Mac edition, Claude and Codex can use the local TextText plugin and bundled CLI. Remote MCP clients that accept bearer credentials can connect to the hosted TextText tool surface with a revocable workspace token. The conversation stays in that AI app while the document stays in TextText.
Accounts and billing stay honest
Consumer subscriptions and provider API accounts are different. TextText does not turn a ChatGPT or Claude subscription into API credits, and it never asks for a provider password. The setup page tells you which account supplies each connection.