QUILL Lite changelog

2.0.0

Scribe for Documents, off until you turn it on (2026-11-21)

QUILL Lite can now send a document you choose to Pneuma Solutions’ Scribe for Documents, which rebuilds scans and badly made files into accessible Word, HTML, tagged PDF, EPUB, Kindle, DAISY with audio, MP3 audio and braille. Powered by Scribe for Documents. Chapter 17 of the guide has the whole story.

GitHub Guide: every chapter is about the Workbench, with walk-throughs, a QUILL Lite chapter and an appendix (2026-11-20)

The GitHub Guide now reads like the WordPress and Forms guide, and matches what shipped.

GitHub help, the GitHub PRD and the release notes describe the Workbench (2026-11-20)

Back Up and Restore Settings keep this computer’s settings (2026-11-20)

The startup folder is no longer put in a backup; like recent files, it belongs to this computer. Restoring a backup keeps this computer’s recent files, session, window size and startup folder. A backup made by QUILL or another app in the family is refused, with a plain explanation, and nothing is changed. Retry in Activity no longer writes an older settings save over a newer one.

The setting you chose last is the one that is saved (2026-11-20)

Turning a View setting on and straight back off, such as Word Wrap, could save the first choice and lose the second, and a View change made just before OK in Preferences could be written after it. Either way the setting changed back after a restart, and nothing was said. Every settings save now goes through one queue, in the order you made the changes, so the last choice wins. A second QUILL Lite window’s changes are still kept. A failed save is still reported and never called saved, and Retry in Activity (Shift+F9) saves your current settings rather than the older ones that failed.

The actual result, once, and lists that stay still (2026-11-19)

Part of the family UX pilot (FUX-04 and FUX-06), shared with QUILL. Saves name the file and its folder (“Saved notes.txt in Documents.”). A background Word save you typed through says that what you typed is not in it yet. Recovering a draft says which, from when and that it is not saved yet, and counts only the drafts that really came back. An open Recent Documents window, the Problems list and the recovery window keep your row, its place on the screen and focus when they refresh, and say nothing extra.

WordPress: Properties keeps your edits when a save fails (2026-11-18)

The WordPress Workbench’s Properties sheet closed on OK the moment it sent the change, so a refusal from the site, or Cancel on “Changed on the Site”, lost every edit on it (review item 32). Now OK and Apply grey out while the save is on its way, and the sheet closes only once the site has taken it; a failure, or declining to replace someone else’s change, leaves the sheet open with your edits.

Forms: a Form Payments switch, as QUILL has (2026-11-18)

Tools > Customize Features (Ctrl+Alt+F10) has a new area, Form Payments, off until you turn it on, as QUILL’s is. While it is off, Tools > Forms has no payment commands. Every profile but Everything leaves it off, and it needs Forms on. The profiles now count 25 areas.

Forms: Square, and more than one account per provider (2026-11-18)

WordPress: it asks before anything leaves for an AI or the Media Library (2026-11-18)

In Short now asks before it sends the page’s text to your AI, naming the AI and the number of words, as Visual Review always did. Ask the Site says, before an ability runs, that what it returns goes to your AI too. Make a Listening Version asks before it records and uploads the first time, and Publish a Document as a Page asks before it uploads the original: an uploaded file can be reached on the site before the page is published (review item 33).

WordPress: the WordPress key says when it times out (2026-11-18)

WordPress: five ways the Workbench could lose your work, closed (2026-11-18)

The WordPress review of 14 November listed eleven ways the Workbench could change or lose something without warning. Checked again against today’s code, five were already fixed and one is half fixed. These are fixed now:

Still open: some Workbench changes (Reply, Merge Into, the Empty commands, shop and event edits, among others) are not yet written to Change History, so Ctrl+Z straight after one undoes an older change instead.

GitHub Copilot SDK 2.0.1 and optional agent features (2026-11-18)

Compare with Site marks each changed line, from Kelly Ford (2026-11-18)

File > WordPress > Compare with Site now starts with a summary (“Comparing your copy with the copy on Community Radio: 1 line added, 3 removed, in 2 places”), then gives each change with where it is (“Lines 10 to 15:”), each line marked first: “Removed” is on the site, “Added” is yours, “Unchanged” is in both. A blank line reads “blank line”. The marks are one of Kelly Ford’s four styles from GHManage and The Chat Place (words, short words, diff symbols, or diff symbols with changed lines), the same saved choice QUILL uses everywhere it shows a difference; it is chosen in QUILL’s Compare Files or the GitHub Workbench. Before, the lines read “Site:” and “Yours:”.

What is left for GitHub, settled a second time (2026-11-18)

Every one of the 422 GitHub endpoints still planned was read again, by Jeff’s request, to ask whether it needs building at all.

Jeff then chose to build the Copilot coding agent and Sponsors as the one sponsored, and to leave GitHub Classroom and 32 preview features (issue artifacts and suggestions, stacked pull requests, pull request creation caps, code quality, planning statuses, concurrency groups) out of scope. That leaves 272, every one to build: Projects, issue relations and fields, organization roles, rulesets, teams and runners, the coding agent, Sponsors, Discussions, gists, commit comments, environment rules and more.

