Scribeist

Writing tools almost always assume writing is one thing. You get an editor, a chat panel, and a set of features that serve a blog post and a novel identically — which means they serve neither properly.

The needs are genuinely different. A novelist needs to remember that a character's sister was introduced in chapter three with brown eyes. A blogger needs headers, meta descriptions and internal links. Neither cares about the other's problem.

Scribeist builds separate workspaces for each, which is a more honest structure. It also does something rarer: it lets you point it at whatever model you choose, including one running on your own machine.

Scribeist: Three Workspaces, One Editor

• Different tools per project type — novels get Mythos and Timelines, blogs get SEO formatting and a site board, notes get a second-brain space.
• Mythos tracks entities: characters, places and lore linked directly to the prose that mentions them.
• Bring your own model, including local ones — OpenAI, Anthropic, Google, xAI, Mistral, OpenRouter, LM Studio and Ollama.
• Voice Capture takes writing samples so generated text matches how you actually write.
• Publishes and exports widely: WordPress, Ghost, HubSpot, Dev.to, Hashnode, Beehiiv, Micro.blog, plus PDF, DOCX, Markdown and EPUB.

Why Should A Novel And A Blog Post Use Different Tools?

Scribeist provides purpose-built tools per writing type rather than one editor with a chat panel attached, and the case for that is strongest at the extremes.

Long fiction has a continuity problem no other writing has. Across ninety thousand words, a writer must keep hundreds of facts consistent — who knows what, when, in which order, and with what eye colour — and the failure mode is not bad prose but a reader noticing chapter twenty contradicts chapter four.

Blogging has an entirely different problem: structure that machines read. Headers in the right hierarchy, a meta description, internal links to related posts, and a topic that fits into a wider site. None of that has anything to do with continuity.

A generic editor gives both writers the same blank page and the same assistant, which is why so many writing tools feel adequate and unhelpful. The specific work of each kind of writing goes unassisted.

The risk of specialising is the mirror image: a tool doing three jobs competes with dedicated products at each. A novelist comparing this against fiction-specific software and a blogger comparing it against SEO-specific software will both find something deeper elsewhere — which makes the case strongest for people who genuinely do both.

Compare that with a tool that picked one job. Jasper AI is built for marketing copy and brand voice, and is judged on that alone.

A novelist needs to remember what a character's sister looked like in chapter three. A blogger needs internal links. A generic editor helps with neither.

Mythos Is The Feature Novelists Actually Need

Mythos links characters, places and lore to the prose that mentions them, and it is the most valuable thing in the product for anyone writing long fiction.

The reason is that continuity errors in a manuscript are found by readers rather than by writers. You wrote it, so you remember what you meant, and your memory papers over the contradiction every time you re-read the passage.

The traditional solution is a series bible — a separate document listing every character, place and rule — and the traditional problem is that it drifts. The manuscript changes, the bible does not get updated, and by draft three it describes a version of the story that no longer exists.

Linking entities directly to the prose closes that gap structurally rather than through discipline. The record of who a character is lives attached to where they appear, which means it updates as a by-product of writing rather than as a separate chore.

Timelines complement it by mapping character arcs, pacing and chapter lengths visually. Pacing problems are notoriously invisible from inside a draft, and a chart showing that three consecutive chapters are twice the length of everything around them tells you something re-reading will not.

Bring Your Own Model Is A Real Choice

Scribeist supports OpenAI, Anthropic, Google, xAI, Mistral, OpenRouter, LM Studio and Ollama — which is an unusually long list, and the last two are the significant entries.

LM Studio and Ollama run models locally on your own machine. That means the text never leaves your computer, which matters enormously for a specific group of writers and not at all for everyone else.

Consider who is in that group. Anyone under a non-disclosure agreement. Anyone writing about a real organisation. A novelist who simply does not want an unpublished manuscript sitting on a third party's servers under terms that could change. Those are ordinary positions, and most writing tools cannot accommodate any of them.

The commercial models on the list matter differently. They let you match the model to the task — one for structural feedback, another for line editing — and they insulate you from a single vendor's pricing and deprecation decisions.

The honest trade with local models is capability. A model that runs on a laptop is meaningfully weaker than a frontier model, and for creative feedback that gap is noticeable. Bringing your own model is a choice about privacy and control, and it costs something.

Model choice is becoming a differentiator across the category — a workspace like Cleve makes the same argument — but local model support is still rare.

• Use a local model through Ollama or LM Studio for anything you cannot put on a server.
• Feed Voice Capture real samples of your own writing, not your best writing.
• Keep Mythos entities updated as you write rather than in a separate pass.
• Check the timeline view when pacing feels wrong but you cannot say why.
• Export at milestones in DOCX or Markdown, since a manuscript should never live in one place.

Voice Capture And The Sound Of Generated Prose

Voice Capture takes writing samples so the AI output matches your style, and this addresses the single most common complaint about AI-assisted writing.

Generated prose has a characteristic sound: balanced, fluent, slightly over-explained, and utterly unlike any specific person. Readers who cannot name it can still detect it, and for a novelist that quality is fatal because voice is most of what they are selling.

Providing samples is the right mechanism, and the result should be judged sceptically. Style is not only vocabulary and sentence length — it is what you choose to describe, what you leave out, and where you place emphasis, and none of those are easily imitated from a sample.

The most useful application is probably not generating prose at all. Style matching makes an assistant better at line editing in your voice, suggesting a cut that sounds like you would have made it, and that is a lower bar than composition and a more useful one.

A practical note: feed it representative samples rather than your best paragraphs. A model matched to your most polished writing will produce something you cannot sustain, and the mismatch between assisted and unassisted passages is exactly what a reader notices.

None of this decides what to write. That question belongs to a strategy tool such as MarketMuse, which sits earlier in the process than any editor.

Setting Up A Manuscript Workspace

The setup decisions in a writing tool matter more than in most software, because a manuscript is a long relationship and switching mid-draft is painful.

Establish the exit before you establish the workflow.

1. Export a test document to DOCX and Markdown on day one, and confirm the formatting survives.
2. Choose your model deliberately: local through Ollama or LM Studio if confidentiality matters, commercial if capability does.
3. Set up Mythos entities for your main characters and places before writing rather than retrospectively.
4. Feed Voice Capture three representative pieces of your own writing, not your three best.
5. Write a chapter, then check the timeline view to see whether the pacing matches what you intended.
6. Export the whole project monthly, because no writing tool should be the only place a manuscript exists.