Skip to content

Changelog

Every release, as it shipped

A minor release changes what Lodestar is. A patch keeps a promise the last one made. Each series opens with the release that named it, and its patches follow.

0.55Minor · November 16, 2026

Lodestar 0.55.0

Dictation hears you sooner and gets more of it right, and the editor checks your writing in about half the time.

The draft now hears you with Nemotron, a model that runs on this Mac, in place of Apple's recognizer. Your words appear about 0.4 seconds behind your voice, where they were 1.2 seconds behind, and once they appear they are never rewritten as you go on. On the recordings it was measured on, fewer words came out wrong (8.7% against 11.4%) and more names came out right (84% against 79%). Lodestar fetches it first, before anything else dictation uses, and keeps it ready from launch, so no draft waits for it. Until it is here, when the Mac is very short of memory, or when you dictate in a language other than English, Apple's recognizer hears you as before.

When you press ⏎, the draft lands at once. It waits only for Parakeet, which takes about a tenth of a second. Qwen3-ASR then hears the last fifteen seconds again behind it, and its words go in if they arrive before the draft lands. It used to hear up to a minute again, which took several seconds on a long dictation, so ⏎ waited its full second and often landed the words unchanged. On the same recordings, 7.1% of words came out wrong and 97% of names came out right, where it was 9.5% with a one-second wait.

What dictation runs now follows your Mac's memory, and you no longer choose it. From 8 GB it runs Parakeet alone, where Apple's recognizer was all a Mac that size had before. From 16 GB it adds Qwen3-ASR and Gemma, from 24 GB the larger Qwen3-ASR, and from 64 GB the largest language model. Only the models your Mac runs stay on disk. Settings shows what is in use instead of a menu.

The editor checks a sentence in about 250 milliseconds on average, where it took about 420, and a long sentence no longer takes longer. A corrected sentence is mostly the same sentence, so the model now reads your words as its guess and writes only where it would change them. Its answers are exactly what they were.

Grammar is checked when you pause, not when you reach a full stop, so a message you send without one is checked too. It looks 0.6 seconds after your last change, where it used to notice a pause one to two seconds late, and starts with the sentence you are in. Marks hold still while you type. A mark no longer disappears at a keystroke and comes back at the pause, and a typo marked as you finished the word no longer vanishes a second later.

One patch

  • 0.55.1Lodestar 0.55.1

    The editor marks only the grammar fixes it is sure of, the draft covers less of the screen, and the walk cue is off until you turn it on.

    The editor now weighs each grammar fix before it marks it. It compares your sentence with the fix against your sentence as written, and a fix that barely wins is not shown. On 666 dictated sentences, the grammar marks shown were right 82% of the time, where they were right 67% before, and every mark that made no sense was among those taken out. Spelling is checked as before, and Apple's model marks what it finds as before.

    The draft takes less of the screen. While you speak it holds three lines, not four. It is as wide as 66 characters of its own font, a comfortable reading width. One line of text takes one line of space, the bar at the bottom steps aside while you speak, and the panel sits closer to the edge of the screen.

    The walk cue is now off until you turn it on in Settings. Measured against your press record, it did not clearly change when you took a break.

    A mark you ignore or learn no longer comes back for a moment. When the editor was still reading your text as you pressed the key, that reading could show the mark again for up to a second.

0.54Minor · October 25, 2026

Lodestar 0.54.0

Health now keeps the whole of what it can measure, and the facts you give it about yourself are sealed with it.

About you has four rows: the year you were born, your sex as assigned at birth, the hand you write with, and whether you touch type. They live beside the health record, under its key, and go wherever it goes: exported with it, deleted with it. They are no longer in the config file. If yours held a year or a hand, this release moves them into the sealed record the first time it opens and takes them out of the file, and the config's history no longer keeps them, including what an earlier release wrote there. The Health setting now says the finger readings assume touch typing, because they do.

When you dictate, health now measures your voice as the draft closes: its pitch and how much it moves, how loud it is, how steady it is from one cycle to the next, how clear it is, where you paused, and how fast you spoke. Only those numbers are kept. The audio is dropped as it always was. Each measurement notes what kind of microphone heard you, never its name. `lodestar observations` shows a voice line once there is something to show.

The pointer record no longer throws motion away. A movement that ended in a click was always kept. Now so is one that came to rest without a click, and one made with a button held down. Each scroll keeps its own movement too, with the part your fingers made kept apart from the glide that followed.

Health also notes what kind of app you were in, such as a browser, a terminal or a chat, beside the app's name, so a record can be read the same way across people who use different apps for the same work.

