Bolt 0.1.160

Bolt 0.1.160

Screening protects you without being switched on first. The layer that
masks sensitive information before it reaches an AI assistant shipped
inactive: it waited on a setting only an administrator could apply, and
the only way to apply it was a console command. A protection nobody
turns on is a protection nobody has. On the assistants people actually
use it is now active from the start, and it tells you each time it has
acted.

New features

Screening is on by default on the major assistants. What you type,
paste, drop or attach is checked before it leaves the browser, with
nothing to enable first. If you would rather it stood down on a
particular site you can decline, and that choice is remembered for
that site.

Every masked send says so. When something is covered, a small marker
appears in the corner naming how many items were caught, with a way to
see what they were. It clears when you dismiss it, or on its own after
a minute. Masking that happens silently asks you to take our word for
it. This is the receipt.

A file that cannot be screened no longer breaks the page. When
sensitive content was found in a file but no masked version could be
produced, the upload was cancelled outright and the site was left
waiting on a request that never answered. The file is now replaced
with a short note saying what happened, the conversation carries on,
and the original file stays on your machine.

Screening follows the content, not the shape of the request.
Assistants send in several different ways, and the check used to
depend on recognising one of them. What matters is whether you typed,
pasted, dropped or attached something, so background and streamed
sends are covered on the same terms. Ordinary diagnostics are left
alone.

Administrators can set policy for each category of information rather
than one setting covering everything, can release a single flagged
item without lowering the bar for the rest, and can offer a way to
request approval instead of leaving someone at a dead end. A check
that cannot run no longer reports that content is safe.

A local model can be chosen as your primary model for chat, and is
remembered as your selection rather than treated as a fallback.

Improvements

The colour loupe on the ruler paints only the pixel it actually has.
It follows the unit you have selected, copying puts the colour on the
clipboard, and a reading that fails is now reported rather than
disappearing.

The launcher no longer lets a bare word like settings take over the
results list, holds back expensive work when the answer is already on
screen, and stops searches that are still running once you have
chosen one. The arrangement of the side rail survives between
sessions.

Signing out closes the gate that allows a request through during
startup. That gate exists for the moment before a session has been
established, and it was never closed on the way out, so the next
person to sign in on a shared machine inherited it standing open.

FileVault reads as on or off rather than granted. It is a property of
the Mac, not something Bolt asked you for, and sharing the wording of
a permission request implied otherwise.

Permissions are read from one place across Settings, the launcher and
the ruler, so the three cannot disagree about the same grant.

Fixes

A masked replacement could fail to arrive, sending the original
instead. The replacement was handed between two parts of the browser
in a form the receiving side could not open, so it fell back to the
untouched text every time.

The network filter panel reports what macOS actually answers rather
than what was last requested, and a policy pushed to a machine reopens
the question instead of silently overriding it. The guidance for
administrators no longer suggests a management profile can install the
filter on someone's behalf, because it cannot. Only the application
can, with the person present.

Security

Screening being inactive unless an administrator turned it on was
itself the exposure, and it is the change this release leads with.
Anyone running Bolt on a personal machine was sending to assistants
unscreened, whatever the policy said, because the layer that would
have caught it was never active.

Every build in this release was produced from a single fixed point,
and each platform was measured against the same recorded source
before it was signed. The macOS applications are signed and notarised
by Apple, for both Apple Silicon and Intel. The Windows installers are
signed with an extended validation certificate issued to Sparcle Inc.

Bolt 0.1.159

Bolt 0.1.159

Colour picking works. The eyedropper shipped in an earlier build could not
actually fire: the desktop shell broadcasts the cursor position every sixteen
milliseconds whether or not anything moved, and the dwell timer was restarted on
every one of those, so the hundred and fifty milliseconds it needed to elapse
never did. The check that was supposed to discard a stale sample compared object
identity against a value that was freshly allocated each time, so it could never
be true either. Dwelling over a colour now shows the swatch and its hex value,
the timer restarts only when the cursor has genuinely moved, and a colour that
cannot be read says so instead of failing quietly.

New features

Colour is a real verb on the ruler overlay. Hold the pointer still over any
pixel on screen and Bolt reads it, shows the swatch, and offers the value in the
formats you are likely to want. A single click samples immediately without
waiting for the dwell. Where a sampled colour is close to one of your design
tokens, that token is named alongside the raw value, so a screenshot of a
product can be traced back to the palette it came from. The pixel itself comes
from a new native path rather than a screenshot round trip, which is what makes
the reading immediate.

