Changelog

Notable user-facing changes to Baudrun. Follows Keep a Changelog; versioning is SemVer. The per-commit history lives in git log and on the GitHub Releases page’s auto-generated “What’s Changed” lists; this file is the curated view of what actually matters to a user reading release notes.

Pre-release tags (vX.Y.Z-beta.N, vX.Y.Z-rc.N) trigger the same release workflow but publish under GitHub’s “Pre-release” badge and don’t displace the “Latest release” pointer. The [Unreleased] section collects changes as they land on main; it becomes the final stable entry at tag time.

[Unreleased]

[0.12.4] — 2026-05-21

Fixed

Windows boot no longer fast-fails when the graphics adapter isn’t available. v0.12.3 added a graceful handler for window- creation failures (log + system error dialog + cx.quit() to shut down cleanly), but the cx.quit() step turned out to be unsafe to call from inside gpui’s initial-setup closure: it re-borrows an internal RefCell and panics with STATUS_STACK_BUFFER_OVERRUN (0xC0000409) on its way out — fast-failing the process with the same exit code we were trying to avoid in the first place. v0.12.4 replaces cx.quit() with a plain return; gpui’s event loop idles with no windows, the error dialog still shows on Windows, and the process exits when the user closes the dialog and kills the residual idle process via Task Manager. Same survival pattern PortFinder uses to clear the winget validator on its arm64 sandbox. Unblocks microsoft/winget-pkgs#377384’s launch test, which hit this regression on every retry.

[0.12.3] — 2026-05-20

Fixed

Windows launches on machines without a working GPU no longer silently crash. When gpui’s DirectX renderer couldn’t acquire a graphics device — driver paused, headless session, GPU exhaustion, or (most visibly) the winget validator’s arm64 sandbox returning DXGI_ERROR_NOT_CURRENTLY_AVAILABLE — v0.12.2 panic-aborted the process with STATUS_STACK_BUFFER_OVERRUN (0xC0000409) before any user-visible feedback could surface. v0.12.3 catches the failure: it logs the underlying HRESULT, pops a Windows error dialog explaining what’s wrong, and exits cleanly. v0.12.2’s gpui git pin is also bumped forward — the upstream handles the device-not-currently-available case more gracefully on the new tip, so the dialog path should be rare in practice. Unblocks v0.12.2’s winget submission which hit this exact crash on the arm64 validator.

[0.12.2] — 2026-05-20

Fixed