GitHub Pages: turn it on or off, rebuild, check (2026-11-18)

In a repository’s GitHub Pages in the GitHub Workbench:

Pages deployments themselves are made by the actions/deploy-pages workflow step, which has its own identity token, so QUILL leaves them to it. Planned GitHub endpoints fall from 430 to 422.

Reviews already on a pull request (2026-11-18)

Reviews… on a pull request in the GitHub Workbench lists its reviews (“sam approved on 2026-11-17: Looks good”). Choose one, then:

A pull request’s commits, which File Differences already reads, are counted now. Merging with GitHub’s background merge route is left to Merge…, which does the same. Planned GitHub endpoints fall from 441 to 430.

Environments, their secrets and variables, and some routes counted (2026-11-18)

Planned GitHub endpoints fall from 456 to 441.

More on a workflow run (2026-11-18)

A workflow run’s row in the GitHub Workbench has six more commands:

Planned GitHub endpoints fall from 467 to 456.

Reacting to a release (2026-11-18)

React… on a release in the GitHub Workbench adds or removes your reaction, from the same list of reactions as an issue’s, and says which. The reactions already offered in the GitHub Items window and the review window (on issues, pull requests and their comments) are now counted as built, which they were. Planned GitHub endpoints fall from 476 to 467.

Codespaces: make one, start, stop, export and publish (2026-11-18)

A codespace is a computer GitHub runs in the cloud for one repository and branch. The GitHub Workbench now has Repositories > My Codespaces for all of yours, and Code > Codespaces in each repository for that repository’s.

Codespaces can cost money; a used-up spending limit is said plainly. Planned GitHub endpoints fall from 492 to 476.

Package versions: see them, restore one, and other people’s packages (2026-11-18)

Planned GitHub endpoints fall from 503 to 492.

Copilot Autofix, every place an alert was found, and SARIF uploads (2026-11-18)

Three more things to do with code scanning in the GitHub Workbench, beyond dismissing an alert:

Each repository also has Code Scanning Analyses (every upload of results, with Delete) and CodeQL Databases (one per language, with Delete), and each organization has Code Scanning Alerts across all its repositories. Planned GitHub endpoints fall from 517 to 503. Running CodeQL’s variant analysis across many repositories is left to VS Code and the CodeQL command-line tool, which build the query packs it needs.

Actions rules, immutable releases and code scanning on Properties (2026-11-18)

Properties on a repository has two new pages:

An organization’s Properties has the organization-wide Actions Rules (the same choices, plus the workflow token’s default permission, whether Actions may create and approve pull requests, and which repositories may use self-hosted runners) and a Safety page: a week-long interaction limit for every public repository, and which repositories must keep releases immutable. Choosing “none” lifts the limit. Each is saved, checked and undone like every other field on a sheet. Planned GitHub endpoints fall from 545 to 517.

Choosing which repositories may use a secret, variable or runner group (2026-11-18)

An organization’s secrets and variables, its Copilot agent secrets and variables, its Codespaces and Dependabot secrets, its runner groups, and your own Codespaces secrets can each be limited to chosen repositories. In the GitHub Workbench, Repositories Allowed… on one of those rows opens a list of the organization’s repositories (or yours) with the ones allowed now already checked. Check or uncheck, press Enter, and QUILL says what changed: “Added 1 repository and removed 1 repository for TOKEN.” It adds and removes one repository at a time rather than replacing the list, so a change somebody else makes at the same moment is kept. A secret that is open to all repositories says to change its visibility to Selected repositories first. Planned GitHub endpoints fall from 577 to 545.

What is left to build for GitHub, and what is not (2026-11-18)

The GitHub Workbench keeps a table of every GitHub endpoint and what QUILL does with each. A review of the 904 still marked as planned settled 327 of them:

That leaves 577 to build, about two dozen batches of everyday features.

Thirty-four lists of settings, in one place each (2026-11-18)

Much of what GitHub keeps for a repository, an organization or your own account is a plain list: variables, secrets, members, invitations, blocked people, email addresses. The GitHub Workbench now has a node for each of 34 such lists, and every one works the same way. Rows read as sentences (“CHANNEL is beta, changed 2026-11-17.”), Ctrl+N adds one by asking a question at a time, Change… edits a row where GitHub allows it, and Delete… asks first. A secret is typed into a password box and sealed with GitHub’s key before it leaves your computer; it is never said, shown or kept.

Behind this, the Workbench’s count of planned GitHub endpoints fell from 1,064 to 904. Eighty-five came from these lists. The other 75 were GraphQL twins of routes the Workbench already uses or has already ruled out, so they need no second route. F1 on each new node explains its list.

Adding, labelling and removing a self-hosted runner (2026-11-18)