Bolt speaks the current Model Context Protocol. The client now implements the
2026 revision alongside the existing one, so servers written to either will
connect. Servers that run as local processes are supported over stdio, with the
spawned process given no window of its own. Import asks before it acts: when a
server is added, the tools and permissions it brings are shown for confirmation
rather than being enabled silently, and a picker lets you choose which of a
server's tools are exposed. Cancellation and progress are wired through, so a
long running tool call can be stopped and reports how far it has got.

Improvements

Messages in a conversation stay in the order they happened. Reopening a chat
used to sort some rows by an internal counter that resets, which could place a
turn from weeks ago among today's. Every message is now anchored to its real
time when the conversation loads.

Typing a command in the launcher consumes the text that summoned it. Previously
the stem you typed could survive into the command you had just opened, so the
first thing a command saw was the word used to reach it. That now happens in one
place for every command rather than for the thirteen that had special cases.

Fixes

The Integrations page could be taken down by a connected server that published
two tools with the same name. The page reported that something had gone wrong
and suggested retrying, but the tool list was identical every time, so retrying
could never work. Duplicate names are now handled where they are read.

Logging out and back in no longer leaves work running in the background. A
liveness timer and its listeners were registered again on each sign in without
the previous set being released, so the beats compounded with every cycle. Icons
that failed to extract were re-requested without limit, which flooded the bridge
between the interface and the desktop shell and could freeze the window shortly
after a second sign in. Both now release what they registered.

A file input in the embedded browser could close the application instead of
opening a chooser. The dialog code treated a panel it could not create as
something to abort on rather than a case to handle.

Bolt no longer takes a place in the Dock or the application switcher without a
window to show. On the path that deliberately starts Bolt hidden, the window was
reported as visible, so under the setting that shows Bolt only while it is open
it appeared in the switcher with nothing behind it and selecting it did nothing.
The window's real state is reported now. A launch that has already raised the
window also no longer leaves a second raise waiting to interrupt you later.

Security

Bolt publishes a security contact and a vulnerability disclosure policy. The
contact is served at the standard well known location and from inside the
desktop application itself, so it is reachable even when the machine is offline.
The policy states what is in scope, what to expect from us and when, and the
safe harbour we extend to researchers acting in good faith.

Dependencies carrying published advisories have been updated, including the
object store library used for file handling. Tokens held for connected accounts
are encrypted with a modern authenticated construction, and the key used is
derived per record rather than shared. Deployments that enforce device posture
can now require it as a condition of access, and an inventory that returns only
part of its result is treated as a failure rather than as an empty answer.

Connecting a Google account asks only for what has been approved. A request
used to be merged with every permission the account had ever granted, so a
tester who had once approved something broader carried it into each later
connection and met a warning screen that could only be cleared by revoking the
application by hand. A request is now exactly what the application declares.
Where an organisation supplies its own Google client, the permissions asked for
follow that client rather than the one we host, so a deployment is no longer
narrowed to our own read only set.

Every build of this release was produced from a single immutable point, with
each platform measured against the same recorded commit before it was signed.
The macOS application is signed and notarised by Apple. Windows binaries are not
yet signed; that work is tracked and will follow.

Bolt 0.1.158

Bolt 0.1.158

Image search returns results again. A change of vision model in 0.1.155 moved
the score range that image matches are measured against, while the relevance
thresholds stayed calibrated for the previous model. Real matches were found
and then discarded before they reached the screen, so image search came back
empty and the launcher went on saying it was still searching. Three separate
thresholds turned out to be holding the old model's numbers, in two different
places, and the first two attempts each left one of them behind. All three are
now corrected against measured scores from the current model, one duplicate
relevance policy is deleted outright so that relevance is decided in one place,
and the thresholds that remain are pinned by tests so they cannot drift back.
Indexing, text recognition and keyword search were unaffected throughout. The
launcher's row of image results is rebuilt around that fix, voice input leaves
Labs and gets a proper home in Settings, and the on-screen ruler gains angle, a
diagonal reading and real-world scale calibration.

New features

Your images now reach the launcher even when the vision model is not there at
all. Reading text out of a screenshot needs no model, no download and no GPU,
and those words are already in the index, but until now the whole row of image
results depended on the vision engine and vanished with it. On a machine where
the vision model is switched off, still downloading, or not available for the
platform, searching for words that are visibly inside your screenshots now
returns them. Where a thumbnail has not decoded yet, each tile says what it is
and why it matched, carrying its filename and either a text or a similarity
chip, and that label steps aside the moment the picture itself arrives.

