StoryForge keeps all data on your machine. There is no server of its own and no user account.
| Location | Content |
|---|---|
{content_root} (default ~/projekte/book-projects) |
Books, chapters, characters, notes, covers, exports, ideas |
~/.storyforge/authors/ |
Author profiles, analysed works, sample texts |
~/.storyforge/genres/ |
Your own genres, created with /storyforge:genre-creator. Survives plugin updates. |
~/.storyforge/db/ |
SQLite databases with book rules, canon facts, character states, author discoveries, session and logged review feedback (fiction: comment, before/after and proposal text; memoir: never raw text, only a classification and one rule without names) |
~/.storyforge/snapshots/ |
Comparison and raw drafts of fiction chapters (plain files, no database) |
~/.storyforge/cache/state.json |
Cache, rebuilt when needed |
~/.storyforge/config.yaml |
Configuration |
The logged review feedback and the draft snapshots also stay local on your machine; the plugin code opens no network connection of its own for them either.
The plugin's runtime code (MCP server and hooks) opens no network connections itself. The skill export-engineer runs the export as shell commands with pandoc and ebook-convert. These programs run locally on your machine.
Data still leaves your machine through these routes, which belong to Claude Code:
researcher, genre-creator, world-builder and continuity-checker can use web search. Search queries contain whatever you ask them to look up and may include terms from your book.You need no accounts or API keys for third-party services. You generate cover images outside the plugin (for example with Midjourney or DALL-E). StoryForge only produces prompts for that and imports the finished image.
In memoir mode you create profiles of real people under people/. Each profile carries relationship, category, consent status and anonymization, optionally also the real name (real_name) when the person is anonymized in the text.
| Field | Values |
|---|---|
person_category |
public-figure, private-living-person, deceased, anonymized-or-composite |
consent_status |
confirmed-consent, pending, not-required, refused, not-asking |
anonymization |
none, partial, pseudonym, composite |
These files stay local in your book project. But like any other project content they are transmitted to Claude as soon as a skill reads them. Treat them accordingly if you entered the real name of a protected person.
The export does not release memoir books with consent_status: refused. memoir-ethics-checker additionally checks consent and defamation risk in the chapters. Neither replaces legal advice.
For memoir books, write_author_discovery and log_review_feedback also reject text that contains the name of a person from the book.
You delete an author profile with /storyforge:delete-author. The skill removes the profile directory along with the author's discoveries and logged review feedback from the database. You delete books in the file system. Remove the matching database file under ~/.storyforge/db/ as well.