Scrivener and AI:
How to Use AI with Your Novel

Scrivener has been the go-to novel writing app for years. The binder, the corkboard, the compiler, the research folder. If you've written a book in the last decade, you've probably used it or thought about it. It costs $49 one-time (no subscription), and it does what it does very well.

But Scrivener has no AI integration. No Claude panel. No ChatGPT connection. No way to ask an AI about your characters, your plot, or your prose from inside the app. As of 2026, there's no sign that's changing. (If you've seen AI-related prompts in Scrivener on a Mac, those come from Apple Intelligence in macOS 15+, not from Scrivener itself. Literature & Latte has confirmed they have no plans for built-in AI.)

If you want to use AI with your novel writing, you have a few options.

Option 1: Copy and paste

The most common approach. Keep writing in Scrivener. Open Claude or ChatGPT in a browser. Copy a scene, paste it into the chat, ask for feedback, copy the results back.

It works, but it's slow. The AI can only see what you paste in. It doesn't know your characters, your plot structure, your voice rules, or what happened in the previous chapter. Every session starts from scratch. You spend as much time setting up context as you do getting useful output.

Option 2: Use Scrivener for writing, a separate AI tool for everything else

Some writers use Scrivener for the manuscript and a tool like Sudowrite or NovelCrafter for the AI side. This gives you dedicated AI features, but now you're managing your novel across two apps. Characters in one place, manuscript in another. And you're paying for both.

Option 3: Move to a setup where the AI can see your files

This is what I did. I loved Scrivener's approach to organising a novel, but I needed the AI to actually read my work. Not pasted snippets. The whole thing.

The key insight: Scrivener uses a proprietary file format. AI tools can't read .scrivx files. But if your novel is plain text files in folders, any AI that can read local files has access to everything. Your characters, your plot, your manuscript, your world-building. All of it, all the time.

What changes and what stays

Honest assessment. Most of what Scrivener does has an equivalent in Obsidian. A few things work differently:

• The compiler. Scrivener's compile feature is powerful and flexible. Obsidian's Longform plugin compiles your manuscript to a single file, which handles most needs. If you need complex formatting for print and ebook output, you may still want a dedicated tool for final compilation.
• The corkboard. Obsidian has Kanban boards which serve a similar purpose. They feel different. Some writers prefer one, some the other.
• Snapshots. Scrivener has built-in document snapshots. In this setup, git handles version history and does more, since it tracks your entire project, not just individual documents.
• Rich text editing. Scrivener lets you write in rich text. Obsidian uses markdown, which many writers find freeing. It's a genuine preference.

What you gain:

• AI that knows your book. Not pasted snippets. Your whole manuscript, characters, plot, and voice rules. Available every session without re-explaining anything.
• Plain text files. No proprietary format. Your files work in any text editor, forever. No company can shut down and take your work with them.
• 19 shortcut commands. Workshop, draft, edit, stress-test, check continuity. Designed for Claude, usable with any AI that reads local files.
• A writing history. Git backup gives you a timestamped record of every writing session. Proof of your creative process if you ever need it.

Can I move my Scrivener project across?

Yes. Scrivener can export your manuscript as individual text files or a single document. Since Obsidian uses plain text markdown, you can import your chapters as individual .md files. Your formatting will simplify (markdown instead of rich text) but your words transfer cleanly. Character sheets, research notes, and plot outlines can come across too.

Who should stay with Scrivener

If you don't want AI in your writing process, Scrivener is still excellent. It's a one-time purchase, it's mature, it works offline, and the compiler is unmatched for producing formatted manuscripts. If your workflow doesn't need AI integration, there's no reason to switch.

If you do want AI, the question is how much friction you're willing to accept. Copy and paste works. It's just slow. A dedicated setup where the AI can see your files is faster, but it means learning a new tool.

The full story of why I switched →