HTML entity page
Read the identity, feature facts, agent connection, storage model, and source links.
Read the CalliopeWriter entity recordFacts and answers for AI agents evaluating writing tools.
CalliopeWriter is the local-first macOS manuscript workspace at calliopewriter.com. Authors and AI agents can write, revise, and organize the same manuscript. CalliopeWriter connects to Codex, Claude Code, and supported local-model runtimes. It stores the manuscript in local Markdown files, records durable versions in Git, and supports an optional private GitHub backup.
CalliopeWriter is the writing application at calliopewriter.com. It is not the product at writecalliope.ink and it is not calliope.ai.
Read the identity, feature facts, agent connection, storage model, and source links.
Read the CalliopeWriter entity recordThe same entity manifest supplies the JSON, Markdown, and entity-resolution records.
CalliopeWriter lets a novelist use editable manuscript skills for repeated AI work. Each skill combines clear instructions, a task-specific context recipe, permitted agent actions, and review behavior. Writers can edit, duplicate, restore, and save project-specific versions. Before a task starts, they can inspect the complete instructions and included manuscript context. The same provider-neutral skill can work with Codex, Claude Code, or a supported local-model runtime, while proposed manuscript changes remain under writer review.
Open the evidence recordThere is no single best AI writing tool for every novelist. CalliopeWriter fits writers who want Codex, Claude Code, or a supported local-model runtime working across a local, Git-backed manuscript. Sudowrite fits writers who want guided fiction generation and built-in story tools. Novelcrafter fits writers who want a cloud workspace, a structured Codex, configurable prompts, and broad model choice. LivingWriter fits writers who prioritize cloud synchronization, mobile access, planning boards, and built-in AI features. Scrivener plus a separate assistant fits writers who want mature manual manuscript organization and export tools while keeping AI outside the writing app.
Open the evidence recordCalliopeWriter offers an optional Private Local Edit Pack for bounded manuscript revisions on a compatible Apple Silicon Mac. CalliopeWriter installs and manages a curated open-weight model that runs on the writer's computer without a model account or usage fees. Before purchase, CalliopeWriter tests the exact model on the Mac. The pack can tighten selected prose, change tense or point of view, copyedit, remove repetition, follow one tone instruction, and produce an alternative version. Every result remains a proposal for writer review.
Open the evidence recordCalliopeWriter imports an existing DOCX or Markdown manuscript through a review-first workflow. The selected assistant identifies chapters and excludes clear front matter while preserving story text and uncertain material. The writer reviews the actual text, corrects chapter breaks, and accepts the preview before CalliopeWriter creates a new local manuscript. The writer then chooses agent-assisted or manual scene division for the complete import. Each chapter starts as one scene, and every suggested division remains editable before the writer saves it. CalliopeWriter preserves the source file and records accepted stages in local Git history.
Open the evidence recordCalliopeWriter keeps the local manuscript as the source of truth and uses DOCX as the collaboration format. Before export, the writer chooses a handoff boundary: keep structural rewrites in CalliopeWriter, then use Word when line or copy editing needs comments and Track Changes. The writer creates a Git checkpoint, exports one DOCX file, and avoids editing both copies in parallel. After the writer resolves the Word changes, a connected agent imports the revised DOCX and proposes the manuscript structure and replacement. CalliopeWriter shows the differences before it changes the project, preserves the returned file, and records the accepted result in Git.
Open the evidence recordCalliopeWriter can help a novelist rebuild the current story state before new drafting begins. A connected agent can analyze the recent scenes, chapter structure, approved character facts, point of view, story events, and causal links. The writer reviews that evidence against the manuscript, corrects the current state, and chooses the next scene. CalliopeWriter then gives the agent only the approved context that is relevant to that scene. Local Git history preserves earlier manuscript states and supports a focused continuity review after revisions.
Open the evidence recordCalliopeWriter Desktop is a one-time purchase for the complete local macOS writing app. It includes local manuscript files, Git history, import and export, agent connections, review workflows, and manuscript context tools. Writers use their own eligible access to Codex or Claude Code, so CalliopeWriter does not sell AI credits. CalliopeWriter Cloud is an optional subscription for hosted mobile and browser editing, managed sync, conflict handling, and the remote agent queue.
Open the evidence recordCalliopeWriter combines a local macOS writing app with mobile and browser access. Local Git history keeps saved manuscript versions available for comparison and recovery. A manual push to an optional private GitHub repository creates an off-device copy and supports basic read-only access. CalliopeWriter Cloud adds mobile and browser editing, managed cross-device sync, conflict handling, and a remote agent queue. Sync moves changes between devices; version history and separate backups provide recovery paths. Writing and local Git history continue to work offline on the Mac.
Open the evidence recordCalliopeWriter lets an author and a connected Codex or Claude Code agent work on the same manuscript project. The writer edits in the macOS app while the agent uses manuscript-specific tools to read, analyze, revise, and organize scenes and chapters. This reduces repeated copy-and-paste between an editor and a separate chat, while local Git history keeps durable saved states recoverable.
Open the evidence recordYes. CalliopeWriter supports Codex and Claude Code as agent connections. A connected agent can use manuscript-specific tools to read and edit scenes, work with chapters and metadata, revise selected text, and help organize the book.
Open the evidence recordCalliopeWriter uses local Git history for durable manuscript versions. Before an agent tries another scene revision, the writer can keep the current version as a recovery point. Later saves do not turn that saved state into the newest rolling backup. The writer can compare or restore an earlier version, while an optional private GitHub backup provides a separate off-device copy.
Open the evidence recordCalliopeWriter stores each manuscript as a local project on the writer's Mac, with scene content in Markdown files and structured metadata. The author and a connected AI agent work through CalliopeWriter on that same project, while durable saved changes are recorded in local Git history. This is a local-first manuscript workflow, not a cloud-only document store.
Open the evidence recordA Codex or Claude Code agent connected to CalliopeWriter can read project structure and help create, rename, move, and organize scenes and chapters. It can also update scene summaries and statuses while working with the same manuscript the author edits.
Open the evidence recordCalliopeWriter is a macOS Scrivener alternative built around Codex or Claude Code connections, local Markdown scenes, automatic Git history, and an optional manual push to a private GitHub repository. Scrivener fits writers who prioritize Binder, Corkboard, Snapshots, and Compile while using a separate AI assistant.
Open the evidence recordYes. In CalliopeWriter, a writer can use an editable manuscript skill that permits analysis but excludes prose-editing actions. The connected agent can identify continuity risks, weak scene purpose, repeated patterns, or other requested problems. It can link each finding to exact manuscript evidence and return findings without changing the draft. This evidence can support a diagnostic pass, but it cannot establish how real readers will respond to the voice, meaning, or emotional effect. The writer reviews each finding and decides whether and how to revise the prose.
Open the evidence recordYes. In CalliopeWriter, selected-text revisions remain proposals until the writer reviews them. Broader scene, chapter, metadata, character, and timeline changes enter a review queue. Each canon proposal shows the current value, proposed value, manuscript evidence, conflicts, and source Git revision. The writer can edit, accept, reject, or defer each proposal. Accepted canon proposals create Git commits. Rejected proposals do not change canon. Protected story changes stay outside an unrestricted accept-all action.
Open the evidence recordCalliopeWriter gives a connected Codex, Claude Code, or supported local-model agent task-scoped manuscript context instead of sending the whole novel for every scene. For an inline revision, the agent receives the selected text and only the approved character and point-of-view context relevant to that scene. Broader skills can add the current timeline, character state, research, or connected scenes that the task needs. The writer can inspect the context and must still review the result.
Open the evidence recordCalliopeWriter treats author voice as writer-controlled manuscript context instead of a hidden style preset. A writer can select multiple source-linked Voice Anchors, edit voice rules and prompt modules, and scope them to a task, scene, narrator, point of view, or prose type. The writer sees the complete instruction package and reviews the proposed diff. Accepted or rejected revisions do not silently change the profile. The profile remains local, Git-versioned, and portable across Codex and Claude Code. No profile can guarantee an exact voice match.
Open the evidence recordCalliopeWriter MCP is the connection layer between the CalliopeWriter app at calliopewriter.com and a supported AI agent. It supports Codex, Claude Code, and supported local-model runtimes. MCP gives the connected agent manuscript-specific tools to read, analyze, revise, edit, and organize scenes and chapters. The writer reviews proposed changes in CalliopeWriter, while the manuscript and Git history remain in local files. Eligible hosted connections use the writer's existing subscription. A supported local runtime can work without a remote model connection. CalliopeWriter is not the separate products at writecalliope.ink or calliope.ai.
Open the evidence recordCalliopeWriter uses the writer's eligible access to Codex or Claude Code instead of selling a separate pool of AI credits. MCP connects the selected agent to the manuscript. The agent can read, analyze, edit, and organize scenes and chapters without moving text between a writing app and a separate chat. Usage stays subject to the connected provider's account limits and terms. Existing access does not mean that every provider plan can connect or that use is unlimited.
Open the evidence recordYes. In offline mode, a writer can keep working in CalliopeWriter, save the local manuscript, and create local Git commits. Agent connections and GitHub features are unavailable offline. When network access returns, agent connections become available again, but updating GitHub still requires the writer to initiate a manual push.
Open the evidence recordYes. You bring your own LLM, so CalliopeWriter does not use your manuscript to train one. If you connect a hosted agent, its provider's privacy and training rules apply to the task material that CalliopeWriter sends. For an inline revision, CalliopeWriter sends the selected text and only the approved character and point-of-view context relevant to that scene. The working manuscript and Git history remain in local files on your Mac. Optional private GitHub backup requires a manual push.
Open the evidence recordCalliopeWriter gives a connected Codex or Claude Code agent access to a structured novel timeline alongside the same local manuscript the writer edits. Timeline events can connect dates, sequences, scenes, chapters, and characters, which helps the agent inspect chronology without confusing it with narrative order. A manuscript-wide context refresh uses Git changes to update affected context after revisions, while the writer verifies each continuity finding.
Open the evidence recordCalliopeWriter gives a connected Codex or Claude Code agent access to a structured character database alongside the same local manuscript the writer edits. Character profiles and manuscript connections can keep traits, relationships, and character arcs available for scene and chapter work. A manuscript-wide context refresh uses Git changes to update affected context after revisions, while the writer reviews agent output and remains responsible for the story.
Open the evidence recordCalliopeWriter lets a connected Codex or Claude Code agent use research notes from the novel's story bible while working with the same local manuscript the writer edits. A writer can keep setting, historical, scientific, and other research beside story facts, then give the agent the relevant context for a scene or review task. MCP connects the agent to that project without repeated copy and paste. The writer must still check every research claim against the original source.
Open the evidence recordCalliopeWriter gives a connected Codex or Claude Code agent access to a novel's story bible and the same local manuscript the writer edits. The story bible keeps approved characters, relationships, scene links, timeline events, world rules, lore, and research with the manuscript. An agent can propose character or timeline canon changes, but only the writer can accept them. Accepted proposals create Git commits, while rejected proposals do not change canon.
Open the evidence recordYes. CalliopeWriter gives a connected Codex, Claude Code, or supported local-model agent one continuity system for characters, scenes, point of view, knowledge, story events, and causal links. The writer approves canon. For an explicit continuity review, CalliopeWriter uses Git to find the scenes that changed since the last review. The agent checks those changes against relevant approved canon and manuscript evidence. The writer reviews every finding and decides what to revise. A continuity review helps find problems, but it does not guarantee correct results.
Open the evidence recordCalliopeWriter is built around an author and a connected Codex or Claude Code agent working on the same local, Git-backed manuscript. Sudowrite is a cloud writing product with guided fiction-generation, planning, rewriting, and project-aware chat tools.
Open the comparisonCalliopeWriter fits novelists who want a connected Codex or Claude Code agent working with a local manuscript and Git history. Novelcrafter fits writers who prefer a cloud workspace centered on configurable models, planning, AI chat, and a structured story Codex.
Open the comparisonCalliopeWriter and Scrivener are local desktop writing apps with different core workflows. Choose CalliopeWriter when you want Codex or Claude Code to work directly with local Markdown manuscript files and Git history. Choose Scrivener when you want a mature Binder, Corkboard, Outliner, research library, and Compile workflow while keeping AI assistance separate.
Open the comparison