Voice input now lives at Settings, Desktop App, Voice input, instead of being
hidden behind the Labs unlock. The panel tells you what is actually true on
your machine: whether the platform is supported, whether the model is
present, and whether the microphone is available. Nothing is downloaded until
you switch voice on, the exact size is stated before you click, and you can
switch between the Standard model (about 148 MB) and a higher accuracy model
(about 488 MB), re-verify a downloaded model against its published checksum,
or remove it to reclaim the disk. Downloads resume after an interruption and
can be cancelled. On-device speech to text is available on Apple Silicon Macs
and on Linux.

The on-screen ruler measures more than distance. The two points you already
place now also report the angle between them and the drawn diagonal, with a
live pointer readout and Cmd+C to copy. A new inline Set scale field turns
one known real length into a calibration, which is what finally makes inches,
centimetres, millimetres and points correct: until you set a scale those
units are marked as approximate rather than claiming a precision they do not
have. The ruler toolbar is rebuilt at a fixed width so it no longer reflows
as you change units or modes.

Quick answers in the launcher are richer. A question about a country
statistic is answered from World Bank structured data when both the country
and the indicator are unambiguous, and stays silent otherwise rather than
guessing. When the source contains a leading figure it is shown as a headline
stat above the answer, and the answer pane can now show a corroboration
scorecard and a trend sparkline alongside the sources.

Discover gains two lanes. One query field with In catalog and Everywhere tabs
beneath it, filtering the catalog server side with a real per-category match
count instead of narrowing a preview slice in the browser.

Administrators can connect AWS Bedrock as a model provider from the admin
Add Model form, using either detected server AWS credentials with no secret
stored in Bolt, or manually entered keys. Auto routing gains department, role
and group routing overrides with a live readout of the effective order, plus
a Complexity sensitivity control with three presets.

Improvements

After a change of vision model, Bolt has to re-embed your image library from
scratch. That rebuild now runs at a faster, still bounded pace while a real
backlog exists, so on a consistently busy machine it finishes instead of
parking indefinitely, and the rebuilding indicator clears when the rebuild is
genuinely done rather than staying on afterwards. It also no longer pauses
over images it has already done, which on a large library was the bulk of the
work it was doing. Foreground work still takes priority, and the rebuild now
recognises more of what counts as foreground: opening a preview, scrolling the
thumbnail strip and drawing list icons all push it back, where previously only
typing a search did.

Voice transcription is several times faster on Apple Silicon. The speech engine
was built without GPU support and was asking for every core on the machine, so
a two second phrase could take eight to fifteen seconds. It now runs on the GPU
and asks for a share of the cores rather than all of them, and it records how
long each transcription took so a slow one can be recognised as slow.

Voice input is more honest about what it is doing. The model is warmed when
you enable voice, or at launcher start if voice is already on, so the first
press does not sit behind a long silent load, and a cold load says Preparing
voice rather than showing an unexplained spinner. On macOS, Bolt now opens
the microphone the system considers default instead of the first device that
answers, which is why selecting a different microphone in System Settings
previously changed nothing.

First-run folder setup no longer fails as a whole when one folder cannot be
listed, for example a disconnected network share or an iCloud folder that has
not finished syncing. That folder is skipped and named, with the reason
stated, and the rest of your selection is granted.

Recall is offered more often for catch-up phrasing such as recap my day,
what is new, or catch me up. It still asks for confirmation before it runs.

The browser extension banner now leads with what the extension protects
rather than what it can observe.

Bolt writes far less to its log files. A per-invoke warning that was
producing tens of thousands of lines an hour is bounded, and trace-level
logging is no longer compiled into release builds. Support-level logging is
unchanged.

Security and compliance

Production deployments now connect to PostgreSQL over TLS. A misplaced key in
the shipped production configuration meant the setting was silently ignored
and connections fell back to no transport encryption. The key is corrected,
and an unrecognised key in that section is now a startup error rather than a
silent downgrade. If you run Bolt against your own PostgreSQL, this is the
one item in this release worth reading twice.

Content data-loss-prevention policy can now be aimed at a department, role or
group rather than applying at one strength to everyone, reusing the same
identity dimension that routing overrides and budget quotas already use. An
empty configuration behaves exactly as before, and a principal that cannot be
resolved falls back to the strictest configured level.