Ctrl+N in Repository > Actions > Runners puts the commands that set up a new runner on the clipboard, for the machine’s system, with a one-hour token that is never said. Runner Labels… adds or removes a label, and Remove Runner… forgets a runner after asking. Chapter 6 of the GitHub Guide has the details.

An organization’s packages, and restoring a package (2026-11-18)

Organizations > an organization > Packages in the GitHub Workbench lists an organization’s packages with Delete Package Version and Delete Package, and Ctrl+N in either packages list brings back a package deleted in the last 30 days. Chapter 7 of the GitHub Guide has the details.

The wiki (2026-11-18)

Repository > Wiki in the GitHub Workbench says whether a repository’s wiki is on and opens it on GitHub, and Clone Wiki… (Ctrl+Alt+W) copies its pages to a folder as Markdown files to edit in the editor and push back with git. GitHub has no API for wiki pages, so this is the way in. Chapter 7 of the GitHub Guide has the details.

GitHub Sponsors (2026-11-18)

People > Sponsorships in the GitHub Workbench lists who you sponsor and who sponsors you, and Sponsor under any person lists their tiers with prices. Sponsor at This Tier… says the price and has you type their login before GitHub charges anything; Cancel Sponsorship… asks first. Chapter 12 of the GitHub Guide has the details.

An organization’s webhooks (2026-11-18)

Organizations > an organization > Webhooks in the GitHub Workbench lists, adds, pings and deletes an organization’s webhooks, with Recent Deliveries and redelivery, exactly as a repository’s do. Sign In with GitHub asks for the admin:org_hook permission for it. Chapter 7 of the GitHub Guide has the details.

Repository > Settings in the GitHub Workbench now has Webhooks, Deploy Keys and Autolinks, each a list of sentences with Ctrl+N to add one and Delete to remove one. A webhook also has Ping, Recent Deliveries with redelivery, and Change Address or Secret; its secret is typed in a password box and never shown, said or kept. Chapter 7 of the GitHub Guide has the details.

Your SSH, GPG and signing keys (2026-11-18)

People > My Keys in the GitHub Workbench lists your SSH keys, GPG keys and SSH signing keys, each with the fingerprint ssh-keygen -lf prints, so you can tell which key is which. Ctrl+N adds one, read from a file or pasted, and refuses a private key before anything is sent; Delete Key… says what stops working first. Sign In with GitHub now asks for the three key permissions. Chapter 12 of the GitHub Guide has the details.

Security policy, advisories, and reporting a vulnerability privately (2026-11-18)

Repository > Security > Policy in the GitHub Workbench says where a repository’s security policy is and whether vulnerabilities can be reported privately. Advisories lists its security advisories as sentences, and New Here there reports a vulnerability privately or drafts an advisory; Publish or Close Advisory… and Request CVE… are on each. Search > Security Advisories searches GitHub’s Advisory Database by package, CVE or GHSA id. Chapter 8 of the GitHub Guide has the details.

Unlinking a branch, and taking back “duplicate of” (2026-11-18)

Unlink Branch… on an issue takes a linked branch off its Development, leaving the branch, and Not a Duplicate… takes back “duplicate of #n” when an issue was closed against the wrong one. Chapter 4 of the GitHub Guide has the details.

Profiles as sentences (2026-11-18)

People > My Profile in the GitHub Workbench, and Profile under any person, read a GitHub profile as rows: who they are, their bio and status, the year’s contributions by kind, the contribution calendar as numbers (the busiest day, the longest and current streak, and each month), and what they pinned. Chapter 12 of the GitHub Guide has the details.

Star lists (2026-11-18)

Repositories > Star Lists in the GitHub Workbench lists every repository on each of your GitHub star lists, the list’s name first. Ctrl+N there makes a list, Star Lists… on any repository chooses which lists it is on, and Rename or Delete Star List… changes or deletes a list. Chapter 7 of the GitHub Guide has the details.

My Packages, and Set Your Status that works (2026-11-18)

Repositories > My Packages in the GitHub Workbench lists your container images and npm, Maven, RubyGems and NuGet packages, each as one sentence, with Delete Package Version… and Delete Package… on each, both asking first. Sign In with GitHub now asks for the user permission instead of user:follow, because GitHub lets Set Your Status… change your status only with user, and for read:packages and delete:packages. If an account is missing a permission a command needs, QUILL now says to sign in again rather than repeating GitHub’s message alone. Chapters 1 and 7 of the GitHub Guide have the details.

Commit activity as tables (2026-11-18)

Repository > Insights > Commit Activity in the GitHub Workbench reads GitHub’s Insights charts as rows: commits and lines added and removed each week, the ten busiest hours of the week, the last four weeks, and each contributor’s commits and lines, every row a whole sentence. Chapter 7 of the GitHub Guide has the details.

Annotated tags, and transferring a repository (2026-11-18)

