What this feature does
This tool lets you use your own Claude account to analyze chapters of your manuscript and automatically update either the Current Arc, the Storyline, or your Considering notes for every character, location, faction, or other entry in your Encyclopedia. You choose which field to target when you generate your prompt. The exchange with Claude happens in two steps — first Claude tells you who it found and flags anyone not yet in your Encyclopedia, then only after you confirm does it write the actual database code. You paste that final result back here to apply the updates. Nothing changes in your Encyclopedia until you review and confirm on this end too.
⚠️ Order matters — for both fields
Both the Storyline and the Current Arc are running logs. Each passage you submit is appended to the bottom of whichever field you chose — nothing gets sorted afterward. Whatever order you submit in is the order it will read in.
If you are backfilling finished books into the Storyline, you will get the most useful result by working through your finished books in publication order — book one first, then book two, and so on — and within each book, chapter by chapter in order. That way each entry's Storyline reads as a clean chronological history of that character or place across the whole series.
If you are tracking the book you are writing now, the same applies to the Current Arc — submit your chapters in order as you go.
Skipping around still works and nothing breaks, but the entries will not be in chronological order and will be confusing to read later. Use the bookmark below to track exactly where you stopped so you can pick up in the right place next session.
Set up your Encyclopedia entries ahead of time when you can
It's fastest if every character, location, faction, and other entry that appears in your manuscript already exists in your Encyclopedia with their full name as the title before you generate your prompt — that way Claude can match everyone right away in Step 1. If something is missing, you don't have to stop and go create it first: Claude will flag it under NOT YET IN ENCYCLOPEDIA using the exact wording from your text, and Step 1 will simply pause there. You can create the entry then, tell Claude its exact name, and continue to Step 2 from the same conversation.
How names and nicknames work — the two-step check
Your manuscript probably doesn't use full names every time — "Braedan" instead of "Braedan Meswick", "the King" instead of "King Evander", or a character referred to by their title rather than their name. The prompt is built so Claude does this in two steps instead of guessing everything in one pass.
Step 1: after you paste your chapter, Claude stops and gives you two lists — its name MAPPINGS (which nickname matched which Encyclopedia entry) and anything NOT YET IN ENCYCLOPEDIA (using the exact wording from your text). It will not write any SQL yet.
Step 2: review both lists. Fix any wrong mapping, and for anyone flagged as missing, go create their Encyclopedia entry now and tell Claude the exact entry name you gave them (or say to skip them). Only then reply telling Claude to proceed — that's when it writes the actual SQL. This mirrors the same back-and-forth check used to build this feature in the first place, so nobody quietly gets left out.
The "Considering" option — a third choice besides Current Arc and Storyline
When you generate your prompt, the field dropdown has a third option beyond Current Arc and Storyline: Considering — future ideas, brainstorming. Use this when you want to hand Claude a big pile of loose ideas — a planning document, a brain dump, notes you jotted down about where a character or plotline might go — rather than an actual passage of finished manuscript.
Unlike Current Arc and Storyline, this mode does not ask Claude to describe what happened — it asks Claude to capture what you're thinking about, phrased as a possibility rather than a fact ("Could reveal...", "Might become..." instead of "Does..." or "Becomes..."). It also skips the book-header step entirely, since brainstorming isn't tied to any one book's canon.
This is the option to reach for if you want to submit one large batch covering many entries at once — for example, a big planning session where you're mapping out ideas for several characters across a whole series. The Considering field never exports and is never moved into the Storyline automatically, so nothing here becomes canon until you decide to write it and update the entry yourself.
The copy button in Claude
The prompt tells Claude to put its SQL output inside a code block, which is what makes Claude's own copy button appear on it in your conversation — use that button to grab everything in one click instead of selecting text by hand.
How much to submit at once, and what happens with very long output
You can submit a full chapter, half a chapter, or just a scene — whatever fits in your Claude conversation. Shorter passages give Claude more focused, accurate output. If a chapter is long, split it into two submissions and use the bookmark to note where you stopped.
There's no fixed length limit, but a single response covering many entries in one long chapter can occasionally get cut off mid-way. The prompt instructs Claude to always close its code block cleanly and, if it runs out of room, to stop only at the end of a complete UPDATE statement rather than mid-line. If you see Claude's response end abruptly, just ask it to continue — it will pick up with a new code block for the rest. It's fine to submit multiple code blocks together; you can paste them all into the box below in one go and everything will still be read correctly.
What to do if Claude's output looks wrong
Do not paste output you aren't confident in. If Claude missed an entry, invented something, or mapped a name incorrectly — regenerate with a correction in your Claude conversation, or submit only the entries you're happy with by removing the incorrect UPDATE statements before pasting. You can also edit any entry's Current Arc or Storyline directly inside the Encyclopedia at any time, without using this tool.
Rollback
Every confirmed submission saves a snapshot of the affected entries before anything changes. The last 5 snapshots are kept, shown at the bottom of this page. If you realize you submitted something out of order or made a mistake, use the rollback to restore those entries to their previous state. Rolling back removes that snapshot and any newer ones — so roll back to the earliest point you need to fix, then resubmit in the correct order.