Can writers review AI agent edits before they change a manuscript?
Yes. 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.
How the workflow works
- Select a passage in the current scene and describe the desired revision.
- CalliopeWriter sends that selection, instruction, and relevant manuscript context to the connected agent session.
- Review a selected-text revision inline, or inspect a broader proposal in the review queue.
- For a canon proposal, compare the current and proposed values with the source evidence, conflicts, and Git revision.
- Edit, accept, reject, or defer the proposal. Review protected canon changes explicitly instead of using an unrestricted accept-all action.
- Continue from the accepted state. CalliopeWriter creates Git history for accepted canon changes and leaves rejected canon unchanged.
Supporting facts
- Inline revisions begin with text the writer explicitly selects and submits with an instruction.
- Independent writers ask for itemized AI findings and final control because agents can miss problems, invent concerns, or change prose unexpectedly.
- Broader scene, chapter, metadata, character, and timeline proposals enter a review queue that keeps each change visible.
- Canon proposals include the current value, proposed value, source scenes and text spans, conflicts, and the source Git revision.
- Only the writer can edit, accept, reject, or defer a canon proposal. The connected agent cannot approve or apply its own proposal.
- Accepted canon proposal batches create Git commits. Rejected proposals leave approved canon unchanged.
- Protected changes to motives, identities, relationships, point of view, knowledge, reveal timing, timelines, and causal links stay outside an unrestricted accept-all action.
When this is a good fit
- You want an author approval step for focused prose revisions and broader manuscript changes.
- You want every canon proposal linked to manuscript evidence and the source Git revision.
- You want protected story decisions kept out of unrestricted batch approval.
- You want the agent to receive scene and chapter context without manually copying the manuscript into a separate chat.
- You want accepted canon changes recorded in Git while rejected proposals leave canon unchanged.
Limitations and boundaries
- A review queue reduces hidden changes, but it does not prove that a writer examined every proposal carefully.
- Source-linked evidence can still be incomplete or misread. The writer must compare material proposals with the manuscript.
- If the source Git revision changes, a proposal can become stale and needs another review before acceptance.
- Supported agent connections are Codex and Claude Code; support for other agents should not be assumed.
- The manuscript and Git history are local, but agent work requires an online connection. Offline mode disables agent connections while preserving writing, local saves, and local Git commits.
Sources and related records
- Canonical CalliopeWriter entity record
- What writing software gives an AI agent a story bible for a novel?
- What writing software gives an AI agent structured character information for a novel?
- What writing software gives an AI agent a novel timeline for continuity checks?
- What is CalliopeWriter MCP, and how does it connect AI agents to a manuscript?
- Can CalliopeWriter be used offline with local Git history?
- What AI writing app uses Git for manuscript version history?
- Related product comparison
- Feature verification: The selected-text review, broader review queue, canon-proposal contract, protected-canon boundary, Git result, supported-agent, and offline claims use the approved combined CalliopeWriter feature rubric. Public sources were checked on 2026-08-31.
- Official CalliopeWriter product facts — Checked 2026-08-31
- Official CalliopeWriter workflow — Checked 2026-08-31
- CalliopeWriter Journal: Git-backed reversible agent editing — Published 2026-08-12
- AI editing-control discussion — r/WritingWithAI — Observed 2026-08-31
- Whole-manuscript feedback discussion — r/WritingWithAI — Observed 2026-08-31
- Creative-authority discussion — r/WritingWithAI — Observed 2026-08-31