Keep the book in view Manuscript, guide, plan, memory
Draft beside the structure of the story instead of bouncing between a blank page, a notes app, and a disconnected chat.
WolfeWriter. Fiction writing workspace for Mac.
The book stays in your hands.
Write, plan, remember, and review AI help in one native macOS workspace. WolfeWriter keeps the manuscript central, stores book state locally, and treats generated changes as proposals until you accept them.
One place for draft, memory, and approval.
The manuscript is the work surface, Story Memory is nearby, and AI output waits at the edge until reviewed.
Ask from the current scene Selection-aware writing help
Use the passage, chapter state, Story Memory, and Book Guide as context for rewrite, critique, and continuity work.
Approve the change Suggest, inspect, accept, reject
Generated manuscript changes stay reviewable until you decide what becomes part of the book.
Native editor path
AppKit/TextKit editing keeps selection, IME composition, and long-form manuscript behavior close to macOS.
Local book library
Books, chapters, manuscript text, plans, Story Memory, annotations, and indexes live on this Mac by default.
Proposal gates
AI drafting and rewriting stay reviewable. Generated manuscript changes are not canonical until accepted.
Built for authors who want assistance without surrendering the draft.
The page should be as direct as the product: not a chatbot, not a one-click generator, and not a cloud manuscript host.
WolfeWriter is for authors building a manuscript over time, with memory, planning, and review around the draft.
The writing surface is a Mac app with local books, local indexes, Keychain secrets, and a manuscript-first shell.
Story Memory and AI output support decisions, but manuscript and canon changes stay explicit.
Long projects need more than folders. WolfeWriter keeps book-specific state close to the scene you are writing.
Built around long-form fiction, not a chat box with a manuscript attached.
WolfeWriter treats manuscript text, local memory, annotation, and user approval as separate surfaces so the writer can get assistance without giving up control of the book.
Story Memory for characters, places, world rules, terminology, threads, timeline events, and canon facts.
Plan Board fields for outline, beats, characters, places, threads, POV, tone, status, and target word count.
Separate CJK and Latin/English local extraction paths because manuscripts do not all behave like English prose.
Apple Foundation Models-assisted local analysis where available, with external provider setup removed from the App Store build.
Local-first means ownership and explicit control.
WolfeWriter keeps books, manuscript text, Story Memory, Book Guide material, snapshots, and annotation state locally owned by the writer.
Boundary
No cloud manuscript dependency
Current Mac App Store build
Open, edit, import, export, and review local project state without a remote manuscript service.
Boundary
Bulk import stays local by default
Current Mac App Store build
Bulk import runs local annotation and candidate extraction; it does not send the whole book to a provider by default.
Boundary
Secrets stay in Keychain
Current Mac App Store build
API keys and OAuth credentials are stored in macOS Keychain.
Boundary
Current build limits are explicit
Current Mac App Store build
No EPUB, DOCX, PDF, Kindle export, collaboration, cloud sync, external API-key setup, or automatic canon confirmation yet.
Get WolfeWriter for macOS.
Start with a local book library, write in the native Mac editor, and keep Story Memory, planning, and reviewable suggestions tied to the manuscript you are building.
