QUILL 0.9.0 Beta 2

Built with you. Polished for all of us.

From Community Access. Free. Optional by design. Private by default. Yours to make quiet — and yours to help shape.

This release is what happens when a community does more than test software: it builds it together. Every crash report, every “this felt strange,” every missing label, every voice that would not speak, every shortcut that collided, and every idea that made QUILL more useful has helped move the project forward.

Beta 2 is not software created somewhere else and handed to the people who use it. It is the result of people speaking up, developers listening closely, testers trying again, and the whole community making QUILL better by and for each and every one of us.

The promise from Beta 1 continues here: this release is overwhelmingly your reports turned into fixes, clarity, polish, confidence, and new possibility. A few features we had been eager to ship joined the celebration too — including the long-requested page indicator, because when enough of you ask for something that matters, it deserves to move.

This is the friendly, long-form companion to the “0.9.0 Beta 2” section of CHANGELOG.md. The shorter text shown under Help > What’s New and Check for Updates comes from that changelog; this document tells the fuller story of what changed, why it matters, and where your feedback can guide the next step.

Grazie. Thank you. Keep testing, keep imagining, and keep the reports coming. This release belongs to you.

The Beta 2 celebration, at a glance


Help us finish the next chapter

Some of the most important work in this release can only be proven on the hardware and platforms you use every day. These are not ceremonial requests. Your results decide what becomes the dependable default next.

Braille display owners: please put QuillRichEdit to the test

We've been chasing two long-standing braille reports, and this release ships the first real lever for both. They are:

The lever is a new experimental editor surface called QuillRichEdit — the same native Rich Edit control QUILL already uses as its default editor, wrapped so QUILL can reach underneath it. It adds a switch that asks that same control to behave more like a plain text-edit control for braille purposes, while keeping everything that makes it read correctly to JAWS and NVDA. We do not yet know if this fixes the offset or the missing dots on real hardware — that is genuinely what we need you to find out.

How to try it, step by step:

  1. Open Preferences > Experimental.
  2. Tick Enable experimental features (the master switch).
  3. Tick Enable experimental editor surfaces.
  4. Set Editor surface to QuillRichEdit.
  5. Tick QuillRichEdit: emulate a system edit control (braille test).
  6. Apply Settings, then restart QUILL — all three of these settings take effect on the next launch, not immediately.
  7. With your braille display attached, open or type into a document and check: does text now start in cell 1, or still cell 2? Does selecting text now show dots 7-8 underneath it? Does JAWS or NVDA still read the editor's content correctly?

If you can, please test under both NVDA and JAWS — braille rendering can differ between screen readers, so a result under one does not guarantee the same under the other. Tell us what you see, for each screen reader you tried, along with your braille display model, through Help > Report a Bug, either way: helped, no difference, or worse. This is still an open question, and real-hardware reports are the only way to answer it. To go back, untick the two experimental-editor checkboxes (or set Editor surface back to its default) and restart QUILL.

This same surface also carries QUILL's first native RTF load/save and in-place bold/italic/underline/font/alignment formatting, as a first step toward a lighter-weight rich-text document mode — but the braille question above is the reason it needs your feedback most.

Mac users: three quick checks that can close the loop

If you use QUILL on macOS, three things would help us enormously. Each is fixed in code in this release but needs a Mac to confirm, so please try the fix and leave a short comment — helped, no difference, or worse — so we can close it out or reopen it.


Everyday writing now feels more alive

These are the changes you can feel immediately: clearer navigation, stronger document accessibility, smarter printing, less friction, and more ways to make QUILL fit the way you work.

A page number — honestly presented

A tester asked directly: "Are we going to be able to see proper page numbers with QUILL?" Now every document shows one, in the status bar, on by default, right next to your line/column position.

Alt text you cannot accidentally skip

GLOW already catches missing alt text after the fact — this adds the proactive half. Insert > Image... is QUILL's first dedicated image-insertion flow: it won't let you insert without either real alt text or an explicit "this image is decorative" choice, so a document can no longer quietly pick up an un-alt-texted image. And for any image already in your document, however it got there, Tools > Describe Image at Cursor tells you exactly what's there: "Image: sunset.png, alt text: a sunset over the lake" — or just as clearly, "alt text MISSING" if nobody ever wrote one.