New Tag… in the GitHub Workbench’s Tags view now asks for a message too: give one and the tag is annotated, carrying the message, who made it and when, the way most projects tag a release. Read Tag Message on a tag says it. Transfer Repository… (Ctrl+Alt+T, on the Workbench’s Repository menu and on Repository Actions) moves a repository to another person or organization after you type its full name. Chapter 7 of the GitHub Guide has the details.

Self-hosted runners, and a software bill of materials (2026-11-18)

Repository > Actions > Runners in the GitHub Workbench lists the machines a repository brings to run its own jobs: online and idle, online and busy, or offline, with each one’s system and labels, so a job waiting forever has an answer. Export Software Bill of Materials… (Ctrl+Alt+B, on the Workbench’s Repository menu and on Repository Actions) saves every package the repository depends on as an SPDX (Software Package Data Exchange) file for a security review. Chapters 6 and 8 of the GitHub Guide have the details.

Hiding a comment, and a commit’s status (2026-11-18)

An issue’s timeline has Hide or Show Comment…, which folds a comment away for everyone for a reason, spam or off topic, without deleting it, and shows it again. A commit’s context menu has Set Status…, which reports a check you ran yourself on that commit. Chapters 4 and 7 of the GitHub Guide have the details.

Your GitHub status (2026-11-18)

Set Your Status… on the GitHub Workbench’s Account menu reads the status beside your name and sets a new one, with an emoji by name, busy or not, and when it clears, or clears it. Chapter 13 of the GitHub Guide has the details.

Tags without a release (2026-11-18)

The GitHub Workbench’s Tags view can make a tag on its own, on any branch, tag or commit, and delete one, saying first when a release is built on it. Chapter 7 of the GitHub Guide has the details.

Invitations, and turning a workflow on or off (2026-11-18)

Needs My Attention > Invitations in the GitHub Workbench lists the repositories you have been invited to, who invited you and with what access, and accepts or declines each after asking. Turn Workflow On or Off… on a workflow says whether it is on, or turned off and by whom, including GitHub’s own switch-off after sixty quiet days, and asks before changing it. Chapters 3 and 6 of the GitHub Guide have the details.

Re-run Failed Jobs, pressed twice (2026-11-18)

Pressing Re-run Failed Jobs again before GitHub had answered the first press sent a second re-run. It now says the first is already on its way and sends nothing.

One commit at a time, and whitespace hidden (2026-11-18)

The pull request diff window has Hide Whitespace Changes, which leaves out lines that changed only their spaces, tabs or blank lines, and Choose Commit…, which shows one commit of the pull request at a time, against the commit before it, with the whole pull request one choice away. Chapter 5 of the GitHub Guide has the details.

One comment window everywhere (2026-11-18)

A reply to a discussion, and Reply to Thread in a pull request review, now open the same comment window as a comment in the GitHub Workbench, with mentions, references, emoji, saved replies, a preview and the check before posting. A line comment and the review message each have Comment Window… (Alt+W), which opens it with what you have written so far and brings the text back. Chapters 5 and 8 of the GitHub Guide have the details.

Load More, on every list (2026-11-18)

Load More, on the GitHub Workbench’s View menu, now reads one more page of any list, and Load All reaches every list too: Notifications, My Work, discussions, labels, the merge queue and the rest, which used to stop at their first 50 rows whatever you asked. When a list holds only part of what GitHub has, the status bar says so and says how to read the rest. Chapter 13 of the GitHub Guide has the details.

Dry Run and a practice repository (2026-11-18)

Dry Run, on the GitHub Workbench’s Tools menu, lets every command ask and preview as usual and then stop before sending anything to GitHub, saying exactly what it would have sent. Practice on GitHub…, on its Help menu, makes quill-practice, a private repository in your account with issues, labels, a pull request and a failing run to learn on, and deletes it or starts it over when you finish. Failures in the Workbench are now said without the support code in brackets. Chapter 12 of the GitHub Guide has the details.

Emoji by name (2026-11-18)

In the GitHub Workbench’s details pane and in Read as Document, emoji shortcodes such as :tada: and :+1: are read by name, “party popper” and “thumbs up”, rather than spelled out; shortcodes in code are left alone. Chapter 12 of the GitHub Guide has the details.

Inbox rules (2026-11-18)

Item > Inbox Rules… (Ctrl+Alt+N) in the GitHub Workbench makes rules for notifications: mark done, mark read or move to the top whatever comes from a repository (with * for any part), for a reason, about a kind of thing, or with words in its title. Each new rule is read back and tried on the notifications loaded today before it is saved, and the rules run every time Notifications loads, saying what they did. Chapter 3 of the GitHub Guide has the details.

Following a running job (2026-11-18)

The workflow jobs window has Follow This Job (Alt+W). Check it on a running job and you hear each step as it starts and as it finishes, and the job’s end, without watching the screen; following stops when the job does. Alt+8 says how far along the selected job is at any time: the step it is on, how many are done, and any that have failed. Chapter 6 of the GitHub Guide has the details.

Hearing a diff (2026-11-18)