The compliance record is more complete. A data-loss-prevention override now
reaches the sealed, exportable audit chain instead of only a metrics table, so
an administrator can hand an auditor evidence rather than a count. Where an
exact-data-match policy fires, the sealed record cites the customer's own
dataset and rule that matched, without ever recording the matched value
itself. Bolt now reports the detection depth the running process actually has,
rather than what its build flags imply, so a build whose classifier model
failed to load no longer reports advanced detection as active.

macOS could keep showing the microphone as in use by Bolt after a transcription
had finished, with nothing recording. The recording indicator is a privacy
promise rather than a cosmetic detail, and an app that still reads as listening
after you let go is indistinguishable from one that is listening. The audio
stream is now stopped explicitly rather than left to be cleaned up, and a press
whose release never arrives can no longer hold the microphone open without a
limit. The same fault had a second effect worth naming: a capture Bolt was
still holding made every later recording come back as pure silence. If that
ever happens again, Bolt now says that it is holding the device itself and that
restarting will clear it, rather than telling you to go check a microphone
permission and an input device that were never the problem.

Two dependency advisories are closed in document and spreadsheet parsing, in
the PDF and Excel extraction paths. Separately, the local plain-HTTP listeners
now refuse HTTP/2, a protocol nothing on the loopback interface asks for,
which puts a known HTTP/2 issue out of reach on that path.

Decoded clipboard images written to a temporary file during indexing are now
created with owner-only permissions rather than inheriting the process umask.

Fixes

Fixed image search returning nothing, described above. It took four corrections
rather than one, because the same miscalibration had been copied into more
places than anyone had counted. The first corrected the thresholds inside the
search engine; the strictness setting called strict survived that one and needed
a second. A third threshold was then found in the launcher itself, dropping
every image result out of Top Matches on its own, and a fourth check alongside
it was carrying an entire second copy of the relevance policy and rejecting
every match unconditionally. That duplicate policy is deleted, because relevance
belongs in one place, and the threshold that does a real job is retuned to the
same number the engine uses so the two cannot drift apart again.

Fixed the launcher's row of image results, which had a set of faults of its own
sitting on top of that one. It c...

Bolt 0.1.157

Bolt 0.1.157

A reliability release focused on app freezes. We found and fixed every unbounded-wait
class we could identify that could make the app stop responding — background file
indexing, local file browsing, the embedded browser, and Vault/secrets search all now
have hard bounds, so a slow or disconnected drive can no longer freeze the whole app.

Improvements

The embedded browser now recovers automatically if a tab's page process crashes,
instead of staying permanently blank. It can also open local files (like an HTML file
or a Markdown file on your Desktop) directly.

Background file indexing (on first launch and ongoing) is now bounded per scan
location, so one slow, disconnected, or not-yet-synced folder can no longer stall
indexing for every other folder.

Local file browsing and search-as-you-type are now bounded against slow or stalled
drives, instead of freezing while waiting on one unresponsive path.

Fixed a screen-ruler bug where opening it would flash and lag, and closing it would
unexpectedly bring the full app window back to the front — even if you were in zen
mode or had the window hidden.

Security and compliance

Updated the h2 (HTTP/2) library to close an advisory allowing unbounded memory growth
from a malicious server response.

Fixes

App-icon loading and file-browser metadata no longer share one pool that a single
stalled network drive or un-downloaded iCloud file could exhaust for the whole app —
they're now bounded separately, each with its own timeout.

Reduced false-positive freeze reports for windows that are legitimately idle and
hidden (e.g. running in the background) — this doesn't change what you see, only what
we're alerted to internally.

Upgrading

No action needed. Existing installs update automatically.

Bolt 0.1.156

Bolt 0.1.156

A reliability and correctness release. The launcher window now behaves correctly on
first install, background indexing work no longer competes with what you're actively
doing, and the Compare tool lays out correctly at narrow window widths. Plus data-
handling correctness fixes to two enterprise catalog connectors.

Improvements

Narrow windows now shrink the toolbar to icons instead of clipping it, so the row
stays usable and the subject text stays readable at any width.

Background screenshot re-indexing now runs at genuinely lower priority than your
foreground work, instead of competing for the same CPU cores.

App-icon loading is now bounded so a client requesting many icons at once can't
overload the app.

Security and compliance

Fixed a defect in one enterprise catalog connector where a room configured as
private could be indexed with an organization-wide-visible permission instead of
being scoped to that room only, and a related defect where a direct one-to-one
conversation's permission could resolve incorrectly. Both are now scoped correctly.

