Updates
Next: Mark rules the eleven calls in review-1 (the preference's default, what invisible means, inline notes, skip, who owns the notes, one update or two, when an automatic install restarts, the version string, Settings' seat, the clock and the age line, the era as data). Then Phase 4: the rulings applied to the mocks, and the states pushed into qnative as stories through /gpui-story.
The desktop app will update often, and the part that installs updates had no screen, no choice and no notes.
One Settings screen that says where an update stands, three ways to let it happen, a quiet trace after it does, and the same screen ready for a bigger rollout later. Eleven choices wait for Mark.
Documents
With file names, on their own page →Start here
Documents
Threads
What changed
The three changes that matter most, in plain words. Open any one to see it.
- 1
One picture shows every state an update can be in, who decides what happens next, and how the screen grows later.
An update and its states · came from Mark Parsonopen →
- 2
A new Settings screen shows the version you have, the new one, what is in it, and one button for the next step.
Settings › Updates · came from Mark Parsonopen →
- 3
When the app updates itself, it tells you what changed in the places you already look, and never interrupts.
Quiet, never hidden · came from Mark Parsonopen →
- Build partners see our own notes today; the same screen grows a Beta channel and company rules later. New in this cycle
- We read how other apps handle updates before deciding ours, and borrowed the good parts. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
c139-M1 Updates can be launched from the app's settings. — Mark Parson
c139-M2 Updates are invisible to the person if their preference says so. — Mark Parson
c139-M3 Show the current version, the new version and a link to the release notes. — Mark Parson
c139-M4 Early users, the build partners, may see our internal notes, so the first era of updates can look different from the structured rollout that comes with maturity. — Mark Parson
One picture shows every state an update can be in, who decides what happens next, and how the screen grows later.
From the record: no recorded conversation behind this one.
c139-M1 Updates can be launched from the app's settings. — Mark Parson
c139-M3 Show the current version, the new version and a link to the release notes. — Mark Parson
A new Settings screen shows the version you have, the new one, what is in it, and one button for the next step.
From the record: no recorded conversation behind this one.
c139-M2 Updates are invisible to the person if their preference says so. — Mark Parson
When the app updates itself, it tells you what changed in the places you already look, and never interrupts.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Asked for updates with a face, and for two eras
Opened the cycle on 2026-11-11: updates launched from Settings, invisible if the person prefers, the current and new version with the notes, and build partners seeing our internal notes before a structured rollout comes with maturity.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 17
The full record 4 decisions · 6 key-change entries · 1,859 words · 17 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c139 →