The pull request diff window has Changed Lines Only (Alt+H), which leaves the unchanged lines around each change out of the patch list so the arrows go from change to change, keeping each hunk’s heading. And arriving on an added or a removed line now plays a short sound of its own, two new moments in the Sound Scheme window that can be previewed, changed or switched off. The Ink scheme has new sounds for them, and the VS Code Signals scheme uses Visual Studio Code’s own diff sounds. Chapter 5 of the GitHub Guide has the details.

Why a pull request cannot merge, and merging the commit you checked (2026-11-17)

Why Can’t I Merge? on a pull request in the GitHub Workbench says whether it can merge, or each reason it cannot (draft, conflicts, behind its base, a review needed, required checks failed or running, a branch rule) with what to do, always naming the commit it is about. Merge… asks the same first, and merges only that commit: if somebody pushes in between, nothing is merged and you hear why. Auto-Merge… and Add to or Remove from Merge Queue… are on the pull request’s row, and a repository’s Merge Queue lists its queue in order. Chapter 5 of the GitHub Guide has the details.

A pull request’s patch, revert and conflicts (2026-11-17)

Three new rows on a pull request in the GitHub Workbench. Open Patch in Editor opens its whole change as one unified diff, every file in turn, with any file GitHub sends no text for (an image, a very large file) named on a line of its own. Revert Pull Request… opens a new pull request that undoes a merged one, asking its title and whether it is a draft. Resolving conflicts on your own computer needs local Git, so that one is in QUILL. Chapter 5 of the GitHub Guide has the details.

Files you have viewed, in a pull request review (2026-11-17)

The pull request review window now shows, for each changed file, whether you have viewed it, as GitHub keeps it for you: viewed, not viewed, or changed since you viewed it. A file’s context menu has Mark as Viewed (or Mark as Not Viewed), the same mark GitHub’s Files tab shows, and Show Only Files Not Viewed, so the outline holds only what is left to review. Comment on This File… comments on a whole file rather than a line, in the comment window with its mentions, preview and check. Chapter 5 of the GitHub Guide has the details.

Writing a comment, with help (2026-11-17)

Comment… in the GitHub Workbench now opens a comment window that does what GitHub’s own comment box does, by ear. Insert Mention… (Alt+M) lists the conversation’s people first; Insert Reference… (Alt+R) finds an issue or pull request by words in its title; Insert Emoji… (Alt+E) finds one by name; Insert Saved Reply… (Alt+S) uses the saved replies you keep on GitHub. Preview (Alt+P) reads the comment as GitHub will show it, saying what each line is and who will be notified. Check before posting (Alt+H), on to begin with, asks before sending a comment with an image that has no description, a “click here” link, a skipped heading level, a long run of capitals or only an emoji. Ctrl+Enter posts. Attach Files… says plainly that GitHub lets no other program attach a file, and what to do instead.

An issue’s reason, its branch and its task list (2026-11-17)

In the GitHub Workbench, closing an issue now asks why, as GitHub does: Completed, Not planned, or Duplicate of another issue…, which asks for the other issue’s number and records it on GitHub. Until now Close or Reopen… promised a reason and never asked. Create Branch for This Issue… makes a branch from the default branch, named as GitHub suggests (7-fix-the-parser), and links it to the issue, so it is the issue’s Development on GitHub; the issue’s properties list its Linked branches. Check or Uncheck a Task… turns over one item of the issue’s task list, and Convert Tasks to Sub-issues… makes each plain task an issue of its own and links its line to it. Both read the description again just before saving, and save nothing if somebody changed it meanwhile. Chapter 4 of the GitHub Guide has the details.

Many issues at once, from a spreadsheet or from lines (2026-11-17)

The GitHub Workbench’s File menu gains two ways to make issues in bulk, each with a preview before anything is sent and a sentence for each issue after. Import Issues from a Spreadsheet… (Ctrl+Alt+I) reads a CSV file or an Excel workbook, matches its columns to title, body, labels, assignees, milestone and type by name, and skips, with the reason, any row that GitHub would refuse, numbering rows as your spreadsheet does. New Issues from Lines… (Ctrl+Alt+L) turns each line of your editor selection into an issue, list markers and check boxes taken off, and can make them sub-issues of an issue you name. The spreadsheet reader is the WordPress Workbench’s, now shared.

Fixes from today’s reports (2026-11-17)

Two fixes in code QUILL Lite shares with QUILL:

GitHub from the line you are on (2026-11-17)

Most GitHub questions start in a file. Put your cursor on a line, or select a few, and eight new rows in the GitHub menu answer without leaving the editor. They sit between separators while workbench mode is on, and are in the Command Palette always. QUILL has the same eight, as GitHub > From This Line.

All eight are refused in Safe Mode, need git, have no key out of the box, and can be reached from Say or Type a Command. The GitHub Guide’s Chapter 7 has the details.

Export any GitHub Workbench list (2026-11-17)

