Changelog
v0.10.4
v0.10.3
0.10.3 — 2026-09-09
viewbus knew two numbers about every queue and treated one of them as an afterthought. Dead letters got a detector, four alert types and most of the dashboard; active messages got a single sort and a threshold you had to guess. This release makes the backlog a first-class thing to watch.
Active messages on the dashboard
- Rank the estate by backlog, not just by failures. The dashboard’s controls now read Metric · Sort · Window, and the metric is its own choice: Dead letters or Active. All three sorts work on either, so “which queues grew their backlog the most this morning” is finally a question you can ask. It replaces the old “Active backlog” sort, which could only ever rank by current size — and which left the window pill on screen doing nothing whenever you picked it.
- A backlog is coloured by what’s normal for that queue. 500 active messages is a routine Tuesday for one queue and a stalled consumer on another, so there’s no threshold that means the same thing everywhere. Each row is graded against its own recent history instead, and hovering says what normal looks like: “1,204 active — normally ~15”. A queue viewbus hasn’t watched long enough stays uncoloured and says so, rather than showing a grade it can’t justify.
- The row’s sparkline follows the metric. Under Active it draws the backlog, not the dead letters — the shape and the number beside it describe the same series.
Smart Alerts for backlogs
- An alert that learns what your queue normally holds. Smart Alerts already watched how fast dead letters arrive; they now also watch how much work is waiting, and tell you when a queue is holding far more than it normally holds. Same idea, no number to pick: a queue that always sits on 50,000 in-flight messages isn’t a problem, and one that’s normally near-empty and suddenly holding 2,000 is.
- A burst that drains doesn’t wake you. A batch job dropping 5,000 messages that clear in two minutes is not a stalled consumer, so a backlog has to stay high for a sustain window — 30 minutes by default — before anything fires.
- The alert editor asks which count first, then what about it. The old list mixed the two: “Total dead letters” named its metric, “Active backlog” hid its trigger, and “Smart Alerts” meant dead letters without saying so. Now you pick the count, and only the triggers that make sense for it are offered. Every existing rule opens on exactly what saved it — nothing was converted or switched on.
Longer history
- “All time” joins the window picker. The look-back stopped at 30 days, so “how much has this queue ever accumulated” had nowhere to go. It reaches as far back as viewbus still has data — up to a year — and the row’s sparkline spans the same range rather than quietly showing you the last month beside an all-time number.
Fixes
- Slack and Discord webhooks actually deliver. Neither accepts an arbitrary JSON document — Slack wants a top-level
textorblocks, Discord acontentorembeds— so both answered every viewbus alert with HTTP 400 and nothing arrived. Alerts are now rendered into the destination’s own format, detected from the URL, and the editor tells you which format it recognised before you save. Plain webhooks are unchanged. - The Windows installer no longer stalls on the MCP sidecar. If an MCP client (Claude Desktop, an editor) was holding
viewbus-mcp.exe, the updater couldn’t overwrite it and the install sat there. The installer now closes the sidecar first. - A badly backed-up queue can’t fall off a large estate’s dashboard. The list’s internal cap ranked candidates by dead letters alone, so on a very large estate a queue with a big backlog and no failures could be truncated away — from the very view meant to show it.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.10.2
v0.10.1
v0.10.0
0.10.0 — 2026-09-03
The monitoring dashboard listed everything it watched. On a real estate that means a handful of queues worth looking at, buried under hundreds reading “0”. This release makes the list the work — and fixes a set of click-throughs that quietly did nothing.
Monitoring
- The dashboard opens on what’s carrying dead letters. Everything else — queues at zero, and ones not yet sampled — is behind a “carrying DL” chip you can switch off, and the list header always says how many of the total you’re seeing. A purged dead-letter queue keeps its row until retention catches up, which is why the list used to be mostly noise.
- The row sparkline follows the window you picked. It was pinned at 24 hours no matter what the 1h/6h/24h/7d/30d pill said, so “+5 in the last hour” sat next to a shape covering a day with nothing on screen admitting it.
- Slice the list by subscription, namespace, or entity type. Multi-select on each, with counts, and queues separable from topic subscriptions. Namespace choices narrow to the subscriptions you’ve ticked, so you can’t build a pair of filters that only ever returns nothing.
- Namespaces deleted in Azure leave the sidebar. A namespace removed in the portal stayed in the tree and stayed monitored, failing every check against a hostname that no longer resolves — and getting logged as a possible network outage. It’s now dropped as soon as Azure stops listing it.
- A quieter row. The severity rail down the left edge is gone; the same information was already in the colour of the row’s number.
Fixes
- Clicking a notification opens the right resource. If an alert, a finished operation, or a history entry named something outside the subscription you happened to be in, the click either did nothing at all or opened the correct tab on the wrong queue. Alerts in the bell, operation rows, the floating progress widget and the History pane all switch subscription first now, and only then land on the resource.
- Resending a subscription’s message goes to its topic. You can’t send to a subscription — the attempt sat there burning the full send timeout before failing, which read as contention rather than a wrong destination.
- Arrow-key selection stays on screen when you walk a long message list.
- The ⓘ popover hands over names. Name, parent topic, namespace and the full entity path, each with its own copy button, and all of it selectable if you’d rather drag.
- A session that never recorded its tenant repairs itself. If the tenant picker got skipped — the sign-in succeeded but listing tenants failed — everything looked healthy except the MCP tools, which refused with “No tenant selected in ViewBus”. The next launch fixes it, and anything indexed in the meantime, with nothing to click.
- Filtered counts no longer under-report.
count_messagesover MCP walked a single page before answering, and now groups a breakdown by more than dead-letter reason in the same pass.
Under the hood
- The index moved out of your roaming Windows profile.
viewbus.dband the logs now live under%LOCALAPPDATA%instead of%APPDATA%. It’s a machine-local cache of one machine’s Azure estate — it grows well past 100 MB, and it had no business syncing between machines and slowing down every Windows login. Your existing index moves itself on first launch and is compacted on the way across, typically shedding a third of its size. Nothing to re-add, and settings, themes and stored connections stay exactly where they were. If you have a plugin reading the database file directly, look in%LOCALAPPDATA%\viewbus\first and fall back to the old path; the/v1discovery file has not moved. - The database stops hoarding disk. Its write-ahead log had no size ceiling, so the one big transaction of a full re-index left a sidecar tens of megabytes larger than the database needed, permanently.
- Stale monitoring state is cleared. Health records for subscriptions you’d un-enrolled — or a tenant you’d left — stayed forever, still reporting failures nothing could clear.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.9.1
0.9.1 — 2026-08-01
Mostly monitoring. It used to be a small dialog; it’s now a proper part of the app.
Monitoring
- A full surface instead of a 640px dialog. Navigation lives in the sidebar, and the panes keep their state — leave and come back and you’re where you left off.
- The dashboard is a ranked worklist. What needs attention sits at the top, and rows expand in place. The separate Live pane is gone; the dashboard does its job.
- Sources are configured in one place, showing cadence, last-checked, failure counts, and stale enrolments.
- Four explicit alert types, including active backlog and oldest-message age — not just dead-letter counts.
- Fire only on a sustained breach. A for-duration qualifier stops a single spike from waking you.
- Create an alert from where you already are — a queue’s tab, the sidebar menu, or a dashboard row. One click starts monitoring the active subscription.
- Clicking a notification opens viewbus on the alerting resource (Windows), and alerts can re-notify while they stay firing.
- History and trends. 24-hour sparklines, dead-letter trends per estate and namespace, MTTR and flappiest/longest-burning rankings, and CSV export.
Navigation
- Back and forward. Mouse side buttons and Alt+←/→ retrace your steps; Esc leaves monitoring.
Fixes
- The message list no longer shows messages that are gone. If a message dead-letters while you have it open, the counts refresh — and now the list and the detail pane follow, instead of leaving you reading something that has already moved.
- Manual connections survive an unreadable keychain instead of vanishing from the sidebar.
- Concurrent database writes wait their turn rather than failing outright.
- Webhooks refuse to send unsigned rather than falling back silently.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.8.5
0.8.5 — 2026-07-26
Two things in this one: large namespaces were being cut off at 100 entities, and a pass over the interface so your theme’s own status colours actually get used.
Fixes
- Namespaces no longer stop at 100 queues or topics. The Service Bus admin API caps every listing response at 100 entries, and viewbus asked only once — so a large namespace showed a partial sidebar with nothing to indicate anything was missing. It now pages through the full listing for queues, topics, and subscriptions. Connections you’ve already added repopulate on their next refresh; there’s nothing to re-add.
- Dead-letter monitoring now sees the whole namespace. The same cap applied to monitoring, so on a namespace with more than 100 queues or topics only part of it was watched — a dead-letter build-up outside that first 100 never raised anything. Dead-letter counts in bulk operations were short for the same reason.
- The last message in the list is reachable. The message list clipped its own bottom row, so scrolling to the end of a peeked queue left the final message permanently out of reach.
- Message search no longer hides how deep the queue is. Search filters the messages already peeked, but “3 of 20 match” read as though 20 were the whole queue — a message that simply hadn’t loaded yet looked like it wasn’t there. The line now names the real queue depth next to the match count.
Improvements
- Faster to add a topic-heavy namespace. Discovery asked each topic for its subscriptions one at a time, which turned into a long wait once the full topic list started loading. Those requests now overlap, and rows still come back grouped topic-then-its-subscriptions.
- Imported themes control the status colours. Around 90 spots reached past your theme for a hardcoded green, amber, or red — imported VS Code themes were silently overruled, and the warm light themes fell short on contrast. They all route through the theme’s own status colours now, including the two steps in the throttle and severity ramps that are derived from them.
- Accessibility. Visible keyboard focus in the title bar, proper tab, sort, list, and tree semantics for screen readers, and text labels on the sidebar count badges, which previously distinguished active from dead-letter by colour alone.
- Consistency. Text sizes collapsed onto a single scale (nothing shifts by more than a pixel), checkboxes tinted by your theme instead of the OS accent colour, one ellipsis character throughout, and an empty-state message that’s finally correct on subscriptions and dead-letter queues too.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.8.4
0.8.4 — 2026-07-26
A sign-in fix for anyone whose Azure tenant enforces MFA or Conditional Access.
Fixes
- No more MFA sign-in loop. Tenants that require MFA rejected viewbus’ silent token refresh, and the app read that as a dead session — it signed you out and sent you back through a sign-in that could never satisfy the challenge. viewbus now recognizes the MFA prompt for what it is, opens the browser ceremony against your specific tenant, and keeps your session for every other tenant intact.
- Clear message when your device isn’t enrolled. If a tenant only admits managed or domain-joined devices, viewbus now says so and points you at your IT admin, instead of asking you to retry a browser verification that can’t succeed on an unenrolled machine.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.8.3
0.8.3 — 2026-07-02
viewbus now has a local API you can build on. While the app is running it serves a small HTTP API on your machine, so your own scripts, launcher plugins, and editor tasks can search what viewbus has already indexed and drive the app — no SDK, just HTTP.
New
- Local HTTP API. While viewbus is open it exposes a read-plus-focus API on
127.0.0.1: check status, fuzzy-search your indexed queues, topics, and subscriptions, and bring the app to the front on a specific resource. Ideal for a Raycast, Alfred, or PowerToys command, a VS Code task, or a quick script. - Local-only by design. The API binds loopback, authenticates with a fresh per-launch token, and rejects browser requests — nothing on your network or the web can reach it. On by default; turn it off with
localApi.enabled: falsein settings. - Developer docs. A new guide at viewbus.app/developers walks through it with copy-paste examples in cURL, TypeScript, Python, C#, and Rust.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.8.2
0.8.2 — 2026-07-01
viewbus goes keyboard-first. There’s now a proper shortcut layer you can drive without touching the mouse — and customize to your liking.
New
- Keyboard shortcuts. Toggle Settings (
Ctrl/⌘+,), notifications (Ctrl/⌘+Shift+N), and the sidebar (Ctrl/⌘+B); refresh the current namespace (Ctrl/⌘+R), reload the app (Ctrl/⌘+Shift+R), or hide to the tray (Ctrl/⌘+W). - Shortcut cheat sheet. Press
?anywhere to see every shortcut and navigation key at a glance. - Rebind anything. A new Settings → Keyboard tab lets you record your own bindings, with live conflict detection and reset-per-action or reset-all. Only the bindings you change are stored — everything else follows the platform defaults.
- Message navigation. With a message open,
↑/↓move through the filtered list andEsccloses it. The sidebar tree keeps its arrow-key browsing.
Improvements
- Clearer selection. The selected message row now stands out with a stronger highlight and an accent bar, so you never lose your place in a long list.
- Refreshed home-screen tips. Shorter, at-a-glance tips highlighting shortcuts, bulk operations, monitoring, the built-in MCP server, and themes.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.8.1
0.8.1 — 2026-06-25
A reliability fix for the Microsoft Store build, plus a couple of small quality-of-life touches.
Fixes
- Microsoft Store updates no longer hang. On the Store (MSIX) build, clicking “Update” could spin forever and stop responding, and the app froze for a few seconds on launch while it checked for updates. Both are resolved — the update check no longer blocks the app, and installing an update runs without freezing the window. The direct-download build was never affected.
Improvements
- Tenant IDs in the tenant picker. Each tenant now shows its ID beneath its name, so you can tell apart directories that share the same display name.
- Open in portal. Right-click a queue, topic, subscription, or namespace and choose “Open in portal” to jump straight to it in the Azure portal, scoped to the right tenant.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.8.0
0.8.0 — 2026-06-24
The release that turns one-message-at-a-time chores into bulk operations you can watch, filter, and trust.
Features
- Bulk dead-letter operations. Drain, delete, or resend many messages at once instead of clicking through them one by one. Preview the batch before you commit, and narrow it with filters — including by application property — so you act on exactly the messages you mean to.
- A dedicated Operations tab. Queue and subscription operations now have a discoverable home, with live progress and an ETA for anything still running. Minimize a long-running job to a toolbar indicator and reopen it whenever you want to check in.
- A unified notification center. The bell now merges alerts and operations into one filterable feed, so monitoring signals and the work you kicked off live in the same place. Operation history sticks around — dismissing something keeps it in the record rather than deleting it.
Improvements
- Graceful under throttling. When Service Bus rate-limits a bulk operation, viewbus backs off automatically and surfaces what’s happening instead of failing outright, with a clear “Reconnecting” state when the broker is unreachable.
- Honest, resumable operations. Targeted hold-lock draining for filtered bulk ops, accurate durations and residue stats, and any operation stranded by a crash or restart is marked interrupted on the next launch rather than left hanging.
- Clearer resend. Resending from a subscription now sends to the topic and warns you about fan-out, and selected-message resend runs through the same unified operation flow as everything else.
- Accessible operation dialogs, steadier layout (no tab-strip or dialog jitter while jobs run), and a completion toast with a filter-aware empty state when you’ve cleared everything.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.7.1
0.7.1 — 2026-06-05
Fixes the Microsoft Store build’s taskbar icon, which rendered on a blue plate instead of transparent. Store-only — direct installers were never affected.
v0.7.0
0.7.0 — 2026-06-04
The release that reorganizes the sidebar around the way you actually navigate.
Features
- A tabbed sidebar. The single scrolling tree is now four focused tabs: Subscription (the classic per-subscription tree), All (every namespace across every subscription in one view), Favorites (just your starred resources), and Connections (your connection-string namespaces, renamed from “Manual”). Each tab has its own search box that filters in place — matches stay in their namespace → topic → subscription context.
- Search across every subscription. The new All tab indexes and searches resources across all your subscriptions at once, so you don’t have to remember which subscription a queue lives in. Spotlight (Ctrl+I) does the same now — results span every subscription, each tagged with where it lives.
Improvements
- “As of” freshness hints on the All and Favorites counts, so you can tell how current the numbers are.
- Friendlier error messages on send, purge, and dead-letter when the broker or network hiccups.
- Security hardening across the sign-in flow and input handling.
- A long list of reliability fixes — steadier indexing across tenant and subscription switches, safer theme and hotkey handling, and a native dialog if the app ever fails to start.
All local-first as always. Update via the in-app updater or grab a fresh installer from viewbus.app — your settings, themes, monitored sets, and stored connections carry over untouched.
v0.6.1
0.6.1 — 2026-05-28
v0.6.0 shipped with a broken message editor — unstyled white text, mis-aligned scroll, and unresponsive typing in the installed app (dev builds were fine, which is how it slipped through). v0.6.1 restores the editor and adds a build-time guard so the same trap can’t catch us again. Update via the in-app updater or grab a fresh installer from viewbus.app — settings, themes, monitored sets, and stored connections are unaffected.
v0.6.0
0.6.0 — 2026-05-28
The release for knowing when your queues start failing — before your users do.
Features
- Set up automatic monitoring and alerting. ViewBus can now watch dead-letter counts for you in the background, on a cadence you choose (5 min / 15 min / 1 h). Group queues, topics, or whole subscriptions into named sets, pick a threshold per set (“ping me if any production DLQ goes over 25”), and get a toast plus a count on the notification bell the moment one trips. Optional webhooks fan out to Slack or your own tooling.
- Mute noisy alerts. Hit mute for an hour or a day on anything that’s just noise. Mutes auto-resume — if the issue’s still going when they expire, ViewBus pings you again.
- Monitoring page. A new top-level Monitoring view: a live ranking of the queues with the most dead-letter activity right now, history charts for the last 7 days / 30 days / 1 year, and a feed of recent alert activity. Click any row to jump straight to that queue.
- Top dead-letter queues on the home screen. A new at-a-glance widget surfaces whatever’s actively misbehaving without making you open Monitoring.
All of it stays on your machine. Monitoring runs in a local background worker, history lives in SQLite next to the rest of your indexed data, and webhooks fire directly from your machine to whatever endpoint you configure. No telemetry, no cloud, no relay.
v0.5.2
0.5.2 — 2026-05-14
A maintenance release: in-app updates work on Windows again, the Microsoft Store taskbar icon stops being a blue square, and macOS gets a Homebrew install path.
Fixes
- In-app “Update to X.Y.Z” works on Windows again. Existing 0.5.1 users on Windows who clicked Update from the toast hit
Update failed: missing field signature. The cause was a half-signedlatest.jsonon viewbus.app —tauri-plugin-updatervalidates the whole platforms map before checking the target version, so the macOS entry missing its signature broke the Windows update path too. One-click updates from the in-app toast now go through. - Microsoft Store taskbar icon is no longer a solid blue square. The Store-installed app was plated with the Windows accent colour on the taskbar, jump list, and Alt+Tab because the MSIX package shipped without the
altform-unplatedicon variants Windows needs to render unplated. The transparent monitor icon now shows up correctly. Store users with the icon already pinned may need to unpin and re-pin once to clear Windows’ icon cache. - Microsoft Store update failures surface real errors. A failed Store-side update used to silently report “update installed.” Failures now write a structured error code to
viewbus.log, and the in-app toast shows the actual reason.
Features
brew install --cask haakofli/viewbus/viewbus. A Homebrew cask is live for Apple Silicon Macs. The cask clears the Gatekeeper quarantine bit automatically — noxattr -crritual after install.brew upgrade --cask viewbushandles future updates. The manual DMG path still works for users without Homebrew.
Internal
- Logging covers more of the app. Roughly fifty silent error paths across the Rust backend and React frontend now write to
viewbus.log, so “zip up your logs folder and send” actually produces something useful when triaging bugs.
v0.5.1
0.5.1 — 2026-05-06
Fixes
- The diff editor used by Resend and Compose rendered as a blank pane in release builds — a CSP rule was blocking Monaco’s bundled worker and fonts. Dev builds were unaffected, which is why it slipped past local testing.
v0.5.0
0.5.0 — 2026-05-06
The release for working on messages, not just looking at them.
Features
- Bulk operations. Purge an entire active queue, dead-letter every active message, or empty a whole dead-letter queue — each with a live progress counter and a cancel button. Designed to drain stuck queues without portal hacks.
- Compose new messages. A dedicated dialog for sending fresh or scheduled messages, with full property and content-type control. Replaces the “open Postman, generate a SAS, paste JSON” workflow.
- Edit before you resend. Click any dead-lettered message and the detail pane opens directly in an inline Monaco editor — change the body, tweak properties, and see a side-by-side diff before sending. JSON syntax highlighting throughout.
Improvements
- Row-level context menu with quick filters and per-message resend / delete.
- Copy-to-clipboard buttons next to every property in the detail pane.
- Optional editor theme tokens (background, diff tints) for MCP-authored themes.
v0.4.0
0.4.0 — 2026-04-30
Features
- Multi-tenant sign-in. If your account belongs to several Azure tenants, viewbus enumerates them on sign-in and lets you switch between them from the account dialog. The sidebar tree, MCP results, and spotlight all stay scoped to the active tenant — no more squinting at the wrong subscription.
- In-app updates. Windows (NSIS), Windows MSIX (Microsoft Store), and macOS DMG builds all check for new versions on launch and show an unobtrusive banner when one is available. Click to download, or dismiss to wait for the next.
v0.3.2
0.3.2 — 2026-04-29
The headline: viewbus runs on macOS.
Features
- macOS support. Apple Silicon DMGs ship from CI on every tagged release. The build is unsigned for now — clear the Gatekeeper quarantine bit with
xattr -cr /Applications/ViewBus.apponce after install. Intel Macs aren’t built, but Rosetta 2 runs the ARM DMG fine. - Runtime parity with Windows. macOS titlebar, keyboard shortcuts, and behaviour match the Windows build — same app, same muscle memory.
Improvements
- Refreshed bundled theme set.
Internal
- Wiki with cross-linked source pointers.
- Contract unit tests.
- CI auto-bumps the marketing site’s
latest.jsonon tag push.
v0.2.1
0.2.1 — 2026-04-27
A small patch release that restores two networked features broken in 0.2.0.
Fixes
- In-app update check reaches the server again. The 0.2.0 build’s content security policy didn’t allow connections to
viewbus.app, so “Check for updates” in Settings → About always failed with “couldn’t reach the update server.” Existing 0.2.0 users will need to download 0.2.1 manually from the website or GitHub releases — the check inside the running 0.2.0 app can’t see this update for the same reason. - Announcements channel works again. The announcements feature shipped in 0.2.0 was silently blocked by the same CSP miss. Notices published to
viewbus.app/announcements.jsonnow reach the app. - Download links on GitHub release pages. The 0.2.0 release page rendered the installer and MSIX links as repository blob paths instead of release-asset URLs, leading to 404s. The release workflow now writes absolute asset URLs.
v0.2.0
0.2.0 — 2026-04-26
A minor release that adds a notification channel for between-release news and lays the groundwork for Microsoft Store distribution.
Features
- In-app announcements channel. viewbus now fetches
https://viewbus.app/announcements.jsonon launch and renders three severity tiers in the main window: an info toast for low-priority items, a top banner for warnings, and a modal for security notices. Each is dismissible and remembered per id, so seen notices don’t reappear. Designed to surface security advisories and deprecation warnings between releases without forcing a new install. - MSIX package. Each tagged release now produces a
viewbus_<version>_x64.msixalongside the NSIS installer. The MSIX is the package format Microsoft Store uses; it’s also installable directly via Windows for sideload (developer mode + signed) for environments that prefer MSIX over.exe.
Improvements
- Theme picker order. Built-in themes now appear as Dark → Light → Dracula instead of the previous alphabetical-by-id order. The “(Showcase)” suffix on Dracula is gone — it’s just “Dracula” now.
- Brand consistency. All user-facing strings now use
viewbuslowercase, matching the wordmark. TheViewBuscasing remains on internal identifiers (installer filename, Windows registry entries) where stability matters for installed users. - License attribution shipped with the installer. A
THIRD-PARTY-NOTICES.txtfile listing every reciprocal-licensed dependency is now bundled with the binary, satisfying the attribution requirements of MPL-2.0 and other relevant licenses.
v0.1.2
0.1.2 — 2026-04-23
Bug fixes and broader MCP client support.
Fixes
- Feedback send now works. Discord was blocked by the app’s content security policy; the endpoint is now allow-listed and network failures along that path get written to the local log file instead of vanishing.
- Animated spinners actually animate. The bus-shaped loader is now animated in production builds. The keyframes had been declared inside the SVG’s inline
<style>block and weren’t being bundled by the production build pipeline; they live in the global stylesheet now. - MCP binary ships with the installer. First launch no longer shows the “run cargo build” message —
viewbus-mcp.exeis now bundled as a Tauri sidecar and installed next to the main app. - Crashes reach the log file. A Rust panic hook forwards unhandled panics into the rolling log, so unexplained app exits leave a trail for support.
Features
- MCP tabs for more clients. The Connect MCP dialog now has tabs for Cursor, Codex CLI, OpenCode, and VS Code (Copilot agent mode) in addition to Claude Desktop and Claude Code. Each tab shows the exact config-file path, the snippet to paste (JSON or TOML, formatted for that client), and how to reload the server after editing.
v0.1.1
0.1.1 — 2026-04-23
Initial public release.
Features
- Azure subscription discovery + live tree browsing (SQLite-backed for instant navigation)
- Queue + topic message peeking with filters (session, message ID, correlation ID, subject, DL reason)
- Dead-letter resend (with property edits) and bulk delete
- Manual connection strings (stored in Windows Credential Manager, never on disk in plain text)
- Spotlight search (
Ctrl+I, rebindable) across all indexed resources - Close-to-tray with Spotlight still active
- Built-in MCP server — 10 read-only tools (
get_status,list_namespaces,list_queues,list_topics,list_subscriptions,get_resource,search_resources,count_messages,peek_messages,get_message_detail) + 1 opt-in write tool (upsert_theme) - Themes, custom user themes via
%APPDATA%\viewbus\themes\, and one-click VS Code theme import - Daily-rotated local log files for support; opt-in feedback dialog attaches them when reporting bugs
Known limitations
- Windows only (macOS / Linux builds not yet available)
- Installer is unsigned — first launch triggers Windows SmartScreen. Click “More info” → “Run anyway” once; subsequent launches are silent. Code-signing certificate + MSIX packaging is planned before Microsoft Store submission.