Changelog
What shipped, newest first.
- Try the demoOne click, no account: a demo studio with Broken Tide, The Ashbell Pass and Sherlock Holmes. Most of their canon is in place as labelled sample canon, the conflicts are found, a rule change waits with its impact, and a short review queue is left to try.
- A fuller guided tourReview, a conflict and a change’s impact first; then, if you want, the wiki, the timeline, Ask, the reader, export and agents. Progress, Back, Skip and Esc on every step.
- RoadmapA public roadmap: what shipped recently, what comes next and later.
- Upload new versionSend any file as the next version of a document from its page, whatever its name.
- Revert and whitespaceUploading an earlier draft again makes it the newest version; a save that only changes line endings or trailing spaces is not a new version.
- Archive documentsRetired documents leave the Library, reading order and book exports; their history and the canon citing them stay. Unarchive any time.
- More formats as textFountain, Yarn, Ink, CSV, TSV and JSON import as sources; a file without blank lines gets one passage per line. Up to 4 MB of text per file.
- Screenplay cuesScript vs recording reads screenplay cues (a name on its own line, V.O. and CONT’D) and names in any case when the project knows them.
- The medium, asked up frontA new project asks whether it is prose, screen or a game, with nothing preselected.
- Natural orderEpisode 2 comes before Episode 10 in folders, tags, entity lists and exports.
- Impact across every kind of documentA proposed change lists every document citing what it touches, grouped by kind: scenes, lore, quests, episodes, recordings. Exports and tasks follow.
- Acts after deathA new hard conflict: a character does something at a story time after canon says they died. Burials, mourning and memories don’t count.
- Review by document or folderNarrow the Review queue to one document or one Library folder; the document page and Library link to it.
- Open conflicts in exportsThe story bible lists conflicts still open, marked as not canon, unless you leave them out.
- Entity type in Add factPick whether a name is a character, place, item or another type when adding a fact by hand.
- Big wiki pages for agentsMCP reads a large entity page in parts, and the context pack says when it was shortened.
- Whole books split into chaptersUpload a manuscript as one file: it becomes one document per chapter, in reading order, in a folder named after the book. Uploading it again versions only the chapters that changed.
- Reading in the backgroundUploads answer at once while the AI reads them, with live status in the Library, on the document and in Review.
- Story or referenceThe AI says whether a document is story or reference notes as it reads it; labels say Chapter or Scene by medium.
- Reading-order timelineNovels without story times get a timeline too: each fact in the chapter that tells it.
- The Oz books and AliceTwo more public-domain samples, bringing the total to six.
- Canon decisions are human-onlyAgents read canon, check facts and propose; a person decides in CanonTracker. Accepting, rejecting, changes, conflicts, citation re-checks and merges are no longer offered over MCP and are refused for every token. Full access now means editorial edits as you. 37 tools.
- Renamed to CanonTrackerA graphite and signal-orange palette and a canon-track mark. The product was then called Story Bible in earlier releases.
- Same detail, two answersA new conflict rule: one character, two different answers for a detail that can only have one (Watson’s wound: shoulder or leg). Deterministic, with both quotes.
- Sherlock Holmes sampleSeven public-domain works, 31 documents and 127,000 words, with the famous continuity slips as a gold set.
- Agent setupReady-made MCP setup examples for coding agents, in Settings and on this site.
- This websiteFeature, use-case, agents, security, pricing and changelog pages; art and icons in the writer palette; a light and dark switch.
- MCP parityAgents can do almost everything people do in a project through MCP (team changes, sample loads, audio uploads and downloads stay in the app): 38 tools. Tokens are propose-only or full access (acts as you), and decisions made by an agent show “via agent”.
- Open sourceCanonTracker is licensed under AGPL-3.0.
- Plain AI labelsThe product says “AI” everywhere; which model ran is on Agent activity and Metrics.
- Continuity checkCheck a draft or a passage against canon; every finding quotes your text and cites real canon. New Agent activity page lists every AI run.
- AI criticA confirmed second opinion on each candidate in Review: keep, reject or needs edit, with a reason.
- Word import.docx files with tracked changes, footnotes and tables; Word comments become notes.
- VoiceRecordings become timed sources, script vs recording checks, and dictation in the editor and Ask.
- ResearchReal-world questions answered with checked web sources and calculators; notes never become canon on their own.
- Team conversations in AskShared conversations with a canon or research switch, follow-up questions and a chat drawer on every page.
- A writer’s paletteLinen, paper and walnut ink in light; warm wood in dark.
- The Ashbell PassA third sample: a 28-document game story with planted contradictions.
- For any story worldCanonTracker now speaks to novelists, game, screen and series writers, and worldbuilders.
- MCP and APIMCP grows to 16 grounded read and propose tools with paging and limits; every API route answers bad input with 400.
- Canon pageA paged, filterable list and a readable relationship graph.
- Version re-checkA new version flags only the canon facts whose quote is gone or repeated.
- Quote matchingQuotes match across smart quotes, dashes, Markdown and line breaks; the stored quote keeps the source’s characters.
- Story timeDays before day 1 and day-only times.
- BooksThe story bible and the manuscript as print PDF and EPUB.
- Entity typesEach project defines its own; game projects start with NPC, item, ability and quest.
- Editing and tagsEdit written and imported text documents as a new version (recording transcripts are kept as heard); tags on documents and Library rows.
- Add a factSentence first, with who, where and when filled in from the text.
- Propose a changeA guided flow, with impact grouped by hop.
- Project pagesA searchable project list and a page per project.
- Conflict severityHard and soft conflicts.
- Export and shareStory bible export as Markdown, zip and PDF; read-only share links.
- Re-review tasksScenes an applied change touches become tasks.
- ImagesUploaded and generated image history, document covers.
- Command paletteCtrl/Cmd+K search across canon, entities, documents and notes.
- SettingsProfile and password change.
- BrandLogo, app icons, illustrations and social images.
- Duplicate candidatesDuplicates are caught by identity and precision across every status.
- First versionImport, AI candidates with quotes, human review, canon, conflict rules and change impact.
- Accounts and studiosSign-up, studios, members with roles, invites and projects.
- Live AIAI features call the model provider live, with every call recorded.
- Entity wikiPages, portraits, merges and mention cards.
- MCP serverAgent tokens, read tools and proposals that wait in Review.
- Write in the appDocuments, focus mode, facts and notes from selected text.
- LibraryUploads, folders, tags, reader search, version history and diff.
- First loginGetting started checklist, guided tour, the Lantern Row sample and a phone nav.
- Image generationPortraits and covers drawn by AI.
- Early workThe idea and the product spec: a human gate, verbatim citations, narrow conflict rules and change impact within two hops. Then the first version: import with hashes and versions, AI candidates with verbatim quotes, review and canon.
Full history: commits on GitHub. What comes next: the roadmap.