Export List… (Ctrl+Shift+X), on the GitHub Workbench’s own File menu, saves the list in front of you as it is shown, its columns, filter and rows, as an Excel workbook, a CSV file or a Markdown table. A Markdown table opens in the editor as a table if you like, where the table keys move cell by cell. It works on issues, pull requests, runs, alerts, people, Change History or any other list, and says how many rows it wrote and which hidden columns it left out. It is the WordPress Workbench’s Export List, now one command shared by both.

GitHub issue forms, written as plain text (2026-11-16)

A GitHub issue form is the form people fill in when they open an issue. In both QUILL and QUILL Lite, Tools > Forms now has Save As GitHub Issue Form…, which saves the form you are writing as one, and Open GitHub Issue Form…, which reads one back so you can edit it as plain text in the form language. Before saving, a window lists what GitHub’s forms cannot hold, one line each, such as a signature question or a condition, and says if GitHub would refuse the result. Going the other way, what only GitHub has (labels, the issue title prefix, ids, an answer shown as code) is kept with the form and given back on the next save, so QUILL’s own five issue forms go to the form language and back unchanged. Nothing is sent anywhere, and both work in Safe Mode.

Properties for everything in the GitHub Workbench (2026-11-10)

Filtering on every attribute (2026-11-10)

Permissions you can see, and control (2026-11-10)

The WordPress Workbench is where Tools > WordPress leads (2026-11-10)

The GitHub Workbench is the GitHub window now (2026-11-10)

Help everywhere in the GitHub Workbench (2026-11-10)

The GitHub menu becomes a short list of doors (2026-11-10)

With GitHub Workbench Mode on, the GitHub menu now holds only the ways into the GitHub Workbench and the few things that belong to the editor.

The GitHub Workbench gets its menus, its keys and its own options (2026-11-10)

This step gives the GitHub Workbench window everything a window needs to be lived in.

The WordPress Workbench, for trying out (2026-11-09)

WordPress custom fields that hold lists and groups (2026-11-09)

GitHub context menus put first things first (2026-11-09)

Change how requests are understood (2026-11-09)

The GitHub Guide has its own folder (2026-11-09)

Say or Type a Command: Jev and your own AI (2026-11-09)

Built on wxPython 4.3.2 (2026-11-09)

GitHub tokens are the advanced road, and a Workbench cell (2026-11-08)

Problems, Word Prediction and Indent: fixes (2026-11-09)

Language servers (2026-11-08)

Say or Type a Command (2026-11-08)

GitHub Workbench Mode and Clone Repository (2026-11-08)

The Problems pane lists every open document (2026-11-08)

The Problems pane checks on save (2026-11-08)

Word Prediction knows your project (2026-11-08)

Word Prediction knows your code (2026-11-08)

Word Prediction (2026-11-08)

The Problems pane (2026-11-08)

Sign In with GitHub (2026-11-08)

The guides, from every download (2026-11-08)

GitHub Workbench: review threads, Explore and job logs (2026-11-07)

QUILL Lite’s shared GitHub Items window now includes Explore, saved global searches, My Work, repository discovery, PR thread resolution and exact diff line targeting, and workflow job logs. The same keyboard and context-menu patterns are described in the QUILL workbench reference.

GitHub: Copilot, commit comments, gists and queue summaries (2026-11-07)

Sign in to GitHub from QUILL Lite (2026-11-07)

A complete GitHub guide (2026-11-07)

GitHub search, releases, housekeeping and rate limits (2026-11-07)

Paste Copied Files, saved replace jobs and fields in abbreviations (2026-11-07)

GitHub repository files, milestones, discussions and security triage (2026-11-07)

GitHub pull request review, line by line (2026-11-07)

GitHub notifications, failed runs and merge automation (2026-11-07)

GitHub workbench (2026-11-05)

Hear the clipboard, the time and what is open (2026-11-06)

Nemotron keeps its last word (2026-11-06)

QUILL’s new Navigate > Code submenu, with the same rows, letters and keys, from the same code.

The WordPress key on every keyboard layout (2026-11-06)

Document Statistics, pressed twice (2026-11-06)

Searches that say more (2026-11-06)

Math as MathML in exported pages (2026-11-06)

Describe Formatting names the text colour (2026-11-06)

Replace All takes what you typed, and a missed backup is said (2026-11-06)

First-page and even-page Word headers are named before a rich edit (2026-11-06)

Taking payments with your forms (2026-11-07)

Form payment integration (2026-11-06)

Testing build: 2.0.0 (build 1). It has not been published yet; the last published version is 1.1.2.

QUILL Lite 2.0.0 is the first release since 1.1.2, and it is a big one. Everything below is new or changed since 1.1.2, grouped by subject with the biggest first: WordPress, Forms, the Developer profile and project tasks, the Command Palette in every profile, page breaks on Ctrl+Enter, Choose Your AI with GitHub Copilot and Codex, AI help, tables in every kind of document, a thesaurus and two dictionaries, spell check that reads only what you wrote, Word documents and PDFs, Find in Open Documents and folder search, dictation and transcription, Activity and Repeat Last Result, and release channels.

