Shipped v0.1.9 of Folio - a local-first IDE for writing novels

I'm building Folio - a desktop IDE for novelists who want a code-editor workflow

(panels, keyboard-driven, fast file ops) instead of a Word/Scrivener vibe.

It's local-first: every chapter is a Markdown file on your disk. No accounts,

no cloud sync, no telemetry. If Folio disappears tomorrow, your manuscript is

still just a folder of `.md` files.

What v0.1.9 brings:

- Panel-visibility settings (hide/show inspector, plan, AI panels per project)

- Split IDE-wide vs. book-scoped settings (theme/font global, status flow per book)

- Plan timeline + beats improvements for outliners

- Smaller polish: status bar cleanup, settings gear moved out of the way

The bigger picture (in case you're new to it):

- 🧬 Codex / world-bible — characters, places, lore as Markdown entries

with front matter. Wikilink-style chapter ↔ entry linking, quick-open.

- 🤖 On-device AI codex extraction — runs a local Gemma model to pull

candidate characters/places/lore from a chapter. You approve/reject. Nothing

leaves your machine. (Cloud providers are also pluggable if you prefer.)

- 📤 Manuscript export — MD / TXT / DOCX / EPUB, with a "final-only"

compile mode and export warnings (missing POV, draft-status chapters, etc.).

- 📸 Auto-snapshots — chapter history, restore previous states.

What I'd genuinely like input on:

I'm wrestling with how prescriptive the "manuscript format" export should be.

Right now it's opinionated (Shunn-ish defaults), but writers querying agents

have wildly different submission specs. Do you (a) want presets per

agency/publisher, (b) raw style-string control, or (c) just give me the .docx

and I'll style it myself? Curious what writers here actually do.

→ Folio on Product Hunt

(Solo dev, ~6 months in, macOS first, Windows/Linux builds working but less

tested. Happy to answer anything.)