27 patches

  • 0.54.27Lodestar 0.54.27

    A release that pastes a picture copied from a browser as the picture, starts an update's new build once instead of twice, and has Lodestar say what held it when it is slow to answer.

    A picture copied in a browser and pasted from Keep with a plain letter or ⌥ now pastes the picture. A browser puts the picture's web address on the clipboard ahead of the picture itself, and Keep used to paste only that address, so an app that takes pictures but not addresses pasted nothing, or a link. ⇧ still pastes everything that was copied, the address and the picture both.

    An update now starts its new build once. It used to start twice in about two seconds, once on its own and again when macOS took over running it, handing your keys from one to the other each time. When macOS is already the one running Lodestar, it now restarts it in place with the new build. In every other case the update starts as it did before.

    When Lodestar's main thread is a second late to answer, Lodestar now notes in its log what that thread was doing, up to four times while it stays late. It already noted that the thread was late but never why, so a stall can now be traced to its cause. Nothing is noted when the thread answers on time.

  • 0.54.26Lodestar 0.54.26

    A release that counts how many Macs use Lodestar each day, with no ID, and has its own switch to stop it.

    Once a day, after you first use Lodestar, it tells lodestar.vaccone.software that this Mac used it. It sends three things: the Lodestar version, the update channel, and roughly how long ago Lodestar was installed (that day, within a week, within a month, within three months, or longer). It sends no ID, no date and nothing about what you do, so no two days can be tied to the same Mac. The site adds one to that day's totals and does not keep the address the request came from.

    Only a deliberate use counts: a key struck under lode, a fix taken in the editor, or words landed by dictation. The count goes out at a random moment up to two hours later, so it never says when you started work, and it is sent at most once a day.

    It has its own switch, apart from updates, in Settings under General: Daily count. Turn it off and nothing is sent. A new Mac says so on the first launch window, and the privacy page lists it with everything else that leaves your Mac.

  • 0.54.25Lodestar 0.54.25

    A release that gives every update a record of its own on this Mac, so Lodestar says what happened to it once, and can say later who decided what and why.

    Each release Lodestar is offered now has a record that follows it from download to running, rolled back or refused, across launches and updates. The record is written beside the files Lodestar has always used to hand an update from one version to the next, and those files are kept exactly as they were, so an update to or from an earlier version works as it always has.

    "Lodestar has updated" is now said once. It used to be said again at every launch until Lodestar was ready, and twice when both halves of a handover lived long enough to say it. A rollback is said once too, even when the instance that found it closes before it can speak, and it is still said if the record cannot be reached.

    A release that failed to start here is still never offered again, and the record now says when it failed and why. If you go back to an older Lodestar by hand and the newer one is offered again, it is applied from the start and its arrival is said again. `lodestar diagnose` lists every release on this Mac with its state, since when, and who moved it last and why.

    The record is kept out of Time Machine with the rest of Lodestar's behavioral files, so restoring one Mac onto another never carries over a verdict about a release that never ran there.

  • 0.54.24Lodestar 0.54.24

    A release that moves Lodestar to Stoic 0.8 and holds all of its code to Stoic's own rules, so failures that used to pass in silence now leave a trace, and timings no longer move when the Mac's clock is set.

    Every time Lodestar measures how long something took, it now uses a clock nobody can set. It used to read the time of day, so a clock corrected by the network in the middle of a measurement could make a wait look seconds long or end it early. The times it writes down, in your records and its log, still come from the time of day as before.

    About a hundred places where Lodestar carried on after something failed now say so in its log, with what it was doing. A file that could not be written or removed, a folder that could not be made, a journal that would not close: each one used to vanish without a word.

    Start at login is steadier. When macOS cannot be asked whether Lodestar's login item is loaded, Lodestar now changes nothing, where it used to load it again on top of one that may have been running. A login item that could not be saved is no longer reloaded from the old one. The `lodestar` command in your terminal is only ever replaced when it points at a Lodestar app, so another tool's command of the same name is left alone, and uninstalling no longer removes it either. The command is replaced in one step, so there is never a moment without it.

    A config that cannot be saved now says so in Lodestar's words, and the details go to the log. A model download the server refuses within its first few seconds now stays said as refused in Settings, where a moment later it turned into "waiting for a connection that is not metered" and stayed that way.

    Timers that were cancelled at the last moment no longer go off. A card that should have closed when an app's window arrived could stay on screen. The check that restarts a microphone that has gone deaf now counts only time the Mac was awake, so opening the lid mid-draft no longer sets it off before the microphone has had a chance to speak.

    Opening the clipboard history no longer reads two of its counters while they are being written. Dictation now keeps a bounded amount of audio for a recognizer that falls far behind, and says so in the log when it lets some go.

    Underneath, every format Lodestar keeps on disk that an earlier version may have to read, after an update is rolled back, is now tested against samples of what each release wrote: the queued feedback notes, the config file and Lodestar's state. A change that would leave an older Lodestar unable to read your queued notes now fails before it ships.

  • 0.54.23Lodestar 0.54.23

    A release that makes dictation start more reliably, takes several gigabytes off Lodestar's launch, and puts more of its plumbing on tested ground.

    Dictation no longer blames the recognizer when the Mac's audio system stops answering. The draft now says so in its own words and stops asking on a timer, and pressing lode . asks again. A headset already in its call mode is no longer waited on for a change that is not coming, which used to cost several seconds on every failed start. A newer question to the language model now takes the place of an older one it covers, where it used to wait behind it.

    Lodestar's launch used several gigabytes of memory for a few minutes while it read its own records, and did so again every half hour. It now reads only what each job needs, and that cost is a small fraction of what it was.

    `lodestar observations` now counts a mark as standing only while it was drawn, counts a mark you came back to once, and says whether marks left standing were sent with the text or left behind. The lines for each app now say how many of those marks were spelling and how many were grammar.

    The editor's language and model settings now always reach it in the order you set them. Two changes made close together could arrive the wrong way round and leave the older one in force.

    Underneath, the two helpers that run the language models and read the clipboard now use Stoic 0.5's XPC library in place of code written for them. The update check refuses an oversized answer and a redirect to an insecure address. Only one Lodestar running is now proven by a lock, so a number left behind by a crash can never lead to another app being asked to quit. A copied file on a volume that has stopped answering no longer ties up Lodestar while it waits.

  • 0.54.22Lodestar 0.54.22

    A release that makes Lodestar steadier: its language models now run apart from it, updates no longer stall, and copies that used to slip past Keep are kept.

    The models behind the editor and dictation now run in a separate part of Lodestar that macOS manages, the way Apple has apps keep heavy work apart from themselves. A model that stops answering is now ended and started fresh at the next sentence, where it used to leave grammar silent until Lodestar restarted. When a model is let go, its memory goes with it at once, and quitting can no longer crash inside the model's code.

    Updates no longer pause for five seconds while the old Lodestar finishes. Its records' upkeep now waits until it has settled and is the copy that stays, so it never holds up a quit.

    A copy caught at the moment its app had cleared the clipboard but not yet written it, or before its app had handed over its contents, is now read again a moment later instead of being missed. A copy made while the screen was locked, such as one from your phone, is now kept once you unlock. Every copy now leaves a line in Lodestar's log saying whether it was kept or refused and which app it came from, never what it said, so a copy that does not reach Keep can be traced.

  • 0.54.21Lodestar 0.54.21

    A release that moves Lodestar's clipboard reader into a part of the app macOS runs on its own.

    Each copy is now read by a small service built into Lodestar, the way Apple has apps keep work they cannot wait on apart from themselves. macOS starts it when a copy needs reading and stops it when it is idle. A copy that is slow to read, such as a file from the Finder or something copied on another device, still waits there and never holds up your keys, and a read that stops answering now ends the service so the next copy starts a fresh one.

  • 0.54.20Lodestar 0.54.20

    A release of fixes for things that could lose your work, and a clipboard that no longer holds up the keyboard.

    Lodestar now reads each copy in a small process of its own. A copy that is slow to read, such as a file from the Finder or something copied on another device, used to keep Lodestar waiting for up to three seconds, and your keys waited with it. Now only the reader waits.

    Pasting a card from Keep whose saved copy will not open now leaves your clipboard as it was. It used to empty the clipboard first and then say the card could not be read.

    The letters the click door shows now stay on the targets they were drawn on. On a busy page a letter could move to another target while you were reading it, so pressing it clicked something else.

    In the draft, `lode .` or `lode ⇧.` pressed while ⏎ is still landing no longer turns the microphone on with nothing on screen, and no longer drops your last words. ⏎ now lands words still shown in grey between two recordings, as esc would keep them. Quitting within a second of esc now keeps the draft on the clipboard, where its text used to be lost.

    If an update ever has to be rolled back, the previous version is put back before the failed one is removed, so an app is always there to start. A rollback interrupted halfway used to leave half an app, or none.

  • 0.54.19A release of foundations: Lodestar now runs on Stoic 0.4.2

    A model or update download that sends more than its server declared now stops at once, where it used to keep writing into the file.

    A config number that must be whole, has a fraction and is out of range, such as `"max-size-mb": 99999.5`, now falls back to its default and says so, where it used to become the nearest bound.

    A mark you fix or change while the editor is reading the field is now recorded for what you did, where it could be counted as changed even when you had fixed it, and with too long a time standing.

  • 0.54.18Lodestar 0.54.18

    A release of fixes, ten of them, found by going through how Lodestar keeps track of what it is in the middle of.

    Going straight from one lens to another, such as `lode /` with hints up, could leave the new one dead, with nothing on screen and your keys swallowed until esc. It now starts whole. Opening Keep with ⇧⌘V from scroll, select, hints or a chain now ends that mode first, where its pill, overlay or guide used to stay behind after Keep closed. What you type while the editor's lens lands a fix now reaches the app even if you press esc or a lode gesture before it lands.

    A memory warning that arrives while the editor's model is loading now lets the weights go when the load ends, where they used to stay for up to twenty minutes. While a warning keeps the model away, nothing brings it back: starting dictation and the draft's own editor used to reload it. A question asked just after you change the editor's model is now answered by the model you chose.

    Words from a crashed draft that could not be unsealed at launch are now kept and given back once the keychain opens. Closing any draft used to delete them. A keychain slow to answer at launch can no longer replace your coach history with only the last few seconds of events, and events from the first moments after launch now stay in that history.

    In Settings, pressing ⏎ after a search landing and a click elsewhere could flip an unrelated setting or crash Lodestar. One `lode ←` could undo two gestures when a chord's letter had changed nothing. Closing a draft and opening the next while a Bluetooth headset was still waking could leave the new draft deaf. A rollback to the previous version now always says so, where it could go unannounced.

  • 0.54.17Lodestar 0.54.17

    Your health record can now be read for analysis. `lodestar health` prints it as JSON lines, one row each, at the grain you ask for: a summary over any dates, days, weeks or months, or the record's own events (quarter hour pulses, 90 second windows, bouts of typing, blind spans, dictation and clicks). Nothing is written to disk, and what you do with the lines is yours, whether that is a script, a local model or Claude. The keystroke rows are held back unless you add `--include-presses`, because hand, finger and the spaces between words come close to a transcript of what you typed. `--since` and `--until` choose the days.

    Older data comes out whole and says how it was measured. Every row names the clock that timed a hold and what a keyboard list meant at the time, and a period is split only where a number's meaning changed (at 0.34.0 and 0.39.2), so no row averages across that change. A measure Lodestar was not yet recording is written as null, never as zero. `lodestar health schema` explains every field.

    Behind the scenes, the test suite no longer takes your keyboard focus while it runs, and it can run in a virtual Mac of its own so it never needs your screen at all.

  • 0.54.16Lodestar 0.54.16

    Lodestar now lets go of far more memory when your Mac runs short. On a memory warning it used to release the editor's model, about 2.7 GB, and keep the 20 GB language model that tidies a draft, which waited out its five minute idle timer. That model now goes on a warning too, right away, or when the draft closes if you are dictating. The next draft loads it again, as it already did after any five minute gap. The model that hears you stays until memory is critical.

    The editor's model also stops coming straight back. On one evening it was reloaded within fifteen seconds of five warnings out of seven, into the same shortage that had just sent it away. It now waits at least five minutes after a warning, and longer if the system still says memory is short, up to half an hour. Spelling and the rules keep working during that time, and the grammar check picks up the sentences that waited.

    The memory MLX keeps for reuse now has a limit of 64 MB. It saves about a gigabyte while dictating, and in testing nothing got slower and the words heard did not change.

    Finally, the log now records memory every five minutes and whenever the level changes: what Lodestar is using, how short the system says memory is, and the largest applications running. If your Mac freezes and has to be forced off, which leaves no report behind, this is the record of what was in memory at the time. It stays in the local log on your Mac, and nothing here sends it anywhere.

  • 0.54.15Lodestar 0.54.15

    A video in the browser now steps aside while the draft listens. On a Bluetooth headset, opening the microphone drops the sound to telephone quality, so the draft has paused Music and Spotify since August and picked them up again afterward. It could not do the same for YouTube, because a browser cannot be asked what it is playing. A browser does say which tabs are making sound, in the label behind the speaker icon on the tab, so the draft now reads that and presses the keyboard's play and pause key. When the draft ends it presses the key again, once the headset is back to full quality. If you started the video yourself in the meantime, it leaves the video alone.

    That key is a toggle, and it goes to whichever app last held the media controls, so every press is checked. If the press started Music, which happens when Music started playing after the video did, Music is paused again within about a second, and the video keeps playing. If the press started a video you had paused just before the draft, because the speaker icon stays up for about three seconds after the sound stops, a second press stops it about four seconds later. In neither case does anything restart when the draft ends.

    This works in Brave and Chrome when the browser's language is English. It was measured on Brave, and other browsers are left alone, as they were before. As with Music, it only happens when the headset is both your microphone and your output. On laptop speakers or wired headphones the sound does not degrade, so nothing is paused.

  • 0.54.14Lodestar 0.54.14

    Lodestar holds its place when the Mac is busy. The way it starts at login never told macOS what kind of program it is, so macOS ran it as a background job: throttled, with every thread below the priority of an ordinary program, including the one that hears your keys. It now starts as an interactive program, and that thread goes ahead of ordinary work. On a Mac under heavy load, a fixed piece of work on a test program started the same way took 0.9 s where it had taken 6.1 s. Lodestar always came back after a crash, but on a badly overloaded Mac the restart itself could starve, which once left the keys dead for 87 seconds. This should shorten that, though it has not yet been measured under that much load.

    Lodestar restarts one extra time right after this update, so the change takes effect at once and not at your next login.

    An install can no longer pass for an uninstall. When Lodestar's login item found the app missing, it took that to mean the app had gone to the Trash and removed itself, so a crash at the moment an install was replacing the app could leave Lodestar with no login item. It now waits two minutes for the app to appear, and starts it as soon as it does. Dragging the app to the Trash still cleans up after itself, only a little later. Lodestar's own updater now exchanges the old and new builds in one step, so there is no moment with no app in place.

    Moving the app to another Applications folder no longer costs the login item. The login item started from the old location, found nothing there, and removed itself. It now starts from the new one.

    The log names each step of launch. A launch that ran slowly used to leave no trace of which step held it. Now a slow step is written down as it ends, a finished launch writes every step on one line, and if the app gives up on a stalled launch, the log says which step it was in.

  • 0.54.13Lodestar 0.54.13

    Dictation gets the better ear far more often. The second ear that hears each phrase again used to let go of its memory five minutes after the draft closed, so more than a third of drafts started without it, and it then took ten seconds to load because it loaded at the same moment as the much larger model that writes what you meant. Now it stays for thirty minutes, loads first, and leaves only when the Mac runs critically short of memory. When it does finish loading partway through a draft, it hears again the words you said while it was loading, from the audio the draft still holds, instead of skipping them.

    ⏎ lands sooner. It used to wait for every hearing the ear had queued, most of them already out of date, and for a rewrite that rarely finished in time. Now the ear runs one hearing at a time with only the newest waiting, and ⏎ waits for a rewrite only when its own record says it can finish within the wait. While it does wait, the foot says "finishing", and a second ⏎ lands at once with what is there.

    Fewer words go missing. A final for words you had just edited used to be dropped whole, taking with it anything you said after them. Now your edit stands and the rest of what you said lands after it. ⏎ waits for the recognizer's last results to arrive rather than landing on the first one. Esc still closes at once, but the clipboard now waits a moment for the last words you said. A draft cut off by a crash, a force quit or a power loss comes back at the next launch as a card in the clipboard history, without replacing what you copied last.

    ⏎ no longer pastes into thin air. When the app in front has nothing focused that can take text, such as Finder with a folder selected, the draft copies the text instead, says so, and plays no landing sound. Terminals, browsers and anything uncertain paste as before.

    Editing works the way a Mac field does. A dictated paragraph is one long line, so ⌘⌫ used to delete the whole paragraph and ↑ jumped to its first character. Now ↑, ↓, ⌘←, ⌘→, ⌃A, ⌃E, ⌃N, ⌃P and ⌘⌫ follow the lines you see, in both editing styles. ⌘Z after you edit what you just said takes back the edit and leaves the sentence. ⌥ types what it types everywhere else, including é, the em dash and curly quotes, with dead keys. A word after a closing quote no longer runs into it.

    The microphone is more patient with Bluetooth headsets. A headset switching to its calling mode changes its sample rate, and starting the microphone during that switch failed or produced an engine that heard nothing, which cost several seconds before the headset took over from the Mac's own microphone. Now the draft waits for the rate to settle before it starts again. If the microphone was refused permission, lode . opens Privacy & Security at Microphone, and a microphone that is refused, failed or hearing nothing is reported on the foot before any other note.

    A pause after "her" or "in" no longer swallows the period when the next sentence starts with "she" or "but", and fewer ordinary phrases are sent to the model that writes what you meant, so it is free sooner for the phrases that need it.

    The editor marks less, and what it marks is worth the look. It used to underline a word whenever the Mac's spell checker would have fixed its casing or its apostrophe, so "jeff", "github" and "dont" each wore a line, and a lowercase name drew a stranger as its fix, "priya" offered "prayer". Your casing and your apostrophes are yours, so those words are left alone now, as are #channels, /commands, :shortcodes: and chat's own words. A word the spell checker is wrong about by more than a slip or two is no longer offered a fix it was only guessing at. Every common typo still marks.

    The grammar model is held to the same rule. Read over 265 passages of the maker's own writing, more than a fifth of its marks were style rather than mistakes: a contraction written out, "it's" to "it is", a digit spelled as a word, and commas before "and", "because" or "when", or after a lone "However". Those are no longer offered, and the same passages now draw 76 marks where they drew 98. A comma that splits what belongs together, "about, the plan" or "your, notes", still is.

    Launchers, search boxes and the browser's address bar are no longer read at all. In its first weeks the editor put 368 marks in Raycast and not one was fixed, because a query is not writing.

    Keep as written now lasts while you write. Leaving a word alone with ⇧ and its letter quieted it only until your next keystroke in the same sentence, which is exactly where the mark nearest the caret always is. Now it stays quiet for as long as the words before it stand.

    A fix in Slack, Brave, Claude and the other Chromium apps lands at once, without the moment it spent waiting on a write those apps ignore, and keys you strike while it lands are typed after it rather than over the word. A second letter in the lens right after a fix that changed the length of the text now lands on the right words. And a card no longer opens for a pointer that is only passing over the text. It waits for the pointer to rest.

    The grammar model no longer stops for good. While you dictated, the editor's model and the ear that settles your speech used the GPU at the same moment and slowed each other, until the editor gave up on every sentence and stayed that way, once for fifty minutes, until Lodestar restarted. Now they take turns, a sentence that could not be asked is asked again a little later, a model that stops answering is loaded afresh, and if grammar is paused for a while the editor says so once, since a missing mark would otherwise look like a clean sentence.

    The record of what the editor does is honest now. It counted a mark again each time the text before it moved and each time a field blinked out for a moment, and it counted every typo you fixed yourself as a mark ignored, which put its fix rate at 5% and said nothing true. Now each mark that stood for a second ends in one outcome, fixed by the editor, fixed by you, edited into something else, kept, or left standing when the message was sent, and `lodestar observations` shows them that way. The marks also stop blinking when an app rebuilds its field behind the same text.

  • 0.54.12Lodestar 0.54.12

    The draft can be pointed at. Until now its words answered only the keys, so fixing the third word of a sentence meant walking the cursor back to it. Now a click puts the caret where you clicked, on the nearer side of the letter, and a drag selects. A double click takes a word, a triple click takes a line, and dragging after either grows the selection by whole words or whole lines. Shift and a click extends whatever is selected. A click in the margin beside a line counts too, the way it does in any Mac field.

    In the Vim style the mouse is vim's own. A click puts the cursor on the letter and drops a command you had half typed, and a drag, a double click or a triple click is visual mode, so what you dragged is what d, c, y and your voice act on next. Speak over a dragged selection and your words take its place.

    None of it takes the draft away from the app underneath. A click never makes the draft the active window, so that app keeps its cursor and its selection, and ⏎ still lands there. Words still being heard become text where they stand the moment you press, so what you pointed at is what is there. A drag that runs past the glass keeps selecting, and holding it above or below the text scrolls a line at a time.

    The four lines the draft holds now stay still while the cursor moves inside them, by the pointer or the arrows, and scroll only when the cursor leaves them. Moving the caret ends what ⌘Z takes back, as in any Mac field: type, click somewhere else, type again, and ⌘Z undoes only the second part. And ⌘⌫ while you are dictating now takes the words still being heard along with the line, as ⌥⌫ already took them with the word.

  • 0.54.11Lodestar 0.54.11

    Lodestar puts a window where you are, and "where you are" is the display under the pointer. With two displays that broke the moment you crossed between them with the keyboard. Summon a window that lives on the other display, or throw the one in front there with lode ], and you were working on that screen while the pointer stayed on the first, so the next summon, the launcher and Keep all opened on the screen you had just left.

    Now the pointer comes with you. Whenever Lodestar brings a window forward on a display the pointer is not on, by a summon, a throw, an undo or a breath, the pointer moves to the middle of that window. On one display it never moves, because the pointer there is yours.

    A breath now remembers each display. Every window in it keeps the monitor it stood on, known by the monitor itself rather than by where it sat, and every display keeps its own direction, so a breath across a laptop and a monitor comes back on the right screens, side by side on one and stacked on the other, even after the monitors are rearranged. A window whose monitor is not attached joins the display you are on. Breaths saved before this release come back as they always did.

    A tall display stacks. A monitor turned on end now divides top to bottom the first time windows share it, instead of into columns too narrow to read, and a display turned on its side follows, unless you had already flipped it the other way.

  • 0.54.10Lodestar 0.54.10

    The Secure Input notice in 0.54.9 never appeared, and this release makes it work. When an app holds Secure Input, macOS names that app truly only while it is in front. Once it goes to the back, macOS names whatever app came forward instead, so Lodestar always found the holder in front, took it for someone typing a password, and stayed quiet.

    Lodestar now remembers the app that turned Secure Input on, at the moment it began, when that app is still the one in front, and keeps it until Secure Input ends. It looks twice a second so that moment is not missed. When the holder has stayed at the back for two seconds, the lode key appears, faded, beside a line naming it, and a click brings it forward. If Secure Input was already on when Lodestar started, or began behind a locked screen, nobody is named until it has been off once, since Lodestar cannot know who turned it on.

    Underneath, the core of Lodestar is now built in Swift 6 mode, where a data race is a compile error rather than a rare crash. The log, the event log, the key tables, the control socket, the window model and the stores each keep what several threads share behind a lock of its own. Nothing you see changes. The tests around it were rebuilt too: every window they open stands on a display far from the real ones, and a test that leaves a setting changed fails by name.

  • 0.54.9Lodestar 0.54.9

    When an app holds Secure Input, macOS lets no key reach Lodestar, and every lode gesture goes dead without a word. That is right while you type a password. It is wrong when the app keeps the hold after you have left it, which Chromium browsers do when a password field keeps its focus in a window at the back. Until now the only sign was a keyboard that had stopped working.

    Lodestar now says so. When Secure Input stays on for a few seconds in an app that is not in front, a small surface appears where the guide does: the lode key, drawn faded because no press of it can arrive, beside a line naming the app that is holding your keys. Click it and that app comes forward, so you can leave its password field or finish the prompt. When Secure Input ends, the key lights and the line says your keys are back, then it goes. Nothing is said while the holder is in front or the screen is locked, and the record still notes only that Secure Input was on, never which app held it.

  • 0.54.8Lodestar 0.54.8

    A mouse wheel can turn the other way again, and this time Lodestar does it itself. macOS has one setting for scroll direction, shared by the trackpad and every mouse, so a page that follows your fingers on glass runs backwards under a wheel. Settings now has a place called Input, where Keys used to be, and its last group is Mice. Turn a mouse's wheel while the place is open and the mouse appears there by name, its row lit while the wheel moves. Switch it on and that wheel scrolls the other way, from the very first notch. The trackpad is never listed and never touched.

    Each scroll is turned only when something vouches for where it came from. Either the mouse's own wheel report arrived a moment before it, which needs Input Monitoring, or an app such as Logi Options+ posted it, in which case it is listed as Mice through that app. A scroll nobody vouches for passes exactly as macOS sent it, so the worst a mistake can do is leave a wheel as it was. A mouse you switch on is kept by name in the config. One you leave off is forgotten when Lodestar quits.

  • 0.54.7Lodestar 0.54.7

    The clipboard history keeps its state on one thread, and now it says so. Reading a card's files, checking whether they are still where they were, and deleting from disk all happen on other threads, and every answer comes back to the main thread before it touches what the strip draws from. That was always how it worked, but nothing held the code to it. The places where those answers land, and the calls that delete cards or ask after their files, now stop at once if they are ever reached from anywhere else, so a mistake would show up in the tests long before it could quietly corrupt the history.

    Nothing you see changes. A suspected race in how the strip remembers which files are still present was looked into and turned out not to exist. This release makes sure it cannot appear later.

  • 0.54.6Lodestar 0.54.6

    The pictures in Settings and on the first-launch doors are cameos now. Each one is the old clay model of its door or place, turned to face you, pressed into a low relief and lit by one light from above, the way Ceramic lights everything. The letters are inlaid in ink and the orange is a glaze, so a picture reads as something made rather than something rendered, and it sits on its slab without a shadow of its own.

    Hints wear capitals. In select, the click door and the aim band, a lowercase letter searches and a hint is picked with Shift, so the hint now shows the key you actually press. An I and an l no longer look alike, and a hand that reached for the lowercase letter out of habit has a capital in front of it to correct it.

    A search field holds only its words. The / that sat inside the Settings search and the clip bars is gone, along with the = in Bring, and the words start where the field starts. Where / is still shown as a key, it is drawn at the letters' size instead of as a speck.

    Mouse scrolling is retired. A mouse's own app or a scrolling utility turns the wheel better than Lodestar did, and scroll mode keeps the direction fix from 0.54.2.

    Lodestar freezes less when the Mac is short of memory. The editor asked macOS every second which app was in front, and the answer came from another process on the thread that draws everything and reads your keys. Under memory pressure one answer could take a second or more. Lodestar now hears when the app in front changes and remembers it, so that thread no longer waits.

  • 0.54.5Lodestar 0.54.5

    The draft no longer asks you to know Vim. It has an editing style now, in Speak, under Microphone, and a new Mac starts on Standard: the draft edits the way every Mac text field does. ⇧ and the arrows select, with ⌥ by the word and ⌘ to the line's ends, ⌘A takes everything, ⌘C, ⌘X, ⌘V and ⌘Z do what they always do, and esc closes the draft with the text kept in the clipboard. Escape used to step into Vim's normal mode, where a person who had pressed it to cancel found letters editing their text. The text is set in the system's sans, the way the rest of Lodestar is.

    A selection can be spoken over in Standard too. Select a phrase, say it again, and the new words take its place in one step, so ⌘Z brings the old ones back. While a selection waits for your voice, the foot says so, and a selection longer than the four lines the draft holds opens the whole text so you can see what it will take.

    Vim is still there, whole, for anyone who chooses it, and a Mac that ran Lodestar before this version keeps it without being asked. fn ⌫ deletes forward in the draft, and ⌃d, ⌃f, ⌃b, ⌃n and ⌃p work the way they do in any Mac field. Before, fn ⌫ and the Home, End and page keys slipped past an open draft or strip into the app underneath and acted there.

  • 0.54.4Lodestar 0.54.4

    The window that opens when you open the disk image has caught up with the rest of Lodestar. It was a night sky drawn before Ceramic, in spaced capitals, and it still said Lodestar runs on macOS 14. It is now the homepage's wall: a few of Lodestar's doors standing quietly around one light bar that holds the app and the place it goes. Applications sits sunk into the bar, the way every place you put something does in Lodestar, and one orange arrow points the way.

  • 0.54.3Lodestar 0.54.3

    The draft no longer gives up on the microphone. When it would not start, the draft said so and waited, and the only way to ask again was to close it and open it again. Now it asks again on its own, after a second, then two, then four, then every five seconds for as long as the draft is open, and the line under it says it is trying again. `lode .` asks at once. Everything already in the draft stays where it is, including the words the recognizer was still settling when the microphone went. If you have muted the draft, it waits for you.

    A headset that will not start no longer ends a take. With the lid open, the Mac's own microphone hears you while a Bluetooth headset wakes. When the headset failed to start, the draft threw that away along with what you were saying. The Mac's microphone now carries the rest of the take, and a headset that comes up late takes over the way a slow one always has. A microphone that stops partway through a take is asked for again too, instead of leaving the draft listening to nothing.

  • 0.54.2Lodestar 0.54.2

    Scroll mode goes the way its keys say again. j and d had started running up the page and k and u down it, and G and gg had swapped ends in every window that does not hand Lodestar its scrollbar, which is most of them. Scroll mode had been asking the Mac which way you scroll, and the Mac's answer never applies to a scroll an app makes. It only seemed to, because Scroll Reverser used to turn Lodestar's scrolling over along with your mouse's, and its new version stopped. Every key in scroll mode now goes one way on every Mac, and each one is checked before a release can ship.

    A mouse can now scroll apart from the trackpad. macOS keeps one direction for both, which is why Scroll Reverser exists. Mouse scrolling, in General, takes System, Natural or Standard. System leaves things as the Mac has them. The other two turn only the mouse wheel, so the trackpad keeps the Mac's own setting. A mouse app such as Logi Options+ counts as the mouse. A Magic Mouse counts as a trackpad, since it scrolls like one. If Scroll Reverser is still running, Settings says so, because the two together would turn the wheel twice. The health record keeps the direction your fingers moved, before any of this.

  • 0.54.1Lodestar 0.54.1

    Every menu in Settings chooses again. Since 0.53, a click on a choice landed on the line's drawing and went no further, so nothing in a menu could be changed: not your sex, not the lode key, not the dictation model. A click anywhere on the line now chooses it, and so does return. Each menu in every place is now clicked through, choice by choice, before a release can ship.

    Exact keyboard is no longer a setting. While health is on, each press is charged to the keyboard that sent it wherever macOS allows, which needs Input Monitoring. Lodestar asks for it once, and Settings shows it beside the other permissions under Health. Without it, presses are charged as they were before.

