web serial fiction

Write a web serial without losing the thread at chapter 200

Serial fiction breaks the tools built for one-off manuscripts. You are publishing while you draft, you cannot retcon freely, and by chapter 200 nobody — including you — remembers what colour a side character's eyes were in chapter 12.

Continuity across hundreds of chapters

The codex holds every character, place and item, and the AI reads the entries your scene actually mentions — not a summary you had to write by hand. Mentions are re-scanned on every save, so the link stays true as the draft moves.

Planning that survives contact with readers

Rolling story planning keeps a compass (where this book is heading) separate from the next arc's chapter plan. When reader response pushes the story sideways, you rewrite the arc, not the whole outline.

A daily word count you can actually hit

Scene beats let you leave a one-line instruction for tomorrow's session. The generation starts from that beat plus the codex context, so the blank page is never actually blank.

Frequently asked

Can it handle a book with 300+ chapters?
Yes. Chapters live inside books, books inside a project, and the AI context is assembled per scene rather than from the whole manuscript — so length does not degrade generation quality or cost.
Will the AI keep a character consistent?
It reads the codex entries mentioned in the scene, including progressive state notes anchored to a specific scene — so a character who lost an arm in chapter 40 still has one arm in chapter 120.
Can I export everything?
Yes, at any time, including after a trial ends. Export is deliberately never gated.

We use analytics cookies to see which pages help writers find us.

Never your manuscript — pages inside the writing workspace are not tracked. Privacy policy