Fixes

The window no longer hides itself when you click away by default — that setting
("Hide on blur") now correctly defaults to off for fresh installs, and the matching
tray Settings menu item, which previously appeared to do nothing, now works.

Fixed the Compare (diff) tool leaving a large empty gap above the comparison panel,
and the two side-by-side panes not adapting to narrow window widths.

Upgrading

No action needed. Existing installs update automatically.

Bolt 0.1.155

Bolt Enterprise 0.1.155

This release fixes a freeze some users hit on first launch, adds saved-login
autofill inside Bolt's own browser (including multi-page sign-ins), and makes
the service meaningfully harder to overload under heavy use. Plus a batch of
smaller fixes and polish since v0.1.153.

New features

Saved logins fill themselves in, inside Bolt's own browser. Bolt now
recognizes a saved-login page as you land on it and offers to fill it, the
same way the browser extension does on the open web, including sign-ins split
across more than one page or step. The offer stays anchored to the tab it was
made for, so switching tabs mid-flow can't cross-fill the wrong site.

Sensitive clips stay off the record, everywhere. A clip you or an application
marks private is now excluded from clipboard history consistently on Mac,
Windows, and Linux, not just the platforms that happened to support it before.

Improvements

Bolt is measurably harder to overload. Requests are now admitted with a
budget on how many can run at once and how long one may take; when that
budget is exhausted, Bolt sheds the request immediately with a clear
retry-after signal instead of making it wait indefinitely. A stuck downstream
dependency (cache, database) can no longer starve every other request behind
it.

A window that used to open too large for your screen, or clipped on a smaller
one, now sizes itself to fit. Zen view's layout keeps its column aligned with
the window at any size, and its dropdown menus stay usable even at the
smallest supported width.

/help teaches as you browse it. Highlighting an entry now shows a plain
description of what it does alongside it, and the top of /help leads with a
clearer "type this, Bolt does this" example.

Search ranking. An app whose name matches a whole word or acronym in your
query now reliably wins the top result over partial matches.

Installing without administrator rights now works correctly on Mac, Windows,
and Linux, and a large download shows real progress instead of appearing to
hang.

Security and compliance

Windows can now read redacted regions inside an image for data-loss-
prevention scanning, rather than withholding the whole image. This closes a
gap where a screenshot or photo containing sensitive text could pass through
unscanned on Windows.

A residency control that previously accepted a setting without enforcing it
now genuinely refuses to process data outside the configured region.

Every automated enforcement decision (the AI features Bolt blocks, allows, or
masks) is now recorded in the sealed evidence chain administrators can audit,
not only some of them.

Administrators can declare their own sensitive data (a list of customer IDs,
account numbers, or similar) and Bolt's DLP engine can now match against it
exactly, with the matching rules and their strictness controlled by admin
policy rather than fixed in the product.

Fixes

Fixed a freeze on first launch. Caching app icons for the launcher could open
many database writes in a short burst on a fresh install, which could stall
the window instead of finishing quietly in the background. Bolt now keeps
this bounded regardless of how many applications you have installed, and
falls back to working entirely in memory for the rest of the session if it
ever can't write to its local cache at all, rather than retrying
indefinitely.

• Fixed a preview panel that could shrink to nothing; it now keeps a minimum
  usable height.
• Fixed a successful server response occasionally being reported as a
  network error, and a login handshake that could get stuck partway through.
• Fixed live updates not reconnecting after signing back in without
  restarting the app.
• Fixed the app getting stuck showing "disconnected" with no way to recover,
  and no longer treats a brief local network blip as proof the service is
  down.
• Fixed a failed cloud file preview being retried endlessly instead of
  showing as unavailable.
• Fixed an overlay opened from Zen view keeping Zen's size instead of sizing
  itself correctly.
• Improved search matching when setting up two-factor authentication.
• Fixed "Open in Bolt" carrying a file over: opening a file this way could
  fail with "That file was not carried over," and its preview could fail the
  same way, on every attempt.
• Fixed visual search only finding screenshots on a fresh install or after a
  model update. Your own photos and other images are now included from the
  first index pass, not just after a restart.

Upgrading

No action needed for new installs. If Bolt is currently frozen or
unresponsive after installing or updating, quit it and reinstall:
curl -fsSL https://sparcle.app/install.sh | sh. This replaces the app with
the fixed version; simply reopening a frozen install does not, on its own,
guarantee you get the fix before it freezes again.