File > Print Studio... tells you what you're about to print before you print it — "3 pages, Letter, default margins" — read aloud or in braille, the way a visual print preview would show a sighted user. Then choose all, odd, or even pages, reverse the order, or skip the first page if it's pre-printed letterhead, before it hands off to the same Print dialog you already know. Printing itself also got more honest along the way — it used to draw whatever fit on one page and quietly drop the rest of a longer document; now it paginates properly.

Headers and footers, built for real documents

File > Header and Footer... builds one from named presets — title on the left with the page number on the right, filename and date, Roman numerals for front matter — or your own mix of a handful of tokens (title, filename, date, page number) placed left, center, or right. Want a different header on page one? There's a checkbox for that. Numeric or Roman page numbers, starting wherever you like. It's saved with the document and shows up on every page you print, Print Studio or plain Print alike.

Five joyful upgrades for the work between the big moments

Make the QUILL key truly yours

A new Change QUILL Key... button in the Keymap Editor (Preferences > Keyboard > Keymap Editor) lets you reassign the QUILL-key prefix itself — the key every QUILL Key + ... chord starts with. Pick a new one and QUILL validates it, warns you about conflicts with other bindings (and with OS-reserved chords), then rewrites your stored chords to follow the new prefix, so QUILL Key + S, QUILL Key + V, and the rest all move together instead of you rebinding them one at a time. And typing quill in the Keymap Editor's search box now lists every QUILL-key-chord command in one place, so you can see — and rebind — the whole chord set at once. It works the same on Windows and macOS.

“Casual Writer” finally gets out of your way

Focus, status, and labels that tell the truth


Your language, your braille, your way of working

Accessibility grows when more people can arrive as themselves. Beta 2 expands QUILL’s language reach, restores features that translations exposed, and keeps braille and screen-reader use at the center rather than at the edge.


Optional power, without optional confusion

QUILL remains small on purpose. The larger pieces arrive only when you choose them — but choosing, installing, testing, removing, and returning to your work should feel welcoming, predictable, and complete.

Getting the extras you want, completely reimagined

QUILL stays small by downloading the big optional pieces only when you ask. Beta testers told us that experience was confusing — so Help > Download Optional Components was rebuilt into one warm, guided place.

PDF and Office extraction is one clear download away


Speech that speaks, dictation that listens, and audio that respects your time

The speech stack received one of the deepest practical passes in Beta 2. Voices now prove they work, previews behave like previews, transcription is more dependable, and long-running audio work gives you control instead of holding QUILL hostage.

Voices, Read Aloud, and offline transcription

Audio Studio: progress, cancellation, safer closing, and cleaner output


AI that is understandable, local-friendly, and actually configurable

AI setup should never imply that a local provider needs a cloud key, hide a working Ollama installation, or send you to a terminal for routine setup. Beta 2 turns those rough edges into a guided path that respects local, remote, and cloud choices.

Ollama and the AI Setup Wizard

Agent SDKs, model discovery, and interrupted installs


Explore GitHub without leaving your editor

QUILL could already open and save files from a GitHub repository. Now it can also show you what's going on in one — the issues, pull requests, branches, commits, tags, releases, and workflow runs — without leaving the editor or firing up a browser. File > Open from Remote > GitHub Items... opens a read-only viewer modeled on the open-source GHManage viewer, built keyboard- and screen-reader-first.