0.53Minor · October 24, 2026

Lodestar 0.53.0

Lodestar has a new look: matte ceramic. Every surface is one opaque pane lit from above, what you can press stands on a visible side, and a place you type into sinks. The glass is gone, and with it the tint that drifted with whatever lay behind it.

There is one colour, International Orange, set for each look: deeper by day, brighter at night, so it reads the same on both. The accent setting is gone. A config that still sets it loads without complaint, and the key is never written back.

The type is one family on four sizes and three weights, one weight heavier at night. Mono stays only where vim is, in the draft and the editor's lens.

Eye comfort is on by default. Through the evening every surface dims toward the night, a little more at bedtime, and never takes on a tint; the Mac still decides light or dark. The pill and the meeting's chip recede after twenty seconds alone and come back at a hover or a key. It is one switch, in Sound and display.

Every key is drawn one way, as you type it. A sequence is one key per keystroke, a double tap is the key and ×2, and a comma or a period sits low on its key as it does on a real keycap. Keys are centred as whole objects, so they no longer look low beside their words.

The chosen row, card or tile is a slab in the other look's colours, and only the key that acts on it is lit. In Keep, the whole chosen card is the slab.

Keep no longer flashes Shift's labels as it opens. A modifier still down from ⇧⌘V does not count, neither on the cards nor for what ⏎ does, until you let go of it and press it again.

A field has one caret and one selection everywhere. The field you are typing in shows it with a deeper edge, not a ring.

Lists keep one rhythm: rows, settings, lines and legends each have one height and one way of laying out. A setting that cannot act is drawn quiet, its value still showing, instead of faded. A setting's letter is a key, and the letters follow the page's reading order, so some have moved. Both Model menus now read just Automatic.

The coach's offer shows its whole record, wrapping onto a second line when it needs one, and says how often you do a thing in plain words: "6 times more than chance".

The meeting's chip has three moods. Before the meeting it is plain. From the last minute to 90 seconds in, its stub is orange. After that it steps back: the stub plain, "MIN AGO", the whole chip receded, and `lode` `lode` no longer lit, though it still joins. Typing does not wake it, since you may be typing in the meeting; a hover does.

Nothing slides or fades now except the voice meter and a switch's knob. A change of state happens at once.

0.52Minor · October 20, 2026

Lodestar 0.52.0

Keep now holds files as files: a copy from the Finder becomes a card with a real picture of each file, pastes as the files themselves, follows them when they move, and leaves when they are gone.