Windows installs on machines without the Visual C++ Redistributable now work. v0.12.1 (and every prior Rust+MSVC build of Baudrun) shipped a Baudrun.exe that dynamically linked against VCRUNTIME140.dll, part of the Visual C++ 2015+ Redistributable. On a freshly-imaged Windows install — including winget’s automated validator sandbox — that DLL isn’t present, so the Windows loader bailed with STATUS_DLL_NOT_FOUND (0xC0000135) before any Baudrun code could run, and the user got Windows’ “code execution cannot proceed because VCRUNTIME140.dll was not found” loader dialog with no recovery hint from us. v0.12.2 static-links the MSVC C runtime into the binary via +crt-static in a new .cargo/config.toml, so the .exe is self-contained at the CRT layer. ~200 KB binary growth, no other behaviour change. Also unblocks the v0.12.1 winget submission (microsoft/winget-pkgs#376876) which was failing the validator’s launch test on this exact issue.

[0.12.1] — 2026-05-19

Changed

Windows MSI now ships for both x64 and arm64. v0.12.0 only carried an x64 .msi because cargo-packager’s bundled WiX 3.11 (2017) couldn’t pass candle.exe -arch arm64 — that flag was added in WiX 3.14. Switched MSI generation from cargo-packager to cargo-wix, which uses a system-installed WiX (set up in CI via chocolatey) and handles both architectures with one toolchain. The arm64 winget manifest entry is now InstallerType: wix with a real ProductCode, replacing the v0.12.0 NSIS entry whose half- machine / half-user registry shape was tripping winget’s Apps & Features validation. cargo-packager continues to own NSIS, .dmg, .deb, .rpm, .AppImage, and .pkg.tar.zst.

[0.12.0] — 2026-05-16

Added

Undo a profile delete within ~5 seconds. The Delete button in the profile editor now drops a toast carrying an inline Undo button alongside the existing “Removed profile X” confirmation. Click Undo before the toast fades and the profile is restored to its original id and timestamps — so any sidebar shortcut, log filename, or workflow note that referenced the old id keeps working. Doesn’t auto-reconnect: restore is about the saved config, not the live session. Mirrors the same Undo affordance that’s been on skin / theme / highlight-pack deletes since v0.9.5.
Live DTR/RTS toggle pills in the session header. Two pills next to the ⋯ button on a connected session, each carrying a small green dot when the line is asserted and a muted dot when deasserted (matches the visual language of the connection-state dot at the start of the row). Click to toggle mid-session — the serial port’s write_data_terminal_ready / write_request_to_send fires on the next write-thread wake-up (~50 ms worst case), and a footer pill confirms the new state (DTR asserted / DTR deasserted). Initial state at connect is seeded from the profile’s dtr_on_connect / rts_on_connect policies. Useful for RS-485 direction toggling, Arduino DTR-reset triggering, and firmwares that key off a line transition. The corresponding feature lived in the Tauri build but hadn’t been carried into the gpui rewrite — the usage/profiles page already documented “Live DTR/RTS toggle pills in the session header” under DTR/RTS, so docs and reality are back in sync.
Footer-pill confirmations for routine actions. Operations that previously succeeded (or failed) silently now surface a short message in the footer status bar — auto-clearing after 8 seconds for info / warn, 15 seconds for errors. New pills: font zoom (Font size: 14) on ⌘= / ⌘- / ⌘0, profile save (Saved / Save failed: …), session move (Session moved to new window), suspend (Session kept alive in background), connect (Connected to /dev/cu.usbserial-XXX @ 9600), reconnect after an auto-reconnect window (Reconnected), disconnect (Disconnected), and auto-reconnect give-up (Auto-reconnect to /dev/cu… gave up after 15 attempts). Restores the “the app talks back” feel that the Tauri build had and the gpui rewrite hadn’t carried over yet. Same colours and severity rules the existing connect-failure / session-log pills already used. The Settings window also gets a new toast on Log directory updated / reset (skin / theme / highlight-pack import + delete toasts already shipped).

Fixed

Settings save failures now surface as a toast. Previously a commit() error in the Settings window only made it to stderr, so toggling something on disk-full / permission-denied would appear to take but silently revert on the next launch. The Settings window now pops an error toast (Couldn't save settings: …) so the user sees the failure when it happens.

[0.11.0] — 2026-05-15

Added

Tokyo Night skin and theme. The well-known navy-and-blue palette in both pieces: a floating-card chrome with the canonical Tokyo Night Night background (#1a1b26), soft blue/cyan accents, and a subtle shell-bg gradient that picks up macOS-26’s glassy panel feel without needing actual backdrop blur. The matching terminal theme ships the 16-slot ANSI palette every Tokyo Night port uses (folke/tokyonight.nvim, enkia/tokyo-night-vscode-theme, alacritty, kitty, …). Light mode is the canonical Tokyo Night Day variant (cool paper-blue #e1e2e7, blue ink #3760bf), active when the system Appearance is light. 16th built-in skin, 15th built-in theme.
Collapsible sidebar. Click the ‹ chevron next to the PROFILES label (or hit ⌘B / Ctrl+B from anywhere in the window) to fold the sidebar into a 48px icon strip. The chrome buttons (›, +, ⧉, ⚙) stack vertically at the top; the right pane expands into the recovered width — useful when the terminal needs every column it can get. Click › (or hit the shortcut again) to expand back. The collapsed state is saved to settings, so a window that’s been collapsed stays collapsed across relaunches by default. Per-window state is independent — toggling one window’s sidebar doesn’t affect another’s, but the most recent toggle is what the next-launched window inherits.
Default profile icon in the collapsed sidebar. Each profile renders as a single Lucide square-terminal glyph — universally read as “command-line / serial console session” — colour-coded by status: muted by default, accent when selected, success green when connected, warn amber while reconnecting, danger red on a connection failure. Click selects the profile, right- click opens the same context menu the expanded row has, and a hover tooltip carries the name + port path so identity isn’t lost when names disappear. Custom per-profile icons are a future option; the default fits every profile for now.

[0.10.0] — 2026-05-14

Added

Foundry app skin — the Blueprint engineering-drawing treatment (grid overlay, sharp corners, all-caps mono labels) recolored to burnt orange. Dark mode is a deep amber ground with a warm ink grid; light mode is cream paper with a burnt-orange grid. 15th built-in skin.
Molten terminal theme — the matching half of the Foundry pair (like CRT / CRT Phosphor). A deep amber ground with a warm-biased ANSI set, sitting on the exact background the Foundry skin uses for its viewport. 14th built-in theme.
Double-click selects a word, triple-click selects a line. Double-click uses the terminal’s semantic word boundaries; triple-click selects the line’s printed content and stops at the last character — no trailing newline, so a triple-click copy doesn’t submit the line when pasted into a serial console.
Theme-driven terminal selection colour. The selection highlight now comes from the active theme’s selection / selectionForeground fields instead of a fixed blue-grey, so every theme — built-in or imported .itermcolors — shows its own selection colour, and it follows a live theme switch. The theme preview dialog now includes a sample line painted with the selection colour.

Fixed

Synthwave profile editor no longer renders as a magenta wash. A latent rendering issue on flush-edged skins with a coloured --shadow-panel (Synthwave’s magenta glow, specifically) caused the editor’s right pane to fill with the shadow’s colour rather than show through to the skin’s --bg-window. The wrapper shadow is now gated to floating-card mode where there’s a bg to absorb it; flush skins lose a shadow that wasn’t visually meaningful anyway (a glow around a flush-edged pane has no “outside the box” to fall on).

[0.9.7] — 2026-05-13

Added

macOS 26 / Liquid Glass skin. Floating-card sidebar and main pane lifted off the window edge with --shell-padding, separated by --shell-gap, with rounded corners (--panel-radius) and a transparent title bar that lets the shell gradient flow up to the traffic lights. The lights reposition to overlap the sidebar’s top-left in the new layout. Floating-card mode is opt-in per skin — every other ships flush-edged.
Auto-updater (detection-only). Boot-time GitHub Releases check with ureq + semver, run on a background-executor task so it doesn’t block startup. When a newer release is available, a small amber dot appears on the sidebar gear icon and on the new Settings → Updates rail row. The Updates pane shows the version, release-notes preview, and View release + Dismiss this version buttons. Dismiss persists; the indicator stays silent until a newer tag ships. By design we never download a replacement bundle — the user is always in control of when (and whether) to install.
Right-click context menu in the terminal pane with Copy / Paste / Select All / Clear. Copy greys when there’s no selection. Each row dispatches the same gpui action the keybinding does, so the two surfaces stay equivalent.
Cmd+A / Ctrl+A → Select All in the terminal. Spans the entire scrollback history through the bottom-right of the visible viewport — same semantics as xterm / iTerm2 / Windows Terminal.
Copy-on-select. The PuTTY-style toggle in Settings (existed but was dormant) now writes selected text to the clipboard immediately on mouse release.
Settings → Accessibility pane. Read-only summary of every OS-level preference Baudrun reacts to (currently Reduce Motion), with a per-platform pointer to the system setting that controls it. Discoverable via the filter under “accessibility”, “reduce motion”, “a11y”.
Settings → Updates pane. Moved out from under Advanced into its own rail entry alongside the amber-dot indicator chain.
Status bar event log. Connect failures, session drops, auto-reconnect status, session-log open / close, etc. surface in the footer with severity-tinted text (info / warn / error) and auto-clear after 8 s (info / warn) or 15 s (error). Same string mirrors to log::*! for stderr capture.
Active-feature chips in the status bar. Small HEX / TIME / LINE# / TO FILE pills on the right when the corresponding formatter or session-log capture is on for the connected profile. Flat (no border / no vertical padding) so they don’t grow the bar.
Session line counter in the status bar — counts newlines received this session, capped at scrollback_lines, resets on clear / disconnect / reconnect.
Scrollable profile sidebar. When the profile list overflows the viewport, a persistent scrollbar appears on the right of the sidebar wired to the same scroll handle. Survives skin changes.
Skin authoring expansion (~18 new tokens). Skins now author --titlebar-height, --titlebar-content-inset, --shell-bg (gradient), --shell-padding, --shell-gap, --panel-radius, --label-transform, --label-weight, --label-letter-spacing, --font-size-h1 / section / label, --scrollbar-thumb / -hover, --overlay, --accent-hover, --bg-terminal, --input-border-idle, --option-group-fg, --sidebar-divider, --panel-border, --shadow-floating, --shadow-panel. Examples in docs-next/public/examples/. Custom skins built against v0.9.5’s smaller variable set continue to work — missing vars fall back to sensible defaults.
Edit menu on macOS with Copy / Paste / Select All entries. Accelerator labels derive from the registered KeyBindings.
Settings → Shortcuts customisation rows for Copy, Paste, and Select All — rebindable like every other action.

Changed

Cmd+Q / Cmd+N / Cmd+, reach Windows and Linux too. The three system bindings now use gpui’s portable secondary- token so they fire Ctrl+Q / Ctrl+N / Ctrl+, on non-mac instead of the OS-intercepted Win / Super key. macOS menu accelerators still display ⌘Q.
Terminal Cmd+C / Cmd+V dispatched through gpui actions with Some("Terminal") key-context scoping. Replaces the old inline KeyDownEvent modifier inspection, which was fragile under focus routing changes. The new path also gates against accidentally hijacking Cmd+C inside a profile-form Input widget — gpui-component ships its own Input::Copy binding against the “Input” context.
Profile row width and corner radius driven by the active skin. Rows on every skin pin to a uniform width inside the sidebar’s padding; macOS-26 rounds them to match its floating-card aesthetic.
Selection background unified across rail-style widgets (profile rows, Settings rail, form tab bar). Hover no longer paints grey over the active blue while the cursor sits on the row.
Cargo deps: ureq + semver added for the auto-updater. dirs 5 → 6. thiserror 1 → 2.
JetBrains Mono Regular bundled on Linux so the terminal grid doesn’t depend on whatever monospace fontconfig happens to pick. Fixes glyph-width drift on minimal Fedora installs that don’t ship fonts-dejavu.

Fixed

Last terminal row clipped under the status bar with skin- driven title-bar heights. maybe_resize now subtracts the flush-edged title-bar height (or the floating-card pane padding) before computing the row count.
1-second lag on profile selection. The editor rebuild was running synchronously on the click-handler stack, blocking paint. Deferred onto cx.spawn_in with Duration::ZERO so the active- row blue paints immediately and the editor materialises a tick later.
Windows: stray console window suppressed plus three gpui invalid-window-handle errors that fired on quit.
Linux on Wayland: window corners grabbable for resize. Widened the hit-test margin so the SSD-emulating client-side decoration picks up corner drags reliably.
Linux on GNOME Wayland: window draggable from the title bar. Restored client-side title-bar dragging that the platform preferred over the missing Server-Side-Decoration protocol.
Settings → Accessibility → Reduce Motion status text now wraps inside its card instead of spilling past the right edge.
Settings → Advanced → Config Directory keeps the Choose… and Reset buttons inside the card when the displayed path is long. The path field truncates with a leading … so the meaningful tail (…/Application Support/Baudrun) stays visible.

Security

Skin / theme / highlight-pack import path-traversal hardening. User-declared id fields are slugified before they become filenames, so a JSON declaring "id": "../../foo" can’t escape the imports directory. Covers the three import stores (data::skins::import, data::themes::import, data::highlight::import).

[0.9.5] — 2026-05-07

A long iteration cycle (nine alphas, seven betas) covering a Settings overhaul, a docs-site rewrite, and a sustained pass on Linux + Windows rendering quality. Highlights below; the per-commit story lives in git log.

Added

Settings is now its own Tauri window rather than a modal over the session view. Multi-window users can keep Settings open on a second monitor while the main window stays focused on the device. Cross-window settings sync keeps changes consistent even when the user is editing in one window and connected in another.
Settings section filter with ⌘F / Ctrl+F (or /) to jump between Appearance, Themes, Highlighting, Shortcuts, and Advanced. Keywords for App Skin and Shortcut sections are broad so search hits intuitive terms.
Vertical-tab layout for Settings and the Profile editor. Connection / Highlighting / Advanced groups in the profile form mirror Settings’s own grouping; less scrolling, clearer scope.
Every keyboard shortcut is user-rebindable. Settings → Shortcuts now exposes every action (connect / disconnect, hex view, send-break, font-size, copy / paste, send-file, clear, toggle-DTR / RTS, etc.) with conflict detection and per-OS defaults. Captured key combos render as ⌘+Shift+K / Ctrl+Shift+K pills.
Highlight pack toggles update existing scrollback live. Turn Cisco IOS off, the Cisco-specific keywords go plain in the lines already on screen, not just in newly-arrived output. Same for the master Highlight switch and the Timestamps toggle. Per-line arrival times are preserved across the replay so toggling Timestamps on doesn’t re-stamp every historical line as “now.”
Windows 11 ARM USB-serial detection. Baudrun’s missing-driver banner now fires on Win11 ARM (was silently dropping rows due to a JSON-parse bug on Manufacturer: null). Detection is arch-aware: PL2303 cables on Win11 ARM get a tailored message (“no compatible driver path; replace with a CP210x or FTDI cable”) and link to the adapters guide instead of a dead-end Prolific download page.
OG image, Twitter cards, JSON-LD SoftwareApplication schema, and Google Search Console verification on the docs site, so link previews and search-engine listings render as a real product page rather than a plain text card.

Changed

Docs site rewritten on Astro + Starlight (replaces MkDocs Material). Same content, faster builds, integrated Pagefind search, Cards / CardGrid components, custom Hero with screenshot-tour link, “Docs” quick-access pill on every page. Editorial pass across all twelve pages: removed AI-flavored comparison phrasing in favor of feature-focused language; no em dashes anywhere on the homepage.
Tauri 2.10 → 2.11.1 with matching @tauri-apps/api and @tauri-apps/cli updates. The 2.11.1 patch closes an IPC origin-confusion advisory (GHSA-7gmj-67g7-phm9); see Security.
Settings UI polish: flat highlight section instead of nested cards, destructive actions (reset, delete pack) prompt for confirmation with an undo, ARIA labels on every toggle.

Fixed

Linux + Windows: terminal output renders correctly on every theme. Cisco / Junos / Aruba syntax highlighting was collapsing to one color and most themes rendered as a black box on WebKit2GTK and WebView2. xterm.js’s runtime-injected stylesheet was getting silently dropped on these renderers, taking default foreground, the 16 ANSI color classes, the cursor’s block fill, and the selection background with it. Fixed by routing all of those through CSS variables on the wrap element instead, so the cascade carries them down regardless of whether the injection applied. macOS unaffected.
Linux + Windows: text selection in connected sessions. Same root cause as above — the selection-overlay rule wasn’t applying, so click-and-drag computed a range but rendered no visible highlight, making selection feel “read-only.”
Linux + Windows: Send File no longer freezes the app. The native file picker was using a sync Tauri command, which Tauri 2 dispatches on the WebView main thread. blocking_pick_file() on that thread deadlocked the event loop on every renderer except macOS. Same async-ification applied to import_theme, import_skin, pick_log_directory, and pick_config_directory.
Send File protocol dropdown shows above the modal. The Select popover sat at z-index: 9999 while modal backdrops sit at 10000; portaled-popover stacking happened to work on macOS WebKit by source order but not on WebKit2GTK or WebView2. Bumped to 10001.
Pager rendering with timestamps on. Cisco IOS / Aruba CX pager prompts (--More--) now stamp cleanly, and the next page of output lands on its own row with its own stamp. Previously the device’s redraw left our stamp untouched and a second stamp landed on the same row, producing the [ts1] [ts2] content artifact.
Empty \r\n lines no longer stamp. Pressing Enter at a Cisco prompt was emitting [ts]\r\n, which xterm wrote at the cursor’s end-of-line position — gluing a phantom stamp onto every prompt line.
macOS: flash-of-black on window open in release builds. Both the Baudrun skin and Settings substrate now pre-paint via WebviewWindow::background_color and an inline <style> in index.html, so there’s no white-then-skin transition.
macOS: header padding offset past the traffic-light zone in Settings and the Profile editor windows so the title and pills don’t sit under the close / minimize / zoom buttons.
Windows XP skin: tab readability. Active tab was rendering blue-on-blue; switched to var(--fg-primary).
Settings dir-load + cross-window sync. The Settings window had the wrong substrate color on first paint (transparent instead of skin background), and edits didn’t propagate back to the main window’s session header until next launch.
Profile form drag-and-drop when reordering profiles in the sidebar.

Docs

macOS PL2303HXA story corrected. Apple’s AppleUSBPLCOM DEXT matches 067B:2303 with no bcdDevice constraint, so the legacy chip rev (TRENDnet TU-S9 etc.) is bound out of the box on every supported macOS. The “PL2303HXA is broken on macOS” narrative was a Windows-driver story leaking into the wrong column.
New Windows 11 ARM section in the adapters guide, with per-vendor ARM64 driver state: SiLabs CP210x ships via Windows Update; FTDI ARM64 driver requires manual install; Prolific HXA has no working path; modern Prolific (REV_05+) needs the v6.5.0.0 ARM installer.
Scoop install on Windows now mentions scoop install git as a prerequisite (Scoop’s bucket-add fails fast without it).

Security

Tauri 2.11.0 → 2.11.1 patches GHSA-7gmj-67g7-phm9 (Origin Confusion: remote pages could invoke local-only IPC commands). Practical risk on Baudrun is low because our CSP restricts script-src to 'self', but worth applying.
rand 0.7.3 advisory cleared via transitive bumps from cargo update.

Internal

Dependabot config matches the actual project layout. Was still scanning gomod at root (left over from the pre-Tauri Go era) and npm at /frontend (path no longer exists). Now scans cargo at /src-tauri, npm at the repo root, npm at /docs-next, and GitHub Actions.

[0.9.4] — 2026-05-04

Added

Settings header shows the app version. A small dim monospace v0.9.4 pill sits on the right side of the Settings header so it’s easy to confirm at a glance which build is running. Pulled from tauri.conf.json at runtime via the @tauri-apps/api/app getVersion() helper, so it always reflects the actual installed bundle.

Fixed

Multi-window: spawned windows were blank and frozen on Windows. Both v0.9.2’s URL fix and v0.9.3’s CSP fix were necessary but not sufficient — the spawned window’s renderer still couldn’t bootstrap because WebviewWindowBuilder::build() ran synchronously inside the IPC handler. While that handler was in flight, Tauri 2’s shared Windows-side WebView2 protocol dispatcher couldn’t service the new window’s bootstrap fetches (HTML / JS / CSS over tauri.localhost, IPC over ipc.localhost). The renderer stalled on its initial document load, the window painted blank, and even F12 / right-click / X didn’t respond (all need a live renderer). build() now runs inside tauri::async_runtime::spawn, so the IPC handler returns the new window’s label immediately and the dispatcher is free to serve the new window’s startup. Right-click + drag multi-window now works end-to-end on Windows.
window.set_focus() removed from the spawn path. Was the first deadlock suspect — SetForegroundWindow on Windows waits for the target window to become processable, which a Tauri- spawned window mid-load isn’t. Newly-created windows take foreground naturally on every desktop OS, so the explicit call was belt-and-braces anyway. Removing it didn’t fully unstick Windows on its own, but it eliminated one known wait state from the IPC handler.

Docs

Note that Scoop needs git before adding a third-party bucket. The README + install guide quickstart now run scoop install git before scoop bucket add packetThrower https://github.com/packetThrower/scoop-bucket. Scoop fails fast with ERROR Git is required for buckets. otherwise.

[0.9.3] — 2026-05-03

Fixed

macOS: Homebrew install was broken because the DMG shipped a pre-fix .app. The release pipeline modifies the macOS bundle after Tauri builds it (rewrites the libusb load command via install_name_tool so the bundled Frameworks/libusb-1.0.0.dylib loads on user Macs that don’t have Homebrew, then re-signs the whole bundle ad-hoc). But Tauri creates the DMG during tauri build before that step runs, and we were copying that original DMG straight into the release artifacts — so brew users got a Baudrun.app with no Contents/Frameworks/, a binary still pointing at /opt/homebrew/opt/libusb/lib/, and a stale signature manifest (spctl rejected with “code has no resources but signature indicates they must be present”). The release workflow now rebuilds the DMG via hdiutil after the libusb fix + re-sign, with a mount-and-codesign --verify sanity check baked in. Users installing via the .zip were unaffected — that artifact already packaged the post-fix .app.
Multi-window: blank webview on Windows (CSP block). Spawned windows on Windows showed a blank page because every IPC call (list_profiles, get_settings, etc.) was being rejected by the Content Security Policy. Tauri 2 on Windows uses http://ipc.localhost for the IPC protocol; our CSP whitelisted only https://ipc.localhost. The Promise.all in the renderer’s bootstrap rejected, the UI never rendered, and the blank page persisted. Added http://ipc.localhost to both default-src and connect-src. macOS / Linux unaffected — they go through tauri: / ipc: schemes that were already in the policy.
Multi-window: spawned-window URL still didn’t render correctly on Windows. Even after dropping the ?profile=<id> query string in 0.9.2, the Windows webview would render blank with the WebviewUrl::App("index.html".into()) form. Switched to WebviewUrl::default() (empty PathBuf, the same path the main window uses since it has no explicit url in tauri.conf.json) — Tauri’s default index resolution is more reliable on Windows than the explicit-path form for spawned windows.

[0.9.2] — 2026-05-01

Fixed

Multi-window: blank webview on Windows. Spawned windows opened to a blank white page on Windows. The spawned-window URL was assembled as index.html?profile=<id>, but ? is an invalid Windows path character — Tauri’s WebviewUrl::App builds its URL from a PathBuf and Windows mangled or rejected the value, so the document never resolved. The initial profile id is now carried through the backend (a per-window pending stash that the renderer drains on mount, mirroring the existing take_pending_terminal_snapshot plumbing) instead of through the URL. Cross-platform clean — the spawned URL is plain index.html everywhere now.
Multi-window: drag-out creates a .txt file on Linux. The drag handler was setting both application/x-baudrun-profile (custom MIME, used by our dragend logic) and text/plain (the profile name). On GTK / Wayland file managers, text/plain looks like a draggable text snippet — dropping on the desktop made the DE create a .txt file with the profile name and consume the drop before dragend reached our backend cursor-outside check, so no new window opened. Removed the text/plain payload; only the custom MIME is set now, which no DE recognizes, so the drop falls through to dragend and spawns the window correctly.

[0.9.1] — 2026-05-01

Added

Multi-window support. Right-click any profile in the sidebar or drag it out to spawn a fresh window with that profile selected. Each window has its own session, so two windows can hold parallel serial connections to different devices. When the dragged profile is the active connection in the source window, the live session and visible scrollback move to the new window — same port, same DTR/RTS state, no mid-session bytes lost. Tear-off mid-transfer is rejected with a “wait or cancel first” message; everything else follows you. See the Advanced settings guide for the gesture map and edge cases.

Fixed

Windows: missing minimize / maximize / close buttons (#7). The tauri-plugin-decorum overlay-titlebar call was being applied on every desktop platform during window setup, but on Windows it strips the native frame expecting the renderer to draw its own titlebar — Baudrun doesn’t, so the system caption buttons went missing. Gated the call (and the spawned-window equivalent in the multi-window flow) to macOS only, where it has always been intended — the plugin’s purpose here is repositioning the macOS traffic-lights so floating-bubble skins can pull them inside the panel. Windows and Linux now get their default decorated chrome with all three buttons.
Settings button now pins to the bottom of the sidebar when there are no profiles (#8). The empty-state container was missing flex: 1, so the Settings button hugged it instead of sticking to the bottom the way it does once a profile exists.

[0.9.0] — 2026-04-25

Added

Tauri v2 / Rust port. Backend reimplemented in Rust on Tauri 2; the renderer stays Svelte 5. Macros / DTR-RTS / hex view / XMODEM/YMODEM / auto-reconnect / driver detection all preserved with the same on-disk JSON shapes so existing profiles, themes, skins, and settings round-trip without a migration step.
Signed in-app updater. Footer toast appears when GitHub has a newer release; clicking Install on a stable update downloads the platform bundle, verifies its minisign signature against the public key embedded in the binary, and relaunches into the new version. Settings → Advanced → Updates toggles the launch check and a separate “include pre-releases” knob. Pre-releases ship signed updater bundles too but don’t update the auto-update manifest, so stable installs aren’t auto-jumped onto an alpha.
Highlight rule packs. Six bundled packs — Baudrun default (vendor-neutral), Cisco IOS / IOS XE / IOS XR, Juniper Junos, Aruba AOS-CX, Arista EOS, and MikroTik RouterOS — toggle on per Settings or per profile. The user pack at $SUPPORT_DIR/highlight-rules.json is editable on disk and layers on top; additional packs can be imported via Settings → Syntax Highlighting → Import pack. First-match-wins ordering, available colors red / green / yellow / blue / magenta / cyan / dim. Per-rule CPU budget bails on regex catastrophic backtracking instead of locking the renderer.
Highlight rule playground — a static HTML page at packetthrower.github.io/Baudrun/playground.html for testing rule packs against real captures (drop a file or paste, edit the JSON, watch colors apply live; everything runs client-side, the file you drop never leaves your browser).
Per-profile syntax-highlight pack overrides. A profile can pick a different set of packs than the global default — handy when one profile talks to a Cisco device and the next to a Juniper one. The profile’s Syntax Highlighting card collapses to save space.
Importable highlight packs alongside the bundled ones. Settings → Syntax Highlighting → Import pack reads a JSON file into $SUPPORT_DIR/highlight/<id>.json and auto-enables it. Imported packs show a Remove button. Two starter examples ship under docs-next/public/examples/ — the minimal-skeleton schema and a practical syslog/journald set with severity keywords, systemd unit states, sshd events, and PID highlighting.

Changed

macOS code signing stays ad-hoc. First launch of a new download still prompts Gatekeeper’s “right-click → Open” UX — the maintainer doesn’t have a paid Apple Developer account yet. Auto-update works either way; only the first-launch experience is affected.
Content Security Policy explicit. Replaced csp: null with a tight default-src 'self' tauri: ipc: …; script-src 'self'; … so any future XSS in the renderer can’t reach an arbitrary origin. connect-src whitelists GitHub for the update check.

Security

Rule-pack ReDoS budget. User-imported regex now runs under a per-line + per-rule wall-clock cap; rules that take longer than the per-rule budget once are auto-disabled for the rest of the session with a console warning.
GitHub API response cap. Update-check fetch ceilings the body at 100 KB and times out after 10 s, so a hostile network redirect can’t return a giant JSON body or hang the renderer.
Skin variable validation. Imported skins reject CSS values containing url(), image-set(), expression(), @import, or javascript: / data: URIs to block exfiltration through var() references in regular CSS.
Updater key now passphrase-protected. Initial keypair was generated with an empty password; rotated to one protected by TAURI_SIGNING_PRIVATE_KEY_PASSWORD. Existing pre-release installs (alpha.1–alpha.13) won’t auto-update against the new pubkey but they were never on the auto-update channel anyway.

Ops & packaging

macOS installs ship per-arch (arm64 + amd64) .dmg + .zip with libusb-1.0.0.dylib bundled inside Contents/Frameworks/, so users without Homebrew can still run.
Windows ships .msi (stable tags only — WiX rejects alphanumeric pre-release identifiers) and .nsis-setup.exe for both x64 and arm64.
Linux ships .deb, .rpm, .AppImage, and Arch .pkg.tar.zst for both amd64 and aarch64. AppImage + the 60-baudrun-serial.rules udev rule mean no sudo / dialout group fiddling.

[0.7.0] — 2026-04-22

Last release on the Wails / Go backend before the Tauri v2 / Rust port in v0.9.0.

Added

Direct USB-serial access on Linux and macOS, via the new usbserial-go library. CP210x adapters — including vendor-rebranded VIDs like the Siemens RUGGEDCOM USB Serial console at 0908:01ff — now open straight through libusb with no vendor driver install. Devices surface in the port picker as USB · VID:PID — product name alongside the regular /dev/* entries. The driver-missing banner stays silent for any chipset the library can open directly. See the USB-serial adapters guide for the full per-chipset × per-OS support matrix.
Configurable scrollback buffer. Settings → Advanced → Scrollback gives a presets list (1k / 5k / 10k default / 50k / 100k lines) with memory-estimate hints. Custom values set directly in settings.json are preserved and shown as “N lines (custom)” in the picker.
Linux 60-baudrun-serial.rules udev rule shipped with the .deb / .rpm / .pkg.tar.zst packages. Uses TAG+="uaccess" so the currently-logged-in console user can open serial adapters without sudo or dialout / plugdev group membership. Full walkthrough in the USB-serial adapters guide.
Helpful error enrichment when a port open fails with permission denied (AppImage or manual-build users who don’t get the udev rule installed). Error text now names the exact sudo usermod -aG dialout $USER fix rather than bare “permission denied”.
Downloads badge on the README meta row.
GitHub Sponsors card on the docs home page.
Custom Select component with full keyboard navigation (arrows, Home/End, Enter, Escape, typeahead), portaled popover that escapes stacking contexts, and automatic skin theming.
Keyboard shortcuts for Clear / Send Break / Suspend. Default bindings are platform-appropriate: ⌘K / ⌘⇧B / ⌘⇧S on macOS, Ctrl+Shift+K / Ctrl+Shift+B / Ctrl+Shift+S on Linux and Windows. The split scheme preserves plain Ctrl+letter passthroughs (XOFF, VT, STX, etc.) to the serial device. Full details in the Keyboard shortcuts guide.
Editable keyboard shortcuts. Settings → Keyboard Shortcuts lets you rebind each session-level action to any combo you want, with a click-to-record widget and per-binding reset-to-default. Overrides persist in settings.json under a shortcuts map.

Changed

Syntax-highlighted scrollback survives zoom. Cmd/Ctrl + / − no longer strips the existing history’s colors. Uses @xterm/addon-serialize for the rebuild snapshot so SGR attributes round-trip correctly through the dispose-and-rebuild path.
Connect button enables the moment you pick a port. Previously stayed disabled until you explicitly Saved. If the form has unsaved changes when you click Connect, it now saves first so the backend opens the port with the config you actually see on screen.
Every dropdown replaced with a themed custom Select popover. Native <select> popups were rendered by the OS (GTK on Linux, Chromium on Windows, the system popup on macOS) and didn’t follow app skins or the light/dark appearance setting. The new popover renders in CSS so every skin — Synthwave and Blueprint included — themes the open dropdown the same way they theme the rest of the app.
macOS release split by architecture. Earlier versions shipped a single universal .app; now produces separate Baudrun-macOS-arm64-<version>.zip (Apple Silicon) and Baudrun-macOS-amd64-<version>.zip (Intel). Each bundles libusb-1.0.0.dylib under Contents/Frameworks/ so the .app is self-contained and works without Homebrew. Homebrew’s libusb is per-arch only, so per-arch builds sidestep the universal-dylib lipo dance.
Release notes on GitHub Releases are now a hand-curated “What’s Changed” commit list between the previous tag and the current one, derived from git log --no-merges. Previously the notes were a single-line link to the compare view.
Bundle ID renamed from com.wails.Baudrun to io.github.packetThrower.Baudrun so the installed app has a stable, repo-anchored identifier.

Fixed

Cyberpunk (Synthwave) and Blueprint grid overlays rendered at wildly wrong cell sizes on Linux — “sometimes normal, sometimes huge” depending on DPR and window size. Root cause was WebKit2GTK’s inconsistent handling of 1px stop bands inside repeating-linear-gradient. Rewritten to the standard tile-based pattern (linear-gradient … 0 0 / 40px 40px repeat) which renders identically on every engine.
Popover z-index conflicts with the full-screen overlay. The body::after decorative overlay used for skin-level grid/scan-line effects was at z-index: 9999, tying with the new Select popover and paint-ordering on top of it via DOM order. Overlay moved to z-index: 50, popover stays at 9999.

Ops & packaging

CI runner matrix swapped macos-13 (retired) for macos-15-intel.
CI + release workflows install libusb (libusb-1.0-0-dev on apt, brew install libusb pkg-config on macOS) to satisfy gousb’s cgo link.
Linux packages declare the matching runtime dep per format: libusb-1.0-0 on .deb, libusbx on .rpm, libusb on Arch pacman.
AppImage bundles libusb-1.0.so.0 into AppDir/usr/lib/ and AppRun prepends that to LD_LIBRARY_PATH so the packaged copy is found ahead of anything on the host.

[0.6.0] — 2026-04-22 and earlier

See GitHub Releases for full notes. Earlier versions landed the skin system, profile form, XMODEM/YMODEM file transfer, hex send, session logging, and the initial cross-platform release pipeline.