Type owner/repo and load (if you're already editing a file you opened from GitHub, the repository is filled in for you). Pick a view — the combined Issues & PRs inbox, Branches, Commits, Tags, Releases, or Workflow Runs — and the list shows one row per item while a details box below shows the full text. In the Issues & PRs view you can also filter by issues/PRs/both, by open/closed/ all, and sort by number, title, last-updated, or comment count.

Two list modes matter for screen readers: Quick shows compact cells, and Full spells each one as field: value (number: 208, type: ISSUE, state: OPEN) so your reader announces a self-describing line per row instead of bare values. Select an issue or PR and the comment thread loads beneath it; Alt+N and Alt+P jump between comments, announcing "Comment N of M." Enter opens a row in your browser — and on a branch row, it drills into that branch's commits. Ctrl+R refreshes, Ctrl+O opens in the browser, Ctrl+G jumps to an issue or PR by number, and View More loads the next page.

It's read-only for now — you can browse and open, but not close, reopen, or comment from inside QUILL. The same gates apply as the other GitHub commands: disabled in Safe Mode, first-run consent, and anonymous access for public repositories (lower rate limit) or your stored token for private ones. (#924)

Mastodon posts now respect language and instance limits


macOS: a top-to-bottom platform transformation

QUILL's macOS support got a top-to-bottom review across several passes this release. Everything Mac-specific lives here in one place. We develop on Windows, so every Mac fix below was made without a Mac in front of us, and a few genuinely need your eyes to close out. Items marked (tester results wanted) are code-complete and unit-tested here but only show their real effect on a Mac — please try the fix and tell us through Help > Report a Bug (or the linked support issue) if a symptom persists, so we can close it out or reopen it.

This work reaches far beyond a handful of compatibility patches. It makes QUILL more recognizably Mac-like in its menus, shortcuts, launching, voices, Keychain behavior, portable mode, Finder integration, security, theming, clipboard use, announcements, and build discipline.

The complete macOS improvement pass


Install QUILL your way

Whether you want the smallest regular installer, a portable copy that carries its optional pieces with it, a command available from every terminal, or a machine that must never touch the internet, Beta 2 gives you a clearer path.

Fully offline, when you need it

QUILL normally keeps its installer small by downloading the bigger optional pieces — Pandoc, offline speech engines, neural voices, the braille pack, and more — only when you first reach for them. That's the right default for most people, but it assumes you have an internet connection at some point after install. A new Offline Edition build removes that assumption entirely: every optional component ships inside the installer and the portable bundle up front, so QUILL is fully functional the moment it's installed, with no internet connection ever needed — right for an air-gapped machine, a locked-down work laptop, or anywhere your first login can't reach the internet.

Help > Download Optional Components knows the difference: in the Offline Edition, every bundled piece shows as Bundled instead of offering a Download button, since there's nothing left to fetch. The regular, smaller installer and portable download you already know are unchanged and remain the default choice for everyone else.

A simpler installer — and a lighter one

Add QUILL to PATH when that fits your workflow


Trust is a feature

A community-built editor must be dependable not only when everything works, but also when something fails. Beta 2 strengthens the path from error to report, protects more personal information, verifies extension signatures for real, and makes support details far more actionable.

Bug reporting that actually reaches us

After upgrading, some of you found the bug reporter saying "no token." The Windows build wasn't including the built-in reporting token, so it shipped empty. It's fixed at the source, and now every build refuses to ship without it — release, beta, or a local test build, on Windows and macOS alike, with no opt-out — so a tokenless bug reporter can never reach anyone again. If the token is ever missing at runtime, QUILL opens the online bug form for you — reading the instructions aloud — instead of leaving you stuck. And if an already-running build is found to be missing the token, Check for Updates offers to reinstall the latest release even at the same version — with a dialog that says it restores the bug-report token, so "update to the version you already have" is not confusing. A silent background check only records a notification (it never auto-reinstalls the running version); use Skip this version to silence it, and it stops the moment the token is back.

This is the fix behind every "please try this and tell us" ask in these notes — it's what makes Report a Bug dependable on every install, Mac included.

Quillin signatures are now genuinely verified

Together, these two changes cover both sides of trust: normal shipping builds now perform the real cryptographic check, while an unusual or incomplete environment fails gracefully instead of taking the manager down with it.

The Quillins Manager stays open when you need it


Reliability work that protects real work

Many of the fixes below are quiet by design. They remove freezes, false crash recovery, stale focus, clipboard races, encoding failures, and diagnostics gaps — the kinds of problems that disappear when the software is doing its job well.

Windows shutdown, shell integration, and clean exits

Clipboard and community-reported crashes

Files, encodings, conversions, startup, and support codes


With gratitude — and with momentum

Beta 2 is a community release in the truest sense. Elena Brescacin (elettrona) gave QUILL its first non-English voice. Richard Wells chased down the Kokoro and Piper voice issues with patient, detailed reports and diagnostics. And every tester who hit an odd crash, a stuck focus, a missing language, or a confusing download and took the time to tell us — this release is yours. Please keep it coming.

Beta 2 proves something bigger than any single feature: when people are heard, when feedback is treated as design input, and when accessibility is understood as a shared responsibility, software can become more useful, more humane, and more joyful with every pass.

This is how QUILL grows: openly, thoughtfully, stubbornly, and together. Built by the community. Built for the community. Built for every one of us.