WordPress

If you look after a WordPress website, QUILL Lite now writes, opens, checks and publishes its pages and posts, and looks after the site itself. It is the WordPress area in Customize Features: on in Recommended, Everything and Developer, and off in WordPad and Notepad, which never had a way to publish to a website. QUILL has the same commands in the same places, from the same shared code. The WordPress and Forms guide covers every command step by step: https://www.quillforall.org/docs/wordpress-forms-guide.html

Connecting your sites

Writing and publishing

Blocks, made plain

Pictures and the Media Library

Checking a page the visitor’s way

Running the site

Where the commands are, and their keys

Forms

Write accessible forms (contact forms, sign-ups, surveys, registrations) as plain text, check them, try them yourself, and put them on your website or on paper. It is the Forms area in Customize Features: on in Recommended, Everything and Developer, off in WordPad and Notepad. QUILL has the same commands in the same places. The WordPress and Forms guide has the whole story: https://www.quillforall.org/docs/wordpress-forms-guide.html

The Command Palette in every profile, with everything in it

Agentic coding: project tasks in the Developer profile (2026-11-04)

Project tasks with an AI, in the new Developer profile. QUILL gets every one of these in the same change, from the same code.

Page breaks with Ctrl+Enter (2026-11-03)

AI menu, own key and silent commands (2026-11-03)

Choose Your AI: your plan, GitHub Copilot, Codex or your own key

Your own key, and your prompts, shared with QUILL

AI help

Each app keeps its own ChatGPT sign-in

Your own API key can be a Google Gemini key, and you choose which

Tables

QUILL Lite can now make a table, read it cell by cell and change its shape, in every kind of document, on the same keys as QUILL. User guide: “Making a table”, “Moving through a table” and “Editing a table”.

Writing and editing

Inline notes, task lists and a page to share

The ideas here come from PlanCake, a small Windows app by Andre of Oire Software for reviewing the plans AI assistants write. Thank you, Andre. All of it is QUILL’s own code, shared, on QUILL’s keys.

Remove Quote Marks has a key that works

A thesaurus that finds the word you are on, Look Up, and an AI dictionary

Spell check, recovery and sharp text

Word, PDF and other documents

More ideas from PlanCake, by Andre of Oire Software. Thank you, Andre. All of it is shared with QUILL, on QUILL’s keys.

Large and networked files open without freezing the window

Finding, searching and recent documents

Recent Documents: the whole list on Alt+Shift+0

Dictation

Speech models: which to use, and how well each hears you

Better accuracy: optional speech models

Dictating in Spanish

Commands, corrections and spelling by voice

What you hear while you dictate, and nothing lost

Settings and word lists shared with the family

Read-back marks, voice editing, live transcripts and Dictate Anywhere

Everything below is shared code, in both editors on the same keys and the same words (QUILL: Tools > Speech > Live Dictation; QUILL Lite: Tools > Dictation).

Dictation: hold-to-talk, live words, talking to the AI, and OpenAI with your own key

Transcribing recordings

Transcribe a Recording: a recording into text with dictation’s engines

Sounds, screen readers and staying safe

Activity, Repeat Last Result, and saves that tell the truth

Find a setting, a focus repair with limits, and a tidier close

A focus repair that does not take leaves a trace

Two instances stop undoing each other’s preferences

Exit without a traceback

Keyboard Manager on Ctrl+Alt+Shift+Space

Updates, installing and release channels

Release channels: safe ways back, background downloads, and updates that undo themselves

Release channels: Stable, Beta and Dev

Portable copies start from a folder with a space in its name

QUILL Lite as your Windows text editor

Shared runtime and licensing

1.1.2 – 2026-09-30

Install and restart now installs, and restarts

1.1.1 – 2026-09-30

The version number that ran ahead of the release

1.1.0 – 2026-09-29

Your ChatGPT subscription, pictures described, and web search (2026-09-29)

Coming back to QUILL Lite puts you back in your document (2026-09-29)

Dictation, made reliable, and taught your words in a window (2026-09-28)

Nine items from the dictation plan, all shared with QUILL’s Live Dictation.

Launcher (2026-09-28)

Updates (2026-09-28)

Installer (2026-09-26)

Support (2026-09-26)

AI help

Dictation

Five finer dictation choices, and Just write what I say

Stop phrase

AI help on your own OpenAI key

1.0.1 – 2026-09-25

A fix for AI help on some Windows 10 computers.

1.0.0 – 2026-09-25

First release. QUILL with everything removed except the editor: numbered documents in one window, four kinds of document, and nothing else.

Contributed as PR #1490 by Steven Scott (doubletaponair) under this repository’s MIT licence, and adopted into the QuillVille family here. Everything below is in 1.0.0, assembled between 2026-09-08 and 2026-09-25.

Three lists, each grouped by subject: Added is what was not there before, Changed is what worked differently, Fixed is what was wrong. The two lists at the end are the QUILL side of the same work, because the rule that governs this product is that QUILL Lite may never be ahead of QUILL – so anything the small editor needed that the big one could not do went into the shared code in the same release.