A copy made in the Finder becomes a card of its own kind. One file shows its picture (a PDF's first page, a film's poster frame, an image itself, the Finder's icon for anything else) with its name, its folder and one line more: pages, pixels or minutes. Several files stand as a stack of pictures with their count beside the key, and their names where the card has room. The pictures are made when you copy, so a card keeps its look whatever happens to the files.

The letter pastes exactly what the Finder's own copy would, so every app takes it the way it already knows: the Finder copies the files in, Mail and Slack attach them, a terminal does what it does with a file. Before this, a card of files pasted only the file's name as text, and the Finder made a text clipping of it. `⌃` and the letter pastes where the files are as text, each path whole and in single quotes, ready for a shell. While `⌃` is held, the card shows those places.

`⌘` and the letter open what a file can do. `F` shows the files in the Finder, `O` opens one file, and `E` views one file large: a picture across the display, a PDF with its pages stacked and scrolling, anything else as the Mac previews it. With the Finder in front, `M` moves the files into the folder it shows, as the Finder's own Move Item Here, so the Finder asks about a name that is already there and `⌘Z` undoes it.

A card finds its files by bookmark, so it follows a file you move or rename, and keeps finding it after a restart. A file in the Trash does not paste (the Finder refuses it), and the pill says it is in the Trash. A card whose files are all in the Trash or gone leaves Keep, and a group of files loses the ones that are gone and keeps its place. A keepsake is never changed, and a file on a disk that is not plugged in keeps its card. Nothing leaves while Keep is open. The first look over your cards comes a few minutes after this version starts, so cards of files you deleted long ago may leave then.

The search finds a card of files by its name and extension, its folder, its kind (pdf, photo, video, folder), the site a download came from and a PDF's title, from what was kept when you copied. It never reads a file.

With `select.copy-on-complete` on, Escape after the first anchor now copies that word, as `⌘C` does. With it off, Escape only leaves, as before.

A copy from select is trimmed at its ends however it is made. Before, when the app made the copy itself, its rich form could keep a space or a blank line at the start, and a rich editor pasted it. The highlight is trimmed the same way, so it never runs over the spaces at a span's ends.

Click hints narrow more quietly. As you type a hint, the letters you have typed dim on its key, the hints those letters cannot complete are gone, and a letter no hint continues brings them all back.

The lit `⏎` keys follow your accent. Switching to System no longer leaves them in International Orange beside letters that changed.

0.51Minor · October 18, 2026

Lodestar 0.51.0

Lodestar now keeps your saved addresses encrypted on disk, removes its keys when you purge, and reads its config through one typed description.

Lodestar's state file (your breaths with their window titles and URLs, the windows it has parked, how often you use each app, and how far the walk has got) is now sealed at rest under a key in your login keychain, like the clipboard history and the health record. What is already on disk is encrypted at the first launch, checked, and only then is the plain copy removed. If the keychain cannot be opened, Lodestar runs without your saved addresses for that launch, never writes them in the clear, and loads them when the keychain answers, keeping what you changed in the meantime. If the key is gone, the unreadable file is moved aside, never deleted, and you are told. `lodestar diagnose` now says whether the state is sealed and opens.

`lodestar uninstall --purge` now also deletes Lodestar's keys from your login keychain, after the data they opened. `--dry-run` lists the step, a plain uninstall keeps the keys because the data it keeps cannot be read without them, and a key the keychain would not delete is named instead of passed over.

The config file now has one description, and everything about it comes from that: the defaults, what each option accepts, the words that explain it, the schema your editor reads, the old spellings it still understands, and the order a save writes. `lodestar.json` and `lodestar-schema.json` keep their names and their place, and a file written by an earlier version is written back byte for byte.

Problems with your config are clearer and come in the order of the file. Each one names the option as you would type it in `lodestar config get`, says what is wrong, and offers the nearest right answer, for a value as well as a key: `lode.trigger: "right-comand" is not allowed, expected one of "right-command", "left-command" (did you mean 'right-command'?)`. A misspelt gesture name is caught the same way. A number out of range says what it became (`scroll.speed: 99999 is out of range, expected a number between 200 and 4000; clamped to 4000`), and the next save writes the number it became. One bad entry in a table, a route or an app you never record clips from, is dropped with a message that names it, and the entries beside it still apply. `lodestar check --json` still gives one string per problem.

A few things that used to be forgiven are now said. A decimal where a whole number belongs (`lead-minutes`, a size in megabytes) is a problem and the default stands, where it was quietly cut. A model or language has to be spelled as listed (`"Full"` was read as `full`, with a complaint, and is now read as the default, with the same complaint). A `null` for a section or table is still read as nothing. In a file with keys Lodestar does not know, those keys now follow the known ones when it saves.

0.50Minor · October 18, 2026

Lodestar 0.50.0

Lodestar now keeps your clipboard history and health record encrypted on disk, its clipboard is faster, and feedback is never lost.

Your clipboard history, your keystroke and pointer health record, and the logbook are now sealed at rest with keys kept in your login keychain. What is already on disk is encrypted in the background on first launch, each file checked before the old copy is removed. Deleting a clip now really deletes it: within seconds its key is gone, so nothing on the disk can be read back. If the keychain cannot be opened, Lodestar pauses that history rather than touching it, and never deletes anything on its own. `lodestar health export <folder>` writes your health record out in the old plain formats for your own scripts. GUIDE.md says what is sealed, what is not, and what that does and does not protect against.

The clipboard is faster. A large copy costs the main thread milliseconds instead of most of a second, and loading the history no longer holds up launch. Copying something you copied before just brings its card back to the front. Thumbnails are decoded off the main thread.

Feedback is never lost. A note is saved before it is sent, and if you are offline Lodestar keeps trying on its own, even after a quit. The site sends each note once, however often it arrives.

The config file is read and written by Stoic's settings layer. A mistake in `lodestar.json` is now reported with its line and column, and Lodestar keeps your last working config instead of falling back to the defaults. A key written twice is read with the last value and flagged, and comments are refused before a rewrite could lose them.

Editor models and updates download through Stoic. Each file is checked as it streams, a download resumes where it stopped, and an update is checked against the digest GitHub publishes, with no three-minute cap on a slow connection.

0.49Minor · October 15, 2026

Lodestar 0.49.0

Lodestar now needs macOS 27, and in return it is harder to break: what it writes survives a crash, and what it waits for has an end.

Lodestar is now built on Stoic, our open-source library for the parts of an app that fail rarely and badly. Settings, history, the dictation journal and saved state are written so that a crash or a full disk leaves the old file or the new one, never half of each, and a write that fails is logged instead of lost. A `lodestar config set` from the terminal and a change in Settings can no longer undo each other. A second copy of Lodestar no longer takes the first one's control socket.

The editor's model download retries with a growing, slightly random wait and gives up on an address that does not exist instead of asking for it forever, and the finished model is swapped into place in one step. The updater no longer waits forever on a stuck signature check. The watchdog that restarts a frozen Lodestar no longer mistakes the Mac's own sleep for a freeze, and if Lodestar keeps failing to start, the watchdog stops restarting it and says so in the log.

Macs on macOS 26 or earlier stay on 0.48.1: the updater sees that this build needs macOS 27, says so once, and does not ask again.

One patch

  • 0.49.1Lodestar 0.49.1

    Lodestar checks for updates more patiently, keeps its clipboard index private to you, and writes down what its foundations notice.

    Lodestar now runs on Stoic 0.3. The update check is a declared operation: on its own schedule it waits out a busy or briefly unreachable server instead of failing on the first try, and when you choose Check for Updates it answers within half a minute. A refused certificate or a malformed address is no longer asked for again as if the network had merely dropped.

    The clipboard index, and a config file Lodestar creates, are readable only by you. A file that was written but whose final disk sync failed is treated as written, with a warning, so a downloaded editor model that is already in place is never reported as failed and fetched again.

    Warnings from Stoic itself (a retry given up on, a write that could not be confirmed, a launch that could not be recorded) now appear in Lodestar's log, with private details redacted, so `lodestar diagnose` shows them.

    On a clipboard card too narrow for every clock, UTC now gives way before a time zone you kept, instead of pushing it off the card in the hours when UTC is already on the next day.

0.48Minor · October 10, 2026

Lodestar 0.48.0

Lodestar now comes in two channels, and the one most Macs follow waits until a build has proven itself.

Every new build goes first to Preview. It reaches Stable on its own after it has been out a while: a new version after seven days, a fix after three, and never a build less than a day old. A fix arriving during the wait never delays it, because when the newest is too young the one before it goes instead. Stable is where every Mac starts. Settings has the choice under Updates, Stable or Preview. A Mac that leaves Preview for Stable stays where it is until Stable passes it, because Lodestar never moves backwards.

Which build is stable is decided in one place, Lodestar's website, from the public list of releases and the date. Every Mac, the download on the site and the Homebrew cask ask the same question and get the same answer, and the rule can be improved without every Mac updating first. A Mac on Stable still takes only a zip from Lodestar's own releases, signed by Lodestar's own developer, so the site can only choose among builds that were already published. If it cannot be reached, nothing changes that day.

This release itself reaches every Mac at once, because the version before it knew only one channel. From here on yours follows Stable unless you choose Preview.

One patch

  • 0.48.1⏎ in the editor's lens fixes everything it shows and then gets out of the way

    After ⏎ fixed every mark, the lens took its usual second look a moment later, before the editor had read the corrected sentence again. It found the old marks still on record and lettered them again: the chips came back over words that were already right, the pill offered to fix them all once more, and every key that was not one of their letters went nowhere until Escape. Fixing one mark by its letter could bring its chip back the same way. The lens now remembers what it has answered and never letters it again. After ⏎ it offers ⌫ to take the batch back, and the next key is yours.

0.47Minor · October 9, 2026

⏎ now means yes to whatever is lit, and Lodestar looks like one thing in one light

In Keep, ⏎ pastes the latest card, the one already lit, exactly as J does, and with the same keys beside it: ⇧ as it was copied, ⌃ its reading, ⌘ its actions. While you search it still takes the best match. In the editor's lens, ⏎ fixes every mark the lens shows at once, and the lens says how many before you press it: "Fix all 3". The fixes land from the end of the text backwards, so none moves another, and only marks in view are touched. The lens then waits one more key. ⌫ takes the whole batch back, and any other key goes to your app, so in a chat the first ⏎ corrects the message and the second sends it.

Messages that flash on the glass now speak one way: the fact first, and on a quieter second line the way forward, with its keys drawn as keys. A message that needs you stays until your next key. A key you could press but are not being asked to lies flat in a shallow well, rather than fading. Nothing you read is set smaller than 13 point, and the coach's record fits on one line: "Searched 31 times across 6 weeks". The launcher's closed address says "Press again to open" and the keys that open it.

Settings, Send Feedback, Uninstall and the image door float on Lodestar's own soft shadow, as every other surface does, rather than the window server's grey ring. In Settings the row your keys are on, the result a search picked and the row a search landed on all rise the same way, where one was washed in the accent and another outlined in it. Its ways out are keys, Reset is a button, the warm glow behind the mark on the light overview is your accent, and each place's picture floats free of the box it sat in. The lists of apps show each app's icon and name, never an identifier. Every card that asks lights the key it is asking for. Everything that moves moves on one curve, every grey fill and edge is one of two weights, and the menu bar's first line is simply the name and the version.

A microphone that hears nothing is set aside after two silent stretches again, as it was meant to be. A rebuild had been counting the first stretch twice, so one silence was enough to switch away from a headset that was only slow to wake.

0.46Minor · October 8, 2026

Lodestar now tells you when to get up, and looks as it should in daylight

After thirty minutes of work with no break of two minutes, a walk is due. Lodestar waits for the next natural stopping point, the moment you leave an app you have been working in or close the draft, because a word between thoughts is taken and one mid-sentence is not. It never comes while you are reading. The note says the fact and then what to do, "Thirty minutes without a break" over "Walk for two minutes", with the mark lit as far into the hour as the stretch has run: half at thirty, whole at sixty. Sixty is the last it says about that stretch. It asks for nothing and goes at your next key. The number comes from the research on breaking up sitting, which finds two minutes of light walking every twenty to thirty minutes does what standing does not. `coach.stand` turns it off and `coach.stand-after` moves the thirty.

Light mode was the night turned over, and it read that way. It is now made for the light. Every surface follows the Mac when it changes from night to day, without a relaunch. Keys are white with a fine edge and a darker lip, so a key is still a small object rather than a dark hole. International Orange takes one deeper shade by day, dark enough to read as text and to carry white on a lit key. And the pictures in Settings and on the first launch are made in sand, a warm clay a step deeper than the page. On the Settings overview the mark is the light: every place casts its shadow straight away from the star, and a faint warm glow spreads out from it under the ring.

The health record is described as it is. It never stores which key you pressed, but which hand, which finger and what kind of key are enough to partly reconstruct what was typed, the way a phone keypad's groups are. That is why it stays on this Mac, why anything leaving it is a separate step you agree to after seeing it, and why the guide and Settings now say so plainly.

The record also says when it could not see: while a password field held secure input, while the keyboard tap was off or accessibility was gone, while health was switched off, while Lodestar was not running, and while the Mac slept. A quiet stretch is no longer mistaken for rest, and `lodestar observations` shows how long it was blind, and why. Each keyboard's report rate is written down beside it, how long a key is held is now measured from the keyboard's own timestamps whatever the clock does, and Exact Keyboard, under Health in Settings and off unless you turn it on, charges each press to the keyboard that sent it. It needs Input Monitoring, and Lodestar asks for it only then.

0.45Minor · October 6, 2026

The clipboard is rebuilt as Keep, laid out the way your hands already are

Eight clips stand in one row, each directly above the key that pastes it. The newest is on J, under your right index finger, two keys wide and a step taller; K, L and ; follow, each a little shorter, then F, D, S and A on the left hand, older and level. A gap at G keeps the two hands apart, as the keyboard does. The left hand opens Keep and the right hand takes what it wants, so the clip you reach for most is under the strongest finger of the hand that is free. Keep opens at the height of the other bars, not at the bottom of the screen, where a terminal keeps its prompt.

Above the left hand, on the line of the number keys, rest four keepsakes: things you keep for good, each with a name and the start of what it holds. The first thing you keep goes on 4, under the index finger. ⌘ and a card's letter opens its actions, and K keeps it, with a name taken from its first words, selected so typing replaces it; ⌘1 to ⌘4 moves it, and R renames it later. A keepsake from the old fifth place moves to a free one.

The letter picks the card and the modifier picks the form, the same everywhere: the letter alone pastes the text, ⇧ pastes it as copied, ⌃ pastes Lodestar's reading of it (a colour's name, a time in your zone, a measurement converted, a column's sum), and holding a modifier shows on every card what it would paste. / searches your clips and fills the same eight places, best match first, with each match wearing the chord that takes it and the best one ⏎. ⇥ narrows to the clips from one app. The keepsakes never move while you search.

= in Keep turns it to Bring, which finds text in your other windows: the one on your other display, the ones underneath, never the one you are typing in. Type a word you saw and every line that holds it comes up in the same places, most recently used app first; ⏎ brings the best match to where you were typing, ⌥ and a letter any other, and ⇧ the whole line instead of the word. Nothing is copied and nothing is kept: your clipboard is left as it was. Password managers are never read, and neither is any app you excluded from the clipboard.

A secret pasted back from Keep stays on this Mac and is marked so other clipboard tools look away, and a secret is never drawn whole, on a card or in a keepsake's name. Every card casts its own soft shadow.

Two smaller things ride along. When you respell a word dictation misheard, the draft learns it, and hears it right the next time. And every key Lodestar draws is now the same keycap, with Settings and the other rooms drawing their own buttons, fields and menus rather than the system's.

6 patches

  • 0.45.6The chime at launch is gone for good this time

    0.45.5 stopped the new Lodestar from opening in front of your work, but one ring was left. The note that says Lodestar is ready could quietly take your keystrokes for the moment it stood, with nothing behind it to receive them, and each one was answered with the alert. Lodestar's notes, its mode pill and the marks it lays over other windows now show without ever taking a key, so what you type goes where you meant it.

  • 0.45.5Lodestar 0.45.5

    When Lodestar speaks about itself, it now shows its mark, and the mark fills as an update arrives. Lodestar has also stopped chiming at you while it changes hands.

    Ask for an update and the note that says a newer Lodestar is on its way stays up while it downloads. The star beside it takes your accent one point at a time, from a quiet stone to whole, so you can see how far it has come without a bar or a number. Whole, the new Lodestar takes over, and the star is there again to say it has.

    For a few versions, Lodestar could ding several times in a row as it started, then fall quiet. The new copy was opening in front of your work for the few seconds before it took over, and every key that reached it in that moment, with nowhere to go, was answered with the alert. It now starts behind whatever you are doing, so the keys go where you meant them and the handover is silent.

  • 0.45.4Lodestar 0.45.4

    Every letter Lodestar lays over your work is now a key, and the words it points at are underlined in your accent.

    Labels start at J. The right hand spends its home row first, then the top row and the bottom, each from the right hand outward, so the first target you see is the one under your strongest finger.

    Click hints, select's labels, the editor's lens and the numbers the peek shows over your windows are all drawn as the same small key you press everywhere else in Lodestar, solid enough to read over any page. As you start typing a label, its key lights, so you can see the hand is on its way before it lands.

    What a key points at is underlined, never washed. The editor's mistakes wear one full accent line, a touch heavier than before, and select's matches wear the same line instead of a tint behind the words, with a heavier one under the word you anchored and the span you hold. After a scroll aim lands, the word keeps its line while scroll mode stands, so you know which pane the wheel is in.

    In the editor's lens each mistake carries one small tag above it, its key and its fix. When two tags would cover each other, one steps up a row and draws a fine line down to its word. A tag that did not move draws no line at all.

  • 0.45.3Lodestar 0.45.3

    A Brave profile you already have open is found again instead of opened twice, a breath can live at B, and the coach's offer is now a row you take.

    Summoning a browser profile looked for its window by the window's title, and Lodestar could be missing windows Brave had restored after one of its updates, or holding a title the window no longer had. When no window matches now, Lodestar reads the browser's windows again before it opens a new one, so the Xonar window you have is the one that comes forward.

    B was reserved from the days breaths lived on lode B, long after they moved to lode '. Every letter holds a breath now, B included.

    When the coach has something to offer, it says it in one sentence and draws the offer the way the launcher draws the row you are about to take: the app's icon, its name, the new address in quiet keys, and lode lode lit at the end. Beneath it, quietly, how often you did it the long way and lode ⌫ to let it pass. It offers breaths far less often, only for a pair you truly arrange together, one at a time.

    Underneath, the editor no longer asks apps it never reads (the ones you skipped, the lock screen, and terminals) what you are typing, and the record keeps lines a newer version wrote even if an update is rolled back.

  • 0.45.2Lodestar 0.45.2

    The editor's card is now the answer itself, and the meeting chip is a stub you could tear off.

    Rest the pointer on a marked word and the card that rises just above it holds nothing but the ways the text could read. The fix is lit. Your own word stands beside it, and clicking it leaves the text as you wrote it. On a spelling mark a third key, Learn, teaches the word, so it is never marked again anywhere. There is no headline and no explanation to read first: a change you can see needs none, and one you cannot, a comma gone, says what it does on the fix's own key.

    Leaving a word and learning it are no longer the same answer. Keeping a word used to teach it, so every one-off word you asked the editor to leave alone went into your dictionary. In the lens, ⇧ and a letter now leaves the words as written and teaches nothing, and ⌥ and a letter learns the word. The safe answer is under the easy key and the permanent one asks a little more. Grammar is never learned, because the same change is right in one sentence and wrong in the next. The lens's keys are on its own sheet behind ?.

    The meeting chip is a fifth of the size it was. A torn stub on its edge counts down, minutes while the meeting is minutes away and seconds at the door, and lights in your accent when it is time to join. Beside it are the meeting's name, where it opens and how many people are in it, and lode lode, lit. It stays one size from the moment it appears, so nothing jumps beside your work. lode ⌫ still dismisses it.

    The calendar question, Send Feedback and Uninstall now speak the way the other rooms do: their names at one size, Lodestar's explanation in its own voice, and the keys at the foot.

  • 0.45.1The icon is redrawn in the same language as everything inside the app

    The star floats on its own soft shadow over a flat plate: clay by day, the warm night by night, with a fine edge and no gloss. On macOS 26 the icon in Finder and Launchpad changes with your appearance. While Lodestar is running, its icon in the Dock, in ⌘⇥ and in its own windows also wears your accent colour, or International Orange if you chose it, and changes the moment you change either.

    Three last places that still looked like the system now look like Lodestar. A search in Settings lands on its row by raising it, the way a bar raises the row you are about to take, instead of with a glowing ring. Uninstall opens in a window of Lodestar's own: the whole plan, a switch for also removing everything Lodestar has kept, and its keys, esc to cancel and ⌘⏎ to uninstall. And nothing is painted red any more; what cannot be undone says so in its words and sits below a line.

0.44Minor · October 5, 2026

Lodestar 0.44.0

The draft is rebuilt around one idea: it should never cover the thing you are writing about.

It holds the last four lines from every door, speaking or typing, so the page, the terminal or the design you are describing stays in view. To read the whole text, press `zo` in normal mode, vim's own key for opening a fold; `zc` folds it again, and speaking folds it too, because your eyes have gone back to the screen. Escape only changes the mode now, never the size. A card opened from the clipboard is still shown whole, since there you came to read.

The microphone has no button and no labels any more. Its status is the draft's top edge: lit in your accent while it hears you, spreading from the middle as your voice rises and curving into the corners at its loudest; a short grey line while it is opening or has failed, with the reason in words; no light at all only when you turned it off. Spoken words stay grey until every pass that might change them has finished, and turn to ink when they are final. A word the second recognizer or the clean-up rewrote is underlined until your next key, so a change made while you were looking elsewhere can be seen and undone. The foot says where the text will land and which microphone hears it; choosing another opens a small card beside the draft, Lodestar's own rather than the system's.

The bars and the draft share finer edges and a softer shadow, and the shadow lets clicks through to whatever is beneath. In Ask a saved link reads as its name with its address a step quieter, and the profile a search will open in is named once at the end of the field, with a row naming its own only when it goes somewhere else. The launcher's dot for a running app sits beside its name.

There is one night again. Lodestone was the more unusual of the two, and the worse colour to spend a day in, so dark mode is the warm grey, and the Background choice is gone; a config that set it still loads.

0.43Minor · October 5, 2026

Lodestar has a fourth look, and it starts with the ground and the bars

In dark mode you choose the night every surface stands on, under Accent in General. Default is a warm grey the colour of wet clay; Lodestone is the cold blue-grey of the stone the first compasses were made from. Both are here because the difference is one you have to live with to judge, and one will go in a later version once it has been lived with. Light mode is clay, the same material as the pictures on the doors and in Settings, and International Orange is itself at night and the same hue a step deeper on clay, so it stays readable without becoming a different colour.

The launcher, Ask and the commands bar choose a row a new way. Instead of filling it with orange, the chosen row rises a step and its keys light: the letters that reach that target without the launcher, and return. The light lands where your hand goes next. Each key is now one small object with a lit top edge and a shadowed lip, lit in the accent the way the mark's faces are. The magnifying glass is gone: each bar shows what it holds instead, windows for the launcher, a link for Ask, the menu bar for the commands, and the caret is the one orange in the field.

The update gate also counts the pointer now, so an update never arrives while you are reading with the mouse, or minutes after Lodestar starts.

0.42Minor · October 4, 2026

The draft now writes what you meant, not only what you said

Say "use the red one, actually no, the blue one" and it lands "use the blue one". A start you began again, a word said twice, a file name spoken as "draft controller dot swift", letters spelled one by one, a list you counted out as first, second and third: each is written the way you meant it, once the second ear has heard the phrase again. A language model proposes the change and a checker decides, word by word. Only words you took back may go, and only spoken names and lists may be written as one, never a word added and never one replaced, and a name you have written stays exactly as written. Anything else and your words stand as heard. On the maker's own recordings it takes the words wrong from 6.1 in a hundred to 4.6, and to 3.9 on the largest model, and across two thousand checked answers from seven models not one added or changed a word that mattered. Each change is one step of ⌘Z, and a change you undo is never offered again. There is no switch: a checker that never adds a word is what makes one unnecessary.

Speak's models are now whole setups, chosen in Speak and nowhere else. Standard is Parakeet with Gemma 4 E2B, from 16 GB; Full is Qwen3-ASR with Gemma, from 24 GB; and Max, new, is Qwen3-ASR with Qwen3.6 35B, from 64 GB. Each names both of its models in the list, and one this Mac cannot run says how much memory it needs. A Mac with 8 GB dictates with Apple's recognizer and the draft's own pipeline, and Automatic says so. What Write runs never decides what Speak runs; where the two use the same model they share one copy, on disk and in memory. Automatic on a Mac with 64 GB picks Max, which fetches about 20 GB the first time you dictate unless Write already holds the same model, and never over a metered connection.

In Settings, a search's border now stays only until your next key or click, and only on the row it found: it no longer lingers on a field, or lights the same row in the next place you open.

0.41Minor · October 4, 2026

Settings is a new room, and everything in it has a key

It opens on ten places set around the mark, each with its picture in the same clay as the doors and one line saying what it holds. The four doors come first, on the keys under your fingers: 1 Write, 2 Switch, 3 Keep, 4 Speak, then Operate, Web, Meetings, Keys and Observations, with General on 0. A digit opens a place from anywhere. A place keeps its picture and its sentence on the left and its settings on the right, under a heading for every group, and every setting wears a letter that never moves. A place with one switch for all of it keeps that switch on a. What you have set wears a dot and a way back; what Lodestar chose says so, Automatic or System, with what it picked. A permission says whether it is granted and opens the pane of System Settings that grants it, and a place that needs you wears a dot beside its name. lode , opens the place for whatever is in front of you: over the strip, Keep; over the draft, Speak; over the editor's marks, Write; over Ask, Web.

Search finds a setting by its name or by the word you would use for it, clipboard for Keep or dictation for Speak, shows the two keys that reach it, and lights the row it lands on with a thin border in your accent. On a Mac with Apple Intelligence you can ask in your own words, make scrolling slower, and Apple's model on the Mac suggests the row. ⌘Z undoes the last change you made there, and History lists every change to the config, from Settings, the file, the coach or the editor, each with its undo.

What Lodestar observes is now two records with two switches. The logbook is how you move between apps and windows, and the coach reads it; health is the rhythm of your hands, when each key goes down and how long it is held, by hand and finger, never which key. Either can be off with the other on, each has a size limit you can set, and either can be deleted on its own, in Settings or with lodestar observations clear and --logbook or --health. With the logbook off the coach rests and nothing is written, from the moment the app starts. The first launch moves the health you have already kept into its own file, once.

Tabs has retired: the editor's marks own lode ⇥, and click hints letter the same tabs. Uninstall now says that removing everything means everything, downloaded models included.

0.40Minor · October 3, 2026

Dictation hears you twice now, and writes what you meant

The draft still shows your words the moment you say them. Behind them, a second ear listens to everything you have said since you last touched a key, and while you keep talking it writes that stretch again, better, in place. On the voice it was measured on, the names you use every day came out right 97 times in a hundred, where they had come out right 32, and the words that needed fixing went from one in six to one in sixteen. The second ear is a model that runs on this Mac. Settings has a page for the draft now, and its Model row starts on Automatic, which fetches the model your Mac suits the first time you dictate: the larger for Macs with 24 GB and more, a smaller one for 8 GB, or Apple's recognizer alone for a Mac that would rather not. Whatever it changes is one undo away, and ⏎ waits for it at most a second.

A pause is thinking, not the end of a sentence. Stopping to find a word used to leave an ellipsis, or a full stop and a capital in the middle of what you were saying, and starting to type while you talked did the same. Now a sentence ends where its words end.

Your words are written the way you write them. Lodestar used to repair a listed name only when the recognizer's spelling came within a letter or two of it, which is why it turned "ghostly" into Ghostty and never turned "load star" into Lodestar. It now listens for how a name sounds: "load star", "super base", "cloud code" and "can Dora" become Lodestar, Supabase, Claude Code and Kindora, and an everyday word you meant stays the word you said. With a terminal or an editor in front, the files, functions and branches of the project it is open in are names too: "draft controller dot swift" lands as DraftController.swift, and "local slash dev" as local/dev. A name that does not exist yet takes the keys a vim hand already knows, crp for PascalCase, crc for camelCase, crs for snake_case. Spoken numbers become digits when they are versions or counts, "um" goes, and "for Monday, no wait, I mean Tuesday" lands as Tuesday.

The editor's model menu leads with Automatic too, and names the model it picks. Interaction in Settings is Interactions now, and the draft and the editor sit side by side on its number row, at 9 1 and 9 2. And the app now lists the open work it is built on, with the licenses that ask to be named, in Acknowledgements.txt inside it.

0.39Minor · September 26, 2026

Lodestar begins with the thing you came for

The first launch opens on a welcome with four doors: Write, Switch, Keep and Speak, the same four the website shows. Choose the one you want first, and Lodestar walks you through that one to a real result: a typo fixed where you wrote it, an app reached by the launcher and then by a letter of its own, a copy pasted back from the strip, a sentence spoken into place. The other three wait, and each is brought up once, later, when it would help.

Only one permission is asked for at the start, Accessibility, and the card says what your door needs it for before macOS asks. On an account that is not an administrator, the card says so up front, because turning it on needs an administrator's password, and it can copy a short note for your IT team.

Writing starts on spelling, with nothing to download. Once the first fix is taken, Lodestar offers the closest model your Mac can run, and says what it costs before anything downloads.

Switching teaches the launcher before any letters, because on the first day the launcher already works: type a few letters of an app and it opens filling the screen. Letters come after, suggested from the apps you have open, and kept only if you keep them.

Nothing changes for anyone already using Lodestar.

6 patches

  • 0.39.6A secret on your clipboard no longer shows itself to a room

    The clipboard strip keeps what you copy, and that has always included the key from a dashboard, the token in a terminal, and the password someone sent you in a message. Opened during a screen share, the strip showed every one of them in full to everyone watching. Now a card that holds a secret draws its middle as a single bar and keeps its ends, so a key reads as sk-proj, a bar, then its last four. The ends are enough to tell one key from another, and the bar is the same width for every secret, so it never says how long one is. Only the secret is hidden: the rest of a command or a settings line reads as it did.

    Nothing else about the clip changes. It is kept, pasted and searched whole, so the key you copied to paste still pastes, and typing part of it still finds it. Password managers already mark what they copy as private, and those copies are still never kept at all. This is for everything else.

    Lodestar knows a secret by the shape its maker gives it, the prefixes OpenAI, Anthropic, GitHub, Stripe, Slack, AWS, Google and others put on their keys; by its label, a value after "password" or an API_KEY=; and by the look of random text. What you mean to paste as it is stays as it is: numbers, commit hashes, IDs, paths and links. A password made of ordinary words is recognised only when something labels it.

    And a copy from select holds only what it says. A span caught with the space after a word, or a line with its indent, used to paste with a stray space you then had to delete. Now every copy select makes leaves the spaces and line breaks at its two ends behind, and a selection it makes in an app is trimmed the same way, so what lights up is exactly what pastes.

  • 0.39.5Lodestar is steadier where it was quietly uneven

    Dictation keeps its promise about time. When the microphone was slow to start, the draft was meant to stop waiting at two and a half seconds and try again, but it waited for the slow start to finish first, however long that took, and then tried again anyway. Now it stops at the deadline, and a start that is merely slow is left to finish rather than begun a second time. On a Bluetooth headset, the Mac's own microphone now keeps listening until the headset has actually heard you, not just until it has answered, so the first words after a slow headset are not lost in the gap. What the Mac's microphone hears no longer counts as the headset hearing, so a headset that stays silent is still named as the one hearing nothing.

    The window you end on is the window Lodestar thinks you are on. Moving quickly from one window to a new one and back could leave it holding the new one, because the answer about the new window arrived last and won. And a window you moved or resized while Lodestar was reading it is now read again, so its last position is the one it keeps.

    When two copies of Lodestar overlap, as they do for a moment at every update, the log keeps every line of both instead of writing one over the other.

    Updates arrive more reliably. A check that fails on a poor connection now tries again after a quarter of an hour and then an hour, instead of waiting a day. An answer from GitHub that is an error, such as a rate limit, is read as an error and not as "nothing new". And an update now waits until you have really stepped away, counting your typing and a presentation in progress, not only your use of Lodestar.

    And what you were in the middle of is on disk sooner. A draft you are dictating is kept safe every half second while you speak, not only when you pause, so a draft cut short can come back. A window set aside to the corner of the screen remembers where it came from the moment it is moved. Quitting saves the clipboard's last copy. The editor, turned off and on again, reads the sentences it had not reached. And a record of your keys that was cut off mid-write is closed as it stands, rather than leaving everything after it misread.

  • 0.39.4Dictation starts listening sooner on a Bluetooth headset

    Most drafts start listening in about a seventh of a second. The slow ones were all the same: a Bluetooth headset, which has to leave the mode it plays music in for the one it takes calls in before it can hear you, and that takes one to two and a half seconds, sometimes more.

    Now, with the lid open, the Mac's own microphone listens while the headset wakes, from the moment the draft opens, and hands over to the headset as soon as the headset hears your voice. Measured on a headset that took between a second and a quarter and six seconds to open, the draft was listening in under half a second. The headset is still the microphone the draft names, and nothing it hears or fails to hear is held against it on the Mac's account.

    With the lid closed nothing changes: the Mac's microphone is off then, and the draft waits for the headset as it always has.

  • 0.39.3Lodestar no longer waits on other apps

    To know your windows, Lodestar asks each app about them: where a window is, what it is called, whether it is still there. It used to ask on the same thread that passes your keys along, for every window at launch and again each time an app opened, closed, renamed or moved one. Brave alone opens a small window for every tab you hover. An app that had stopped answering made each of those questions wait, and while it waited so did your keys, sometimes long enough for Lodestar to give up and restart. Those questions are now asked to one side, one queue for each app, so an app that hangs holds up only its own windows. Lodestar is also ready sooner when it starts.

    The health record is more careful about which hand did what. A move, click or scroll is now counted to the device that made it, which the event itself says: a trackpad marks its touches and gives its scrolls a beginning and an end, and a mouse does neither. Before, with a mouse and the trackpad both attached, every reach counted as the mouse's and every smooth scroll as the trackpad's, including a mouse that scrolls smoothly. And a day in the record now runs from four in the morning to four in the morning on your own clock, so an evening at the keys counts as one day, not two.

    The editor also now keeps a quiet note of how long the apps you write in take to answer it, so the next thing it gets faster at is the thing that costs you most.

    And Lodestar no longer quits when the microphone changes hands at the wrong moment. The draft readies its microphone at launch and lets it go when the audio devices change, and a second change arriving just after could reach the microphone it had already let go of. It is now kept a few minutes before it is freed. The new release check found this one: each build is now started and put through a click, a scroll and a keystroke by itself before it ships.

  • 0.39.2Typing no longer waits on the editor

    Every key you press passes through Lodestar on its way to the app in front, and since the editor arrived it had been waiting there. On each keystroke in a field the editor reads, it worked out its marks on the same thread that passes the keys along: a few hundredths of a second in a chat message, a quarter of a second in a long email, a full second at the editor's limit, which is long enough for macOS to stop sending keys through at all. That work now happens to one side, and the editor asks what language a sentence is in once rather than on every key. The keys go straight through.

    The editor's model also stays ready for longer. It was let go two minutes after the last sentence, so coming back from a short pause meant waiting several seconds while it loaded again, twenty gigabytes at a time for the larger model. It is now kept for twenty minutes, and still let go at once when macOS says memory is short. A small leak that grew with every load is closed.

    A pick made with a capital no longer holds shift down for the click. Click hints and select are chosen with a capital letter, and the click that followed carried the shift, which Brave reads as open in a new window. Nothing Lodestar clicks, drags, scrolls or types now carries a key your hand is holding.

    Keeping a word in the editor no longer quits Lodestar, and neither does copying a line like hsl(nan 50% 50%). A slow start after a crash is no longer mistaken for a freeze, which had turned one crash into several, and a few waits on other programs that could freeze the app now happen off to the side.

    Lodestar also notices keyboards that connect after it starts. Its list of keyboards had been fixed at launch, so a Bluetooth keyboard that reconnected later never appeared, on the Keyboards page or in the record, and its keys were counted as the laptop's. Each key is now counted to the keyboard it came from, and a keyboard with mouse keys is no longer taken for a mouse.

  • 0.39.1Feedback now reaches a person

    Report an Issue sent you to GitHub, where most people have no account and the rest must write in public. In its place is Send Feedback, in the menu under the star: a note written in Lodestar's own window that goes straight to the person who makes it.

    Nothing about you travels with it unless you add it. An email address is there if you would like a reply, and left empty the note arrives all the same. A diagnostic report can go with it, off until you tick it, and you can read the report before you send, because its recent log lines can name windows you had open.

    If the note cannot be sent, it stays in the window and is also put on the clipboard, so nothing you wrote is lost.

0.38Minor · September 25, 2026

The clipboard reads what you copied, and finds it faster

A clip that is only a color, a moment, a measurement or a sum now carries a note from Lodestar at the foot of its card, in Lodestar's own serif. The clip itself stays exactly where every card keeps its text, and it is still the only thing that pastes; the note is Lodestar telling you what it is.

A color is shown and named: #FF4F00 is International Orange, #FF0000 is Fire Engine Red, Apple's green is Shamrock Green. The names are the ones more than two hundred thousand people gave colors on their own screens, so a name sits where people put it. Search finds a color by its name, so orange finds the orange you copied as a hex.

A timestamp says how long ago it was, as a person says it: 6 hours ago, yesterday morning, Tuesday afternoon, August 2025. Beneath it is your clock, UTC, and any zones you keep, which you add on the Clipboard page as a city. A zone that would only repeat the value is left out.

A measurement in the other system is read into yours, in the unit you would reach for: 5 km is 3.11 mi, 180 cm is 5′ 11″, 72°F is 22°C. One already in your units is left as it is. Imperial or Metric is the one new setting, under Advanced, and it starts as your region's.

Arithmetic is read as its answer: 1234 * 1.08 is 1,332.72. A phone number, a date, an ID or a range is never mistaken for a sum.

The search itself was the lag you felt while typing into the strip. It had been reading every clip afresh on every key; it now reads each one once, and a keystroke over a full history takes about a millisecond where it took a tenth of a second, finding exactly what it found before.

The editor now works inside the draft too, with ]s and [s to move between marks and z= and zg to fix or keep a word, and it learns which English you write from your Mac.

One patch

  • 0.38.1A new mark

    The compass rose that stood for Lodestar did its job, and read as a compass: the thing you take a bearing with, not the star you steer by. In its place is a star with depth, twelve points drawn as flat planes of International Orange, each lit only by the way it faces, on a charcoal that carries a little of the orange. It is in the Dock, in Finder, on the disk image, and in the menu bar, where its silhouette stands at rest and knocks out of a disc while a chain is pending, as the rose did.

    The star is defined once and every copy is drawn from that definition, in whatever color it is asked for, so it can follow wherever color on the Mac goes next.

0.37Minor · September 25, 2026

The editor: a line under what reads wrong, in everything you write

Lodestar now reads what you type, in any app, and draws one thin line under a word that is misspelled or a phrase that does not scan. Nothing else appears: no badge, no count, no panel beside the text. A field with no lines has been read and is fine. Press lode ⇥ and every mark wears a letter and its fix; the letter applies it, ⇧ and the letter keeps what you wrote, ⌫ takes the last fix back. If your hand is on the mouse, rest the pointer on a mark and it offers the same two answers.

It corrects what you meant to write and never what it thinks you should have meant. Spelling and grammar, never rewording, never tone, never a name, never your lowercase or your casual words, never anything inside code or a link. A word you keep becomes one of your words; a grammar mark you keep is quiet in that sentence and teaches nothing, because the same change is right in one sentence and wrong in the next.

A small language model reads each sentence when you finish it, on this Mac and nowhere else. Choose how much it reads in Settings, on its own page under 0: Spelling needs no model at all, Minimal uses Apple's own, Standard is a 3.6 GB download that holds about 4 GB while you write, and Full, for Macs with 64 GB, reads most precisely. The model loads when you start typing and lets its memory go two minutes after you stop. Your text never leaves the Mac and is never kept.

The editor is off until you turn it on, and when you do, it asks first.

This version needs a Mac with Apple silicon and macOS 14 or later. A Mac that cannot run it stays on 0.36.3, and says so once.

One patch

  • 0.37.1The editor, on every Mac it was meant for

    0.37.0 started only on macOS 27. One of the libraries under the editor's language model had quietly moved to something only the newest macOS provides, and the build carried it along. On any earlier system the app did not open, and the updater put the previous version back a minute later. This version holds that library where it was, and from now on a release is opened on every macOS it claims, 14 through 26, before it is published at all.

    What 0.37.0 was meant to bring:

    The editor: a line under what reads wrong, in everything you write.

    Lodestar now reads what you type, in any app, and draws one thin line under a word that is misspelled or a phrase that does not scan. Nothing else appears: no badge, no count, no panel beside the text. A field with no lines has been read and is fine. Press lode ⇥ and every mark wears a letter and its fix; the letter applies it, ⇧ and the letter keeps what you wrote, ⌫ takes the last fix back. If your hand is on the mouse, rest the pointer on a mark and it offers the same two answers.

    It corrects what you meant to write and never what it thinks you should have meant. Spelling and grammar, never rewording, never tone, never a name, never your lowercase or your casual words, never anything inside code or a link. A word you keep becomes one of your words; a grammar mark you keep is quiet in that sentence and teaches nothing, because the same change is right in one sentence and wrong in the next.

    A small language model reads each sentence when you finish it, on this Mac and nowhere else. Choose how much it reads in Settings, on its own page under 0: Spelling needs no model at all, Minimal uses Apple's own, Standard is a 3.6 GB download that holds about 4 GB while you write, and Full, for Macs with 64 GB, reads most precisely. The model loads when you start typing and lets its memory go two minutes after you stop. Your text never leaves the Mac and is never kept.

    The editor is off until you turn it on, and when you do, it asks first.

    This version needs a Mac with Apple silicon and macOS 14 or later. A Mac that cannot run it stays on 0.36.3, and says so once.

0.36Minor · September 21, 2026

The lode key can be tapped

It was a hold: down, a letter, up, and the lens stood while it was down. Four days of the raw record said what that hold was for. Ninety- four in a hundred covered exactly one key, and a hold that buys one key is a co-contraction bought for nothing — the thumb pressing against the letter for two hundred milliseconds, a hundred and ninety times a day.

So a tap arms the next key instead. Lode down and up with nothing struck inside it, shorter than a peek, and the key that follows within a second is the gesture it would have been under the hold, routed the same way, the phrase ending with the key the way it ends when the thumb lifts. The hold is unchanged and is still how the map appears, which is what gives the two forms their meaning: tap for the gesture the hand owns, hold to see the map. Nothing appears on screen for a tap: nine gestures in ten strike inside three tenths of a second, so a mark would be motion on almost every one, and what bounds a state the eye cannot see is the second the arm lives rather than anything the eye has to find. Escape disarms. A tap followed by nothing expires silently. Tapping twice is still assent to the coach and never leaves a key armed behind it. And the record showed the cost as well as the gain — a short empty press followed by a letter now becomes a gesture rather than that letter, fourteen times in four days — so `lode.tap` is a switch, on by default, and every press that arrives armed is marked in the raw record, where the trade can be read rather than argued.

And the record knows where your keys are.

It kept a finger per press by reading the keycode the way a typing course reads a Mac keyboard. On a split board that puts enter, backspace, space and half the modifiers under the thumbs, every one of those presses was charged to the pinky, and one lode press — three modifier records — was scattered across three digits. The convention was wrong on exactly the boards whose owners care.

Settings has its first page behind a pane for it. Coach → Health → Keyboards opens to one board, chosen at the top, its fourteen keys below with the standard placement labelled as such, and a placement that differs is the only thing ever written: `health.keyboards`, per keyboard and per key, "right thumb". Letters keep their columns on every board that keeps columns and are never on the page. The tap writes the finger under that declaration, and every past row can be read under it again, because the record kept a kind, a modifier bit and a side. The hand column is never touched — it is the split the published index was defined on, and the sides and the pairs come out identical under any map. A changed map is a new era in the ring.

The Health row once called Handedness is now Dominant hand.

3 patches

  • 0.36.3An update that checks the Mac it is going to before it goes

    The next version of Lodestar will ask more of the Mac it runs on: Apple silicon, and macOS 14 or later. That is what the editor it brings needs, a language model reading your sentences on the Mac's own graphics chip. Until now the updater checked that a new version was signed by us and was the version it claimed to be, and never whether this Mac could open it. An Intel Mac, or one still on macOS 13, would have installed it, failed to start it, rolled it back a minute later, and done the same with every release after.

    This version reads what a new build asks for before it installs it. If this Mac can run it, nothing changes. If it cannot, the update is set aside, Lodestar says once which Mac or which macOS it needs, and this Mac stays on the version that works for it.

  • 0.36.2Breaths offered where they are wanted, and a draft that remembers what it heard

    The coach had been offering breaths as its default. Ten of its last twelve suggestions were layouts, and not one of the four you accepted was ever brought back. The reason was in what it counted: two apps used one after the other, all day, read as two apps that belong together. They do not. Ghostty and Brave, the pair it pressed hardest, were each pulled into view on its own nearly every time the week after their breath was saved. The hand wanted one window at a time, and the chord already composes the rare pair it wants together.

    So a breath is now offered only for a pair you stand side by side yourself, with a shift summon, a chord or a beside move, about twice a week, and it is priced on those arrangements, because a breath replaces composing, not switching. And an accepted breath is judged the way an address is: by coming back. It holds the coach's one learning slot until you have recalled it a handful of times, at any letter and in any layout that still holds the pair, and one that is never recalled counts against the kind, where the accept alone used to count as a success. When things are already quick, the coach now has less to say, which is right.

    The draft also keeps something it used to throw away. When a draft ends with nothing in it, the record now holds how loud the microphone was: a device delivering nothing at all, a quiet room, or a voice. A draft closed in a second and a draft that waited on a deaf microphone look the same from the outside, and only this can tell them apart.

  • 0.36.1Dictation with the lid closed, and on a headset that was slow once

    A closed lid switches your Mac's microphone off. Not quietly: every program reading it receives exact zeros, at the full rate, and the draft read those zeros through an evening in clamshell, sixteen sessions with the glyph lit and nothing behind it. It had a test for a microphone that delivers nothing, but the test counted buffers, and the zeros arrived as buffers.

    The engine is now watched for signal. A room never reads below a whisper of noise; a dead input reads nothing at all, and nothing at all for a second and a half, four on a Bluetooth headset whose telephone link takes that long to come up cold, is what the draft acts on. With the lid closed your Mac's microphone is not fallen back to at all: a headset is read when one is connected, and when none is, the register line says the reason in one line rather than listening to silence.

    The headset had its own trouble that evening. Its link came up more slowly than the draft's budget for a start, so each start was retried, and the retry stopped a session whose first sound had not arrived yet and wrote the headset off as deaf. Twice, in ten seconds, after which every session in the process was pinned to the microphone the lid had switched off, whatever the register line was set to. Three things changed. A start that timed out proves nothing about a device; only a whole window of silence with the engine running does. A device you name on the register line is read as named, always. And a device written off is forgiven the moment the set of inputs changes, so a headset that was slow once is not held against it after it reconnects.

    And when the microphone has been open for three seconds and heard nothing, the register line says so: hearing nothing on, and the name. The listening note's silence, for the eye that is on the draft.

0.35Minor · September 16, 2026

Lodestar writes itself down

The first audit of the raw record began with a question the data could not answer: the way holds were timed had changed, and nothing in the files said when. So every day file now carries, in its header, the build that wrote it, the record format, the install and the devices that were attached — and opens a fresh segment beside itself the moment any of that would change mid-day, so a header never describes rows it did not see. An era event lands in the record whenever the build, the formats, the input settings, the screens or the keyboard layout differ from the last time they were written down, and the monthly archive keeps the set of builds it saw. A change in the data can now be told from a change in the hand without reading a log.

The record grew, each column with the question it answers. A modifier's own press is recorded — how long ⌘, ⇧, ⌥, ⌃ or fn was held, and how many keys it covered — because a chord's sustained load is what the letters' holds cannot show. The finger, one step finer than the hand, because the finger is the unit a layout is changed in. The time from a key to the backspace that corrects it, because how fast a slip is noticed is a different fact from how often one is made. Beneath the pointer's folded reaches there is now a raw record of the reaches themselves, every report the mouse made on the way to a target, with each press's button, its source — your hand, Lodestar's own pick, or another program — and the device it was on, because a smoothness measure nobody has chosen yet cannot be derived from three band sums, and a pick is a click the hand did not make. The wheel's bursts are split by precise deltas and by momentum, a drag against a flick. And beside every window: what a pixel is on each screen, whether the lid was down, which layout the keys were read through, and the settings that scale a delta into a point. Never which key. Never a position.

Retention is two memories, each bounded by size and each saying why. The behavioral ring — what you did — retires its oldest months once it is over a quarter gigabyte, about two years at today's rate; its pulses and windows leave first, for an archive no bound of the ring's touches. The health record — how your hands did it — has a bound a decade out, declared and measured; Lodestar will say so as it nears it, and it never prunes a baseline on its own. The ring was already kept for a year, not the ninety days the notes once said; age retires nothing now.

The health record is backed up. The data folder used to sit outside Time Machine as a whole, for the right reason — the behavioral record is browser-history-grade. Those files still stay out, one by one. The raw presses, the raw reaches, the archived windows and the monthly rollup go in, because they are the part nothing can recompute, and one disk must not be the only copy of them.

The doctor prints the time to correction, the wheel by what made it, and the clicks that were the tool's and not the hand's.

2 patches

  • 0.35.2Lodestar cannot freeze the way it did

    Two nights ago the first click after an update deadlocked the mouse tap, the main thread queued behind it, and the system switched the key tap off for not answering. 0.35.1 fixed the lock. This release removes the class of bug and bounds the damage of anything like it.

    No tap callback takes a lock any more. The key tap and the mouse tap copy the few fields they need off the event and hand them to one queue that owns everything else; there is nothing to deadlock on because there is nothing to lock. A thread of its own pings the main thread and, if the answer does not come back inside eight seconds, says so in the log and aborts — a crash launchd recovers from in a second, with a report naming every thread, where a freeze recovers from nothing. And the update watchdog now blesses a new build only when it answers on its control socket, not merely when it holds the pid file: a frozen build is rolled back like one that never started.

    The tests reach the real threads now. The harness runs the real health monitor at a scratch directory in every scenario, a stress test drives both taps at once against a deadline, and `lodestar --self-test` runs that stress on the signed binary itself before it is notarized. The suite also runs five times faster, four minutes to fifty seconds: every scenario's glass stayed in the application's window list after the scenario died, a hundred panels by the end, and every run-loop turn paid for all of them. They are closed now, and a test proves a dead scenario leaves nothing behind. And the ship stops after the build for a hand: one click, one scroll, one keystroke on the bytes that ship.

    And the click door spends its chips where they were always meant to go.

    `lode ;` puts a letter on what typing cannot reach, and it had been deciding that by asking how a target was found rather than what it looks like: anything the accessibility tree could name by role was assumed to carry a word the hand could type. An icon button refutes that. It is a button like any other and there is nothing written on it, so it wore no letter and answered to no search, and the pointer was its only door. A notifications page held a hundred and seven targets and drew a single letter, while two in five of them painted no text at all — the checkboxes down the side, the icons across the header, a done button on every row.

    The question is now asked of the screen. A target keeps the address it always had when a word is painted inside it and wears a letter when none is, read from the same recognized words the typing searches, so the two ways in can never disagree about what is there. A word that merely brushes a target belongs to its neighbour — the caption beside a checkbox is the caption's, not the box's — so most of a word has to sit inside to count as an address. The tree answers before the screen does, so the letters wait for the first words and are then spent once: a letter that moved under a hand already reading it would be worse than no letter at all, and a window with no words coming is not made to wait past four tenths of a second. A browser window that drew one letter now draws forty-seven.

  • 0.35.1Lodestar froze on the first click

    0.35.0's mouse tap took its lock for the whole of a click, then asked whether the lid was closed under the same lock, which does not re-enter. The tap's thread waited on itself; the next keystroke waited on the tap; the system switched the key tap off for not answering, and the right command key fell through as plain command. If that happened to you: sorry. Quit and relaunch, and this build does not do it.

    The lid now has a lock of its own, a test proves that a click and a scroll both come back on a thread of their own, and the raw stores are placed beside the observations rather than at a fixed path, so that test could not touch a real record.

0.34Minor · September 16, 2026

Lodestar keeps the record

Until now the health pulse kept summaries: counts, moments, a histogram of how long keys were held. A summary answers the questions it was built for and no others. Beneath it there is now a raw record: every press, when it went down and when it came up, which hand, what kind of key, and whether a modifier, a lens, or Lodestar itself was involved. Never which key. One file a day, compressed when the day closes, on the order of fifty megabytes a year, in the keys folder beside the rest of your data. Nothing in it is analyzed. It is kept so that a question nobody has asked yet can still be put to this year's typing.

Above the record, ninety-second windows describe the typing habit the way the clinical literature reads it: exact quantiles, the distribution at the edges the published features use, the fluctuation between one press and the next, the rollover when a key goes down before the last one came up, all of it kept for each hand and each direction across the keyboard. Each window also notes the app, the kind of element that had focus, the keyboards attached, the power source and the screens, because a hold time is a mechanical fact and a different keyboard is a different instrument. The pointer's reaches keep their speed profile from the mouse's own counts. The monthly archive keeps each window's spread as a sample, so a month holds the spread of the spread.

Two optional facts about you live under Health in the Coach pane: the year you were born and the hand you write with. Age and side are the first things any reading of the hands is adjusted for. Both stay on the machine, like everything else here.

The design note moved one line. The discipline is not in what the instrument collects but in what it says and what leaves the machine. Nothing leaves. What it says is still nothing: the printout describes, and a description is not a verdict.

Fixed: every hold was timed from the moment the event tap got around to it, on the main thread, so a key released during a window rearrangement was measured tens of milliseconds long. Presses and releases are timed from the event's own stamp now, on the keyboard and the mouse alike.

0.33Minor · September 15, 2026

A letter on every tab, two notes in the draft, and a click that means it

First, a fact that is also an apology. Yesterday's 0.32.4 was the previous build under a new label. Xcode 27, which arrived with macOS 27, puts a universal build in a different folder than the one the packaging script had always read, and the script packaged a three-day-old binary without a word. The glass tinted toward the system's ground, which the last note described, arrives now. The label did more than mislead: a Lodestar that believed it was 0.32.3 saw 0.32.4 on offer, installed it, relaunched, and was still 0.32.3, so it installed it again, every three minutes through the night. The packaging script now refuses a binary that does not announce the version it is labelled with, and Lodestar refuses a release that, once applied, did not change it.

lode ⇥ puts a letter on every tab of the window, and the letter switches to it. It is the tab as your Mac names it, so it works the same way in a browser and in a terminal, and a window with no tabs says so. The list of windows the key used to open is one modifier away, on lode ⇧⇥.

A pick is a click. Whatever you pick in the click door, by typing what you see or by a letter on a chip, Lodestar now clicks it the way your hand would, in every app alike. It used to ask the app to press the element for you, and some apps said yes and did nothing; the Share button in Asana was one of them. The cursor ends where the click was.

The draft has two sounds. A note rises when the microphone is live, on the first sound it hears rather than on the engine reporting ready, because a microphone your Mac names can deliver silence. A note falls when the words land. Nothing on cancel. Both are a fifth apart from Lodestar's own alert sound, which ships inside the app and can be chosen in Sound settings. Sounds, in settings, turns the pair off.

In the web bar, a pin before a profile's name says that a pin or a rule chose it. A bare name is Lodestar's guess.

The launcher no longer counts windows beside an app. The number counted everything the tree called a window, pickers and toasts included, and moved while you watched.

And a window that outlives its accessibility handle is found again. Zoom rebuilds its tree during a meeting; the meeting window kept its identity while Lodestar's name for it expired, and for seven minutes nothing could reach it. Now a fresh handle for a known window takes over, and every verb that needs the focused window asks the app afresh when Lodestar's answer has died.

4 patches

  • 0.33.4Lodestar leaves the way it came

    Until now the only way out was a command typed into a terminal, and dragging the app to the Trash left its login agent behind, asking the system for a binary that was no longer there every ten seconds for as long as the machine lived. Both doors are finished now. Uninstall sits under Quit in the menu and shows the whole plan before it touches anything: the browser role handed back, the permissions returned, the alert sound removed and the alert restored to the Mac's own, the links, the app, the login agent, and last of all the running program. Config, breaths and the clipboard stay unless you ask for them to go, because they are yours and they survive a reinstall. And the Trash is a real door: the login agent now runs through a stub that becomes Lodestar when Lodestar is there, and when it is not, takes itself and the alert sound away and stops. An app merely moved puts both back the next time it starts.

    The alert sound is Lodestar's own, so Lodestar keeps it where Sound settings looks. A copy is placed at every start, and replaced when a release changes it. Whether your Mac's alert uses it stays your choice, made where you make every other one.

    The menu carries verbs now, and only a few: the walk, Settings, updates, an issue, Quit, Uninstall. Editing the config file and opening the log were doors nobody should be asked to open, and routing clicked links was a switch pretending to be a verb, which is what Settings is for.

    Fixed: after every update since Lodestar learned to hand itself back to its supervisor, the short-lived instance the updater started was reading the news of its own update and taking it with it, so the Lodestar that stayed never knew it had updated, and never said so.

  • 0.33.3Every surface the same shade, and a click that is only a click

    The launcher and the web bar read darker than the draft and the pill. Photographed on one stage they were the same glass; on a desktop they sat over different things, and the pill, being small and mostly edge, ran a few levels lighter than a bar over the same ground. The veil inside the glass now takes nearly all of the backdrop's vote: the bar, the draft and the pill read 25 over charcoal and 29, 29 and 31 over a white page, within a hand of levels of one another anywhere on the screen. A trace of the frost remains at the rim.

    A pick in the click door used to press and release faster than the cursor could get there, so some apps took the press where the pointer had last rested and the release at the target, and dragged a selection between the two. The cursor is now placed first and the press waits for it, so a click is a click.

  • 0.33.2One glass reads the same on every surface

    The draft looked different from the launcher, and the photographs said it was not: on a flat ground the two measured to the level. The difference was the backdrop. The glass lets a share of what is behind it through, and a small bar sits over one thing while the draft, being large, sits over several, so a bright window behind half of it read as a patch. No tint colour or strength removes that share; every one tried moved the panel darker or lighter as a whole and left the patch alone. What removes it is a veil in the ground's own colour inside the glass, taking most of the backdrop's vote and leaving the frost the rest. The draft now reads the same over a white page as over a dark one, within twelve levels, and so does everything else, because every surface is the one glass.

    Nothing else changed.

  • 0.33.1The glass is charcoal again

    This morning's release tinted every panel toward black, and every panel arrived a shade darker than it was drawn: grey 6 where the design's charcoal is 26. The material does not blend toward a colour the way a veil does; it multiplies with what is behind it, so aiming at black, or at charcoal itself, both land near black. The tint now aims at a lighter grey chosen by photograph so that the panel lands on its own ground: 25 over charcoal, 65 over a white page at nearly eight to one, and in light mode paper over anything. Reduce Transparency draws an opaque veil in the ground's colour, since a tint cannot be made opaque either.

    Nothing else changed.

0.32Minor · September 12, 2026

The draft stops explaining itself, and starts listening better

The draft was the last surface carrying a legend. Three keys sat under your words on every opening, fading on a timer, and they were the three that fit rather than the three that mattered. Now the draft shows nothing and answers `lode ?` with its own keys, the way every bar already does.

Which leaves room to say something worth reading. The keys open with the mode you are in and one plain line about it, and the editor's own panel teaches the grammar rather than listing the alphabet: the verbs stand alone, the group says what follows them, and the wrapping verbs that are not vim at all finally have somewhere to be found. Nobody guesses `sa`.

One undo used to take back a whole dictation. Speech was joining the typing run, and a dictation never leaves insert mode, so the run was the entire session: eighty-seven words on one keystroke. Each thing the recognizer settles is its own step now.

And speaking over a selection replaces it. Select a phrase, say it differently, and the words take its place. One undo brings the selection back exactly as it stood, which is what makes it worth trying.

The microphone can no longer hang. Opening it waits on a queue that CoreAudio can block, and a queue wedged by a device changing hands after a restart never came back: the draft would say it was opening the microphone until it was closed and opened again. Every attempt is bounded now, and the watch that was meant to catch this was waiting eight seconds, which is longer than anyone waits.

The register line found one line, too. Everything on it shared a centre and still looked crooked, for three reasons measurement found and the eye only felt.

4 patches

  • 0.32.4The glass stops changing with the page behind it

    Every Lodestar surface is Liquid Glass, and glass shows what is behind it. Over a dark window that was fine. Over a white page the dark bar turned to a mid grey and its text thinned to below the floor Lodestar sets for anything read, and the pill, the smallest surface, fared worst. A veil inside the glass had been correcting the tone after the fact. It held the tone. It did not hold the weight.

    macOS 27 added a slider for how clear Liquid Glass should be, and photographing Lodestar at every position of it showed that the clearest setting, which is the default, was the one that read worst. The fix is not the slider. The glass is now tinted toward the system's own ground through the material itself, black on charcoal and white on paper, and the veil is gone. Over a white page the bar sits sixteen levels from its charcoal self and its text reads above twelve to one; the pill goes from three and a half to twelve and a half. The frost and the rim are as they were. The slider is left to you, and at its clearest Lodestar now clears its own floors.

    Nothing else changed.

  • 0.32.3Dictation stops opening a microphone that is not there

    The input your Mac calls the default is not always a microphone. A dock or a monitor can present one, take the default, and deliver silence, without anyone having chosen it. The draft follows the system, so it opened that silence on every dictation, and kept opening it, until the hardware happened to be unplugged.

    Now a device that delivers nothing twice is set aside and your Mac's own microphone is used instead. Being heard somewhere is better than being silent faithfully.

    The other half is that nothing used to say so. The recognizer's preparation has no time limit of its own, and when the speech stack is stuck it simply never answers, so the draft sat there reporting that the microphone did not start while the thing that would have started it was waiting forever. Every step of opening the microphone now has its own deadline and names itself when it gives up, which is also why you will hear about a real failure in a few seconds rather than after a long silence.

  • 0.32.2The microphone stops going deaf after an update

    Updating Lodestar has been leaving dictation silent, on and off, since 0.25.0. You would open the draft, speak, and get nothing: no words, no meter, no error. It usually came back after a few minutes, or after quitting and reopening, which is why it read as flakiness rather than as a bug with a shape.

    It has a shape. An audio engine can start, report that it is running, and deliver no sound at all, and nothing about it looks wrong from the outside: the same microphone, the same format, no error. The minute after an update is when one gets built that way. And because keeping a warm engine is worth a second of startup, that deaf one was kept and restarted for every draft that followed.

    Now it is watched instead of trusted. An engine that claims to be running and delivers nothing for a second and a half is rebuilt on the spot, in the middle of the session, so you lose a moment rather than the sentence. A session that hears nothing at all is not allowed to hand its engine on to the next one.

    This is also most of the reason three in ten dictations used to settle no words.

  • 0.32.1Dictation and the hand, in the order they happened

    The recognizer runs a few seconds behind your voice, so typing while words are still being worked out is the ordinary case, not an edge one. Three things were wrong with it.

    Taking a word off something you had just said brought the whole thing back. The words would go, correctly, and then the recognizer would finish and paste the entire utterance in again on top of the edit. For an unbroken dictation that is the whole session. A result whose words you have already edited is now discarded, which is what it always claimed to do.

    Words spoken before you started typing could land after what you typed. The reservation that keeps the order only existed once the recognizer had shown something, and it shows late. Now a key pressed while the microphone is hearing your voice reserves the place too, so what is still being worked out goes in ahead of what you typed. Speak, type while it catches up, speak again: it comes out in that order.

    And a typed word ran into the spoken one before it. Say a sentence, type the next word, and you would get `columnand`. Typing now joins by the same rule speech has always used, which also keeps punctuation attached and does not double a space you typed yourself.

    Also: the keys behind `lode ?` no longer come back on their own. A draft closed with them open used to reopen showing them.

0.31Minor · September 11, 2026

One door to the keys, and everything that spoke joins the voice

lode ? is the one chord that shows the keys of wherever you are: the whole system at idle, a lens's keys inside the lens, a bar's inside the bar, the settings window's over it. A plain question mark opens nothing any more, so it is only ever a character. The launcher, Ask and the commands bar carry no legend now, and no guide carries an instruction line: the keys live in one place, and that place is complete.

The keys are not a sheet beside the thing they belong to. A bar grows to hold them beneath its rows, in its own glass, and the pill grows around its row, which stays put as the foot of the card. It is the one motion in Lodestar: three tenths of a second on the system's own curve, no overshoot, the glass leading and the keys fading in a beat behind its edge. Reduce Motion shows the result in place.

Everything that spoke now speaks in the voice. A launch that takes time stands as the pill in an opening mode, and only after a third of a second, so a running app's summon never shows it. The meeting is a sentence: begins in four minutes, begins in 45 seconds, is beginning, began three minutes ago, with Join and Dismiss on the two chords every ask answers to. The boot ask for Accessibility is the same card with no keys, because until the grant lands no key reaches Lodestar. The walk's eight lessons say what each is for in a sentence and draw the keys they teach as rows beneath, in a new order that ends on the sheet, with the clipboard just before it. The chain guide's header is the chain so far drawn as the keys it is, led by the wind when the chain is a breath, and a breath's rows are its apps and nothing else. The last text on the glass that trailed off is gone.

2 patches

  • 0.31.2The pulse learns shape

    A mean and a standard deviation describe a bell and nothing else, and the interesting part of a motor measurement is in its tail. The health pulse keeps shape now, under the line it has always been under: what that line forbids is key identity, and a shape is not an identity.

    Hold time goes in beside the counts, press to release. It is the one keyboard measurement with a clinical literature behind it, and it asks for nothing the line forbids, because how long a press lasted is not which key it was. A press the system repeated is never timed, for the same reason its keydowns were never counted.

    The pauses stop being thrown away. A gap past the motor ceiling used to be dropped so that thinking time could not contaminate a motor number, and now it is kept beside it instead. The old numbers mean exactly what they always meant. The tail is simply no longer lost.

    Bouts are the unit the hands actually work in. A bout ends when the hands stop for longer than ten minutes, and every pulse now records where in its bout it sat. Whether the hands drift as a bout runs on is worked out when you read it, each bout measured against itself first, so a long day cannot pass itself off as a slow hour. The answer comes with its own error, and where the error swallows the effect the printout says flat rather than dressing up nothing as something.

    The day's shape is read with the measures the sleep literature settled on for exactly this kind of record, and the day begins at four in the morning, or an evening that runs past midnight is cut in half and counted as two.

    `lodestar observations` shows all of it. None of it is judged: a rhythm is described, and what you want your rhythm to be is yours.

  • 0.31.1The pill comes back to its own size

    The pill grew around its row to hold a lens's keys and then, when the keys went, kept the width it had grown to: the departing columns were still asking the glass to be wide enough for them while they faded. Their edges come off before the glass shrinks, so the pill returns to the row's own width and height, and a test holds it there.

0.30Minor · September 11, 2026

A placeholder is the interface asking, not the hand answering

Mono is the hand's face, reserved for what a person typed. The empty launcher, Ask, commands bar, clipboard search and settings fields were showing their invitations in it too. Every placeholder now wears the interface's sans at the field's size and the quiet tone, set through one door in the theme, and the drift guard refuses a bare placeholder from here on.

15 patches

  • 0.30.33A card's header is one line

    The clipboard card's key, its count, its source and the source's icon were each placed from the card's top on their own arithmetic, and the icon sat four points below the rest. The four now share the key's midline, which is what makes a header read as a line and not as three things near the top.

  • 0.30.32The strip and the settings window speak the language

    Three faces, one per speaker, and a face is never borrowed: the interface in the system's sans, the hand in mono, Lodestar in New York. The launcher, Ask, the commands bar, the strip's search and the settings fields are mono now, so what you typed is told from what the app says at a glance. One ladder for rounding, each rung the one above over phi squared, and every corner in the app sits on a rung.

    The clipboard's addresses are drawn as the keys they are: the same cap on every card and every pin that the guides and the sheet draw. A card's header is the pill's trailing wing. The settings window's pane numbers and row letters are the same caps, its headers speak in the body voice rather than in capitals, its choices are named as names, and its legend is gone: a plain question mark shows the window's keys on the sheet, as it does inside the strip and inside every lens, and escape takes the sheet down before it closes anything.

  • 0.30.31Lodestar has a voice, and the coach speaks in it

    The coach's chip used to put its offer on a key row and its answers in a footer. Now it speaks: the offer as a sentence in the serif, Slack could be one key away, with the keymap drawn as the keys it is beneath it and the measurements beside them in the interface's face. Forty-one searches, about ninety seconds a week, about an hour a year: the same number twice, once as measured and once at a scale a person can feel. The two answers are named as the verbs they are, Accept and Decline. A decline is answered in the same voice, once, and then the glass is clear; the offer sleeps a season.

    The voice is New York, the system's own serif, and it is reserved for sentences Lodestar says when it asks, teaches or reflects. It never says I. It says you. It names Lodestar only where Lodestar is the subject, so an update on its way says so and the start of a session says only that it is ready when you are, with the way in drawn as the keys it is. A fact stays in the interface's face, so the two speakers are never confused, and no title ends with a period.

    Every flash is now one family with the pill. The glyph a flash opened with named its kind; the kind draws as a symbol in the pill's own configuration, and the line opens with a capital: refused, needs you, the clipboard, opening, done, the layout. Breaths wear wind, because a breath is taken and released, not filed. A breath saved says so in a sentence, with the windows it holds and the apps it brings back named the way a sentence names them.

  • 0.30.30Lodestar 0.30.30

    Three small things from the first day: a flash the width of its words, one ready instead of two, and a green check on every push.

    A one-line flash, the copied receipt among them, kept the guide's minimum width and left empty glass to the right of short words. A flash is now exactly as wide as what it says.

    After an update the relaunched Lodestar said ready, handed itself back to launchd, and launchd's own instance said ready again. The relay now holds its tongue: only the instance that stays announces itself.

    One image-door test read a display's size instead of the door's rule, and failed on the continuous-integration runner's small screen after every push. It zooms further in before it measures, so the picture's edge is never what it measures.

  • 0.30.29The pill fits what has been said

    The typing state reserved a slot ahead of the letters so the outline would hold still keystroke to keystroke, and with a short search that left a gap between the letters and the app's icon that read as something missing. The slot is gone: the pill is exactly as wide as its glyphs, the letters and their caret.

  • 0.30.28Lodestar 0.30.28

    A pick is seen where it is made, the anchor rides ahead of the far end, and the design language is held by a test.

    When a capital narrows the chips, the chips now say so: the letters already typed wear the accent on every chip they can still complete, and the chips they can no longer reach are gone. The reference is on the glass, where the eye is when it picks, and never in the pill.

    In select, once the start anchor lands, the anchored word rides ahead of the far end's search between the pill's wings, with a quiet dot between the word already taken and the letters being typed. The stage that a sentence used to announce is legible from the word itself.

    The pill can be dragged by its glass, the way the coach's chip can, and comes back where it was left for the rest of the session, kept on the screen. The sheet that ? opens is built on the pill's own proportions and voices: its insets, its gaps, headers in the body voice and never in caps.

    And the design language is now guarded the way the accent has been: a corner radius, a type size or a symbol configuration written into a surface as a number fails the build with the file named. Every one of them lives in the theme, and the last stray few were brought home.

  • 0.30.27Three corrections to the pill, from the first day with it

    The pill shows only what is being searched for. A capital is a pick, not a search, and it belongs on the chips it narrows, not in the text between the wings; it no longer appears there.

    The sheet inside a lens answers a plain question mark. Holding the mode key for it was one key too many, and a search was never made of a question mark, so the lens gives that character to the sheet. Escape still takes the sheet down with the lens up, and lode ? still works.

    The typed text stands upright. The italic was tried on the glass and did not look right, so the hand's words are set apart by size and weight alone.

  • 0.30.26Every lens wears one pill, and the sheet knows which lens is up

    Scroll, its aim band, click and select each had a band of their own, in its own shape, saying its own things. Now there is one object: a pill on the glass, floating where the guide has always stood, that every lens shares. Its left wing is the mode, a symbol and a word; its right wing is the app, a name and its icon, told from the mode by tone alone. Between them is what you have said. Nothing, while you have said nothing. A still hairline caret when the lens is listening for your typing, so the band says whether letters would land without carrying an instruction. And the letters themselves, in italic, the moment you have typed or aimed at anything, at which point both wings fold to their glyphs and the symbol and the icon stay exactly where they were. Nothing moves and nothing animates, because a mode indicator's one job is to be true the instant the mode is true.

    The pill carries no instruction, not even esc. The keys a lens owns are on the sheet: lode ? inside scroll, the aim band, click or select shows every key that lens answers to, and esc takes the sheet down with the lens still up. Outside a lens, lode ? is the whole system as before.

    Every dimension of the pill is its height over a power of φ, so one number sets the object and the next surface inherits it. The scroll guide's rows and their fade are gone with the band they stood on; the sheet is where the map lives now, one key away, for as long as anyone wants it.

  • 0.30.25The scroll guide is a band, and the map waits for a hesitation

    Scroll mode used to open a six-row panel over the pane being read, every time, including the thousandth. Now its resting state is one line along the bottom edge, in the same place and the same shape as select's band: the mode, the app, and the word the aim landed on, with the keys named quietly after them. The two lenses are siblings, and now they look it; opening the aim is the band changing its verb rather than one panel giving way to another.

    The map of keys still exists, above the band, but it waits. The same fade the bars' footers earn governs it, on the scroll verb's own count: a new hand gets the rows at once, a hand that has used the mode thirty times gets them two seconds after it hesitates, and a hand that knows its keys never reads them at all. An escape with nothing done in the mode is the stumble that brings the rows straight back for an hour. A map that always paints always gets read, and reading is reconstruction, not recall.

    The rows themselves read plainer: one separator where there were three widths of dot, and the aim row says what it does in the voice of the others.

  • 0.30.24The wheel is aimed by a word, and the lens ends when the hand leaves the keys

    Scroll mode always scrolled the same spot. Entering it put the pointer at the window's center, and a wheel event goes to whatever sits under the pointer, so the sidebar, the thread pane, the table header that scrolls sideways were all out of reach. The obvious fix was to find the panes, and it was tried and measured dead: a browser names none of them, not by role, not by scrollbar, not by any flag on any container, and it clips the geometry that might have given them away. Probing the pixels finds them, at the price of a second of visible twitching per point, and still misses a pane that is already at its end.

    So the panes are not found. Inside scroll mode, `/` opens the same band as `lode /`: type a few characters of a word you can see in the pane you want, and the pick lands the pointer on that word and does nothing else. No press, no focus, no copy. The wheel that follows goes to whatever scrolls under it, and the app decides what that is, because that is the question a wheel event has always asked. A word is the one address every pane already paints, in a web view, an Electron app or a native window alike, so the aim needs no discovery, no history and no cooperation from the toolkit. Uniqueness commits, so `/thr` lands on the one word that starts that way without a capital, and the letters you were still spelling are absorbed rather than read as scroll keys. The read covers the whole display, so the word may be in the window beside the one you are in, and that window scrolls without taking focus, which the trackpad cannot do without a click. Tab's pane cycle is gone; the record showed it had never fired, and the measurement showed why.

    The lens now ends the moment the hand reaches for the pointer. A click, or a swipe of your own, closes scroll mode the way a click closes the clipboard strip, because a mode left up under a hand that had moved on would swallow the typing after the click. Lodestar's own scrolling is told apart from yours, so the mode can never end itself.

    `0` and `$` jump to the left and right edges, the other axis of `gg` and `G`, for the boards and the wide tables the aim can now reach. And every session leaves one record: how long, which keys, whether the aim was used, and how the mode was left, so the lens is judged by its use and not by its share of all scrolling, which the trackpad will always own.

  • 0.30.23Lodestar 0.30.23

    The click door presses what the accessibility tree could not name, and spends its letters where typing cannot reach.

    A web page is not made of buttons. It is made of divs that press, images that open menus, rows that pick a channel, and the tree has no name for any of them, so the door's list of roles walked past them all: in one Brave window it named seventy-three pressables and missed ninety-one more, in Slack it missed the channel list entire. Now anything small enough to be a control rather than a card is asked the only question that matters, which is whether it presses at all. Only the innermost press counts, because the tree presses all the way up, and a chip on the card wrapping the row wrapping the button would put one letter over a whole region.

    A chip is not free. It is a word the eye must find and the hand must spell, and the door already owns a better address for most of a window: the text painted on it. So while a harvest fits in single letters everything wears one, which is the small window's whole experience, a dialog's three buttons each on one keystroke. Past that the letters go only to what paints no word — the presses the tree found by action alone, and the input boxes whose text is yours to write. A Brave window that drew seventy-three two-letter chips now draws ten single-letter ones, and the sixty-five that carry a name are reached by typing the name.

    The labels are three rows in one fixed order, read from the live layout so a chip always names the key that types it: the home row, then the top row, then the bottom. The hand never leaves home while a home key is unspent, and past it reaching up beats reaching down, ten keys to seven, on the row the fingers already travel for e, r, t, i, o and u. Twenty-six letters mean twenty-six targets answer on one keystroke where nine made every one of them two. The order never varies, because a chip that moved rows between windows would be a fresh decision every time.

  • 0.30.22The coach stops offering a breath you already have, and a breath used now leaves a trace

    A saved breath that holds both apps of a pair answers the finding. The coach reads every saved layout, not just its letters, and a pair it already holds is tested but never offered, whichever letter it lives at and whichever order the switches ran. The letter is the hand's to choose; the combination is what the coach cares about, and a combination that exists has nothing left to say but "use it".

    A pair is named in one order. The ledger once keyed a breath by whichever direction dominated the fortnight, so a breath accepted as one app and another could return a week later as the other and the one, a brand-new finding with the same two windows. Now both directions are one entry.

    Restoring a breath is recorded, and the record names every app in the layout it brought back. Before this a breath left no mark in the log at all: the coach could offer one, watch it be accepted, and never learn whether it was used. The use travels with the apps rather than the letter, so rebinding a breath to a new key keeps its history.

  • 0.30.21The mirror learns to price the pointer, dictation, and what was left undone

    The mouse now measures its own reach, not just counts it. From the tap's motion the instrument reads the parts a click has always been assumed to cost: the homing off the keys, the travel, the settle onto the target, the press, and the trip back to the keys, with the path the pointer drew against the straight line it needed. Positions never leave the tap's thread; only seconds and distance do. The overhead's pointing line reads as measured once most of a window's clicks were timed, and the older trip flag gives way to the reach that began after a keystroke, read from motion instead of inferred from order.

    Dictation joins the scorecard it was missing from. Every spoken draft's open time is priced against the words it kept at a natural speaking rate, so a draft that landed nothing is dictation's overhead the way the backspace loop is typing's. Beside the pointing pool stands a new abandonment view: each surface's share of openings that ended in nothing, and the seconds they cost, gathered from the giving-up every surface already logged and summed at last in one place. The draft's fixed cost is split by whether the speech model was warm, so the value of keeping it warm is a number rather than a guess.

    A held key is no longer read as typing. Autorepeat keydowns, which the system emits every thirty milliseconds while a key is down, now mark the minute present and count as neither keystrokes nor rhythm, so an evening with a key held reads as presence and not as a hand typing faster than any hand can.

  • 0.30.20The door answers the home row, and the row is whole

    Inside the image door, h j k l slide the picture and shift slides it three times as far, scroll mode's own stride; plus and minus zoom about the center of what is shown, and = reads as plus without the shift. And the strip's recents now run the whole home row, semicolon included, ten labels of which a display shows as many as it has room for at a readable card: a MacBook shows the six it always did, a wide display the rest.

  • 0.30.19The door takes focus, and gives it back

    A pinch reaches the active application and nowhere else, not the window under the pointer and not a watcher outside it, so a door that stayed behind another app zoomed for nobody, twice. The image door is now the one surface in Lodestar that takes focus. The strip and the draft never do, because what they do lands in the app behind them; the door's result lands nowhere but the picture, so taking focus costs the hand nothing. The app it took focus from is remembered and gets it back the moment the door closes.