Bolt 0.1.154

Desktop binaries for Bolt v0.1.154. Install: https://sparcle.app/download

Ship progress (auto-updates during release):

             status
  mac-x64     ✗    

Bolt

Desktop binaries for Bolt v. Install: https://sparcle.app/download

Bolt 0.1.153

Bolt 0.1.153

Zen and Full remember where you put them

• Full mode opens at the actual size of your work area. It used to open at a fraction of the screen, which on a large display left a visible margin that looked like a bug.
• Your window geometry survives a restart. Full mode could lose its size and position on quit; Bolt now flushes the geometry as it exits, including the paths that restart the app rather than quitting it.
• On more than one display, Bolt resolves the right monitor at startup. Reopening on a secondary screen could clamp the window against the wrong display's bounds.
• Zen and Full keep separate geometry. Switching between them no longer drags one mode's size onto the other, and the switch itself no longer animates through an intermediate size.
• Switching modes hides the reflow. The content is veiled for the moment the native window is resizing, so you see the new layout rather than the page rearranging itself.

Bolt fits the screen you actually have

• The default zoom now accounts for your screen. On smaller or lower-resolution displays Bolt starts at a readable size instead of one tuned for a large monitor.
• Full mode on an ultrawide no longer stretches every surface edge to edge. Reading width is constrained where it helps — the chat column — and left alone everywhere else.
• The chat composer lines up with the messages above it.
• The left rail has one width authority instead of two that could disagree, which is what made it appear to jump.

The browser extension protects more, and interrupts less

• Severity decides whether a file interrupts you at all. A low-risk finding no longer stops what you are doing the way a serious one does.
• Three visually distinct states, and red only means a refusal. A warning no longer looks like a block.
• A slow scan reads as slow, not as a block. There is a latency budget, so waiting on a scan is visibly waiting rather than looking like a refusal.
• Picking several files at once keeps all of them. A multi-file selection used to be replaced by the last pick instead of reconciled with it.
• An oversize file is no longer released and painted red at the same time — it said "blocked" while letting the file through.
• The file guard now covers the same ground as the typing guard, including the corporate-host exemption, rather than protecting one path and not the other.
• Where a Block cannot reach is stated at the point an administrator chooses it, instead of appearing to cover everything.
• The extension's own input guard uses Bolt's in-page notice rather than a native browser dialog.

Open in Bolt carries the file

• Sending something to Bolt from the browser now hands over the file itself, not just its name, through a single-use staging handle. What Bolt scans is what you sent.

The search bar holds still

• The header no longer grows and shrinks as you focus and unfocus the search bar. Settings has moved into the avatar menu, and the avatar is always visible at a fixed width instead of sliding out of a drawer.
• The avatar sits inside the input card rather than floating outside it.
• Search ranking no longer breaks ties alphabetically by internal id, which had let one kind of result quietly outrank another for no reason a person would recognise.
• What you picked last time wins a tie. When two results match a query equally well, the one you chose before is preferred, so typing password settles on the thing you actually meant.

Fixes

• Updating Bolt no longer depends on reaching Apple at install time. The update package now carries its own notarisation ticket, so it installs on a Mac that is offline or on a restricted network instead of being refused.
• "Open in Bolt" carries the file again. The endpoint that redeems a handed-over file was unreachable, so every attempt reported "That file was not carried over". File preview was affected the same way.
• Bolt installs without administrator rights on all three platforms.
• The pinned-shortcuts rail scrolls by click-drag outside edit mode.
• The Zen/Full minimum-size floor scales with your zoom level, so a zoomed view no longer fights the window's lower bound.
• Clicking an option in a searchable dropdown does something again. In lists long enough to show the filter box, the click was being swallowed.
• The window controls no longer sit on top of a note's title, and Zen mode respects auto-hide.
• App results in search are typed correctly, so a .app is presented as an application rather than a folder.

Privacy detection is more precise

• Your own name and address are no longer flagged as someone else's personal data, and a job title next to a name no longer swallows the name itself.
• Role addresses at known vendors (support@, billing@ and similar) stop being reported as personal data.
• A file with a part we could not read is no longer treated as fully scanned. If an attachment contains an encrypted or corrupt section — a password-protected file inside a zip, say — Bolt now reports exactly that and holds the file as unscreened, instead of clearing it on the strength of the parts it could read.
• Incident records are scoped to your own organisation — a read can no longer return another tenant's rows.
• Our compliance documentation now describes SAML support as partial, in all three places that previously overstated it.

