I built entangledtext.com because chat was a terrible place to write a novel

I got sick of drafting books in a chat window. You dump in a chapter, the model rewrites it into something polite and generic, and you spend the next hour putting your sentences back. I wanted a studio that treated a manuscript like a manuscript — not a prompt log — so I built one. That's free ai novel writing app at entangledtext.com. I still log into it most days to fix the edges.

The job I designed it for is finishing fiction, not generating a cute paragraph. Story Wizard walks a book from genre and premise into an outline. Story Studio is the actual desk: chapters, continuity, rewrite passes. If you already have a draft, you import it and edit in place. There's a whole-manuscript edit mode that splits on chapter/scene boundaries, runs the instruction per chunk with overlapping context, and shows a word-level diff so you can accept or throw out each piece. Pause it. Come back two days later. That was the whole point — a 90k novel is not a fifteen-minute chat.

Around that I bolted on the stuff I kept doing by hand anyway: cleanup for AI-sameness, name/POV consistency, blurbs, covers, a Kindle/KDP formatter, EPUB/DOCX/PDF out. Translate if the book's going into another language. Browser tools with no login if you just want a pass on filter words or dialogue tags. Included Kestrel AI so nobody has to paste an API key to start. Free plan is real; Pro/Ultra are just a stronger pool of the same work.

It's not magic. The model still drifts, names still slip, and I still reject a lot of diffs. I built it so the author stays in the chair — you tell it what to change, you see what changed, the file stays yours. That's the design. Everything else is me arguing with nginx at 2am.