Added

Files, encoding and saving

The four kinds of document

Headings and structure

Selection and marks

Spelling

The clipboard, the tray and the collector

Lines and text tools

The Insert menu

Typing, characters and the control’s own keys

Abbreviations and snippets

The status bar

Speech, sounds, and how much it says

Printing

Windows, sessions and recovering unsaved work

Features, profiles and preferences

Help, F1 and tutorials

Settings, data and where it lives

Downloads, updates and packaging

Documentation and QA

AI help (2026-09-23)

QUILL Lite gained five AI commands – summarize, rewrite, proofread, explain, and ask a question about the document in front of you – running on QUILL’s own free service. They are in Tools > AI, behind Ctrl+Alt+G (the assistant pad) and Ctrl+Alt+Z (the question box), with Usage, Connect or Sign Out and Privacy Agreement beside them.

Neither the feature switch nor the sign-in is enough to send anything. Both the area and the agreement have to be true. They are deliberately separate questions: the area answers “does this feature exist in my copy”, and the agreement answers “have I agreed to what it does”. Conflating them gets one of them wrong – an area switched on by a profile, by a settings import, or by somebody else using the machine is not consent.

So the agreement is asked for on its own, stored as a version rather than a yes, so that a material change to what is sent or kept can ask again instead of the old answer being taken to cover the new thing. It is reachable by three doors – Tools > AI > Accounts and Usage > Privacy Agreement, a check box in Preferences, and switching the area on in Customize Features – because the place somebody looks depends on which part of the app they already know. All three read and write the same answer, so none of them can disagree with the others.

How much you can ask about doubled. The input ceiling went from about 1,125 words to about 2,250 (1,500 tokens to 3,000). Input is the cheap half of a request – the answer costs more to generate than the question costs to send – so the wider ceiling makes most short documents fit whole for a modest increase per request. The service’s own headroom was raised to match, because running out of it turns hosted AI off for everyone rather than merely slowing it down.

Privacy Agreement is never dimmed, whether or not the area is on and whether or not you have accepted. A door you can only reach by first agreeing to something is not a door.

One pad behind one key, not five commands. The chords free in both editors are few, and family rule 2 says a command both products have keeps its chord – so five separate keyed commands were never on offer. One pad is the better shape anyway: one place showing what will be sent, one showing what is left, and one consent surface rather than five.

QUILL’s existing AI is untouched. No provider list changed, no default cascade changed, and no bring-your-own-key, agent or local-model path changed. The capability is shared, so the two editors run the same five commands on the same five chords from the same module – QUILL Lite is not ahead of QUILL here, and QUILL has more AI than QUILL Lite rather than less.

Release day (2026-09-25)

The last pass before 1.0 (2026-09-24)

Normal Text (2026-09-22)

Changed

Files, encoding and saving

The four kinds of document

Headings and structure

Selection and marks

Spelling

The clipboard, the tray and the collector

Lines and text tools

Typing, characters and the control’s own keys

The status bar

Speech, sounds, and how much it says

Sharing with QUILL

Speed

Downloads, updates and packaging

Documentation and QA

Fixed

Files, encoding and saving

The four kinds of document

Headings and structure

Selection and marks

Finding and replacing

Spelling

The clipboard, the tray and the collector

Typing, characters and the control’s own keys

The status bar

Speech, sounds, and how much it says

Printing

Windows, sessions and recovering unsaved work

Features, profiles and preferences

Downloads, updates and packaging

Documentation and QA

Reliability

Formatting that did not survive being converted (2026-09-24)

Twenty-eight constructs now survive both round trips exactly, asserted one by one in tests/unit/io/test_format_fidelity.py.

Headings (2026-09-24)

Rich text that other programs read (2026-09-24)

The documents, and what they were teaching (2026-09-24)

Reported while testing (2026-09-21 to 2026-09-22)

Fixed in QUILL, for every QUILL user

Both were isolated in PR #1490 and left unapplied so that adding an app and changing the editor stayed separate decisions. Both decisions were taken.

Added in QUILL, so the editor is never behind its own small sibling

A note on the two keys that used to differ

QUILL Lite shipped using WordPad’s Ctrl+J for Justify and Ctrl+Shift+V for Paste Text Only, where QUILL had spent both keys long before – Ctrl+J on Set Temporary Bookmark and Ctrl+Shift+V on Preview – so the two products disagreed about two keys and the reason was recorded in the keymap.

The family parity pass closed it the other way round: QUILL moved its own commands and both keys now mean the same thing in both editors. An existing binding somebody’s hands already know does outrank a new command’s convention, which is why this took a deliberate decision rather than a patch – but two editors in one family disagreeing about Justify outranks both. Ctrl+Alt+J and Ctrl+Alt+V are Set Temporary Bookmark and the copy tray in QUILL now; the eight keys that still differ on purpose are listed in quill/core/lite/parity.py, each with its reason.