Under the hood

• Server-assembled prompt context is now scanned at the same chokepoint as everything else, so text the server adds to a request is inspected rather than assumed safe.
• The hybrid scanner forwards its refusal tier correctly instead of downgrading it.
• Bolt's desktop posture degrades a governance-pack refusal to a warning rather than a hard stop.
• The app's authoritative DLP posture is served to the extension, so the two cannot disagree about what is enabled.
• Security: the legacy TLS stack was removed from the build and the remaining certificate-verification library unified on a single current version, clearing four advisories (RUSTSEC-2026-0049, -0098, -0099, -0104).
• Faster startup app search on macOS, which now also finds the system utilities kept outside the normal Applications folder.

Bolt 0.1.152

Bolt 0.1.152

Bolt has its own vault

• Bolt no longer only reads your connected password managers — it can hold secrets itself. Generate a password with =pw and save it in one step, or create an entry by hand.
• Fill from the browser. Right-click a username or password field and fill it from Bolt. It reuses the same consent, origin-check and picker machinery that already guards 2FA codes, so a page script cannot fill a field on your behalf: every fill needs a real click from you.
• Save what you just typed. When Bolt sees a login form submitted successfully, it offers to save the credential. The offer waits for the submit to actually succeed, so a rejected or mistyped password is never stored.
• Save into 1Password or Bitwarden, not just Bolt. A login you save can be written into a
  connected external vault. Bolt creates the entry through the provider's own CLI and never puts
  the password on a command line. Other connected providers stay read-only for now, and the save
  dialog says so rather than failing quietly.
• A lock. Your vaults lock on idle and unlock with a PIN, covering every connected provider rather than only Bolt's own entries — so an unattended desktop does not leave your secrets open. The PIN is hashed with Argon2id and unlock attempts are rate-limited.
• Administrators can enforce it. The idle timeout and require-a-PIN can both be set by your organisation's policy. When they are, the setting shows as managed and read-only rather than being silently overridden.
• Secrets you mark as sensitive opt into sync automatically once the device is enrolled, with per-item sync status visible.
• On Linux, Bolt now stores secrets in the system keyring through the Secret Service API, alongside the existing macOS Keychain and Windows Credential Manager support.

2FA codes

• The badge shows Bolt's instant local answer first, then visibly continues pulling from your connected vaults, so a slow vault reads as still-searching rather than as a missing code.

Bolt works from the keyboard now

• Command mode is a real mode rather than a pile of shortcuts. Press it once and letters act instead of typing; the notch tells you which mode you are in.
• It survives navigation. Moving between pages with j/k/f keeps you in command mode: Bolt distinguishes a cursor you moved from one the app moved.
• Hints stay up after you act, so opening a menu and choosing from it takes one keypress. Hint labels sit clear of what they label, short hints are prefix-free, and the alphabet is wider.
• Search your hints. Type to narrow the hints on screen, collapse a group you do not want, and move between them by direction rather than by list order. A collapsed group is still findable by its own name.
• Nothing reveals itself on its own. In command mode the only thing that opens a panel is you pressing space, so the screen holds still while you aim. The notch holds its size and place, on every route.
• Hint mode reaches controls that only appear on hover — a delete button, a row action — handled in one place rather than control by control.
• Assign your own shortcut to any tile on the rail, and see it as a key badge on /help rows.
• z toggles Zen from command mode, and the notch says what f actually does: it finds, it does not click.
• Bolt's shortcuts work while a web page has focus. Chords typed inside the in-app browser reach Bolt's own handlers.

The rail narrows, instead of a second strip of chips

• Typing / or = now narrows the utility rail in place. The old scope and utility chip strips are gone, so there is one list of things to aim at instead of two.
• The keyboard lands on the rail as soon as you start narrowing — including when nothing matches yet — and arrow keys move along it. Step out with ArrowUp and ArrowDown brings you back.
• Narrowing searches the full catalog, not just what happens to be on screen, and /cmd chips are compact enough to see at a glance.
• In the app strip, arrow keys keep the selected app in view as they move.

Settings and help, from the launcher

• /settings and /help are real launcher scopes. Search every setting and every help topic from the same bar you search everything else, with Cmd+K and Cmd+? reaching them from inside the dropdown.
• Flip a setting without leaving the launcher. A toggle found by search is switchable in place, by click or by Enter.
• Help rows carry the key badge for what they do, and selecting one enters the scope or utility.
• A bare ? opens Help, and Cmd+? reaches the shortcuts you expect.

Policy as code, from the command line

• boltctl is a new command-line tool for administrators. Keep your organisation's policy
  as a git-tracked YAML file and validate, diff, apply, list versions or rollback it,
  without opening the admin UI or waiting on a Bolt release. It talks to the same admin
  endpoints the UI uses, so nothing about how policy is enforced changes.

Note it in Bolt, from anywhere

• Select text in your browser, right-click, and it becomes a note. Select text or a file in any macOS app and do the same from the Services menu.
• The page confirms it worked, with a button to open the note in Bolt, and tells you when a capture is being held because Bolt is not reachable. Held captures land when Bolt reconnects.
• A captured note is enriched with where it came from: the page, the app you were in, what else was open. That context goes into the note body as well as its metadata, so searching for it actually finds it.

Notes

• Apply labels in the composer and filter /notes by them.
• Mine, Captured and Shared are real facets, filtered in the database rather than over one page of results, so they stay accurate at any note count.
• Metadata stored alongside a note is preserved across saves, including keys written by other tools.
• Note previews render as clean text.

Reminders and Recall

• Reminders run on the same alerts backbone as everything else, with all four ways of creating one converged onto it. Duplicates are collapsed, silent reminders stay silent, and an unsynced reminder retries at startup.
• Recall can seal a day into a real note. The day's rollup becomes a note you can keep, offered once after a seal rather than interrupting mid-panel.
• Today at a glance is the first row of /recall.

Windows

• Keyboard shortcuts work immediately at launch. Ctrl+\, Ctrl+, and type-to-search no longer need a click in the window first.
• Cleaner shutdown and relaunch. The background service and the embedded database server are tied to the app's own lifetime, and Bolt waits for its port to be genuinely free before starting again — so a restart no longer meets a machine that looks busy.
• Running-app icons appear in the launcher strip, read from the executable on every path that needs them.

macOS

• Bolt asks to be moved to Applications when launched from a quarantined copy, so macOS permissions can persist.
• Bolt does not trigger system install prompts on its own.

Keyboard and screen-reader access

• The focus ring is visible on every control, including the primary sign-in button, with a check that keeps it that way.
• Every modal keeps the keyboard inside it, through one shared trap rather than per-dialog handling.
• Deleting a chat session, and other actions that appear on hover, are reachable by keyboard, and scrollable panes can be scrolled without a pointer.

Zen mode

• Zen and Full each keep their own window geometry. Switching between them restores that mode's own size and position instead of resizing the window around you, and Zen's layout is anchored to the top.
• Pinned notes open to a click and to keyboard focus, not only to a hovering pointer, and the Zen notch reveals itself on movement with the same keyboard parity — with a clearer icon and label.
• Zen Glance uses the same card treatment as everywhere else, the rail is no longer dimmed in Zen, and the rail's border no longer clips.

Speed and stability

• /apps is populated at the first frame from the warm app cache.
• Dragging the window edge to resize stays responsive, at any size and in any mode.
• The launcher's shape detection loads reliably in packaged builds, so results that depend on recognising what you typed are there from the first keystroke.
• A dialog you have closed no longer holds on to the keyboard — every keystroke routes to what is actually on screen.
• Badges re-measure against the window after you resize it.
• Visual and semantic search wait for a query long enough to be meaningful.
• Results paint once when settled rather than flickering through intermediate states, and a file preview recovers from a transient read error.
• A failure in one part of the screen is contained there, including in zen mode, and degraded areas recover on their own.
• Result identities are made unique where rows enter the interface, so no search provider can produce a collision, with a check that refuses any list keyed on something that could.
• Fixed a startup crash that could leave the app on its loading screen, and a false error flash on startup.

Privacy and security

• Scan a file for sensitive content before it leaves your machine. The browser extension's
  file guard now reaches the detection service, and it honours the same all-sites scope and
  exclude-host list the on-type guard already had, so administrators can point it at every site
  or hold it to a named set.
• Bolt's browser protection warns you, it does not stop you. A file that scans clean attaches
  automatically. A file Bolt cannot screen — an image needing OCR, or Bolt simply not running — is
  sent with a record rather than held. Anything flagged can be sent with one click, and that choice
  is always logged. Managed and enterprise block policies are unchanged.
• Local-storage encryption at r...