Skip to content

omnideck v0.1.0-beta.5

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 13 Aug 19:13
· 33 commits to main since this release
cbe57d1

omnideck application v0.1.0-beta.5

This beta fills several native desktop gaps while preserving the existing
browser application and setup experience. It bundles OmniDeck CLI
v0.11.0-beta.2 from commit a32d3ad95f44 and the OmniDeck 0.1.4 runtime
image at its checked-in immutable digest.

Desktop zoom and window chrome

The hosted application now responds to Ctrl/Cmd with +, -, or 0, and to
Ctrl/Cmd plus the mouse wheel. Zoom is implemented by a desktop-only webview
controller, so the regular browser application is unchanged. The unintended
native application menu remains disabled.

Downloads and completion feedback

Agent exports and conversation artifacts now use the native download path and
remain on the hosted application. Successful downloads appear in the existing
top-center toast stack with the saved filename and Downloads destination.
Software-update notices intentionally remain in their quieter bottom-right
location.

Native software updates

The desktop host once again checks for application updates and exposes only a
narrow, typed update bridge to the exact loopback-hosted application. Update
availability, defer, skip, and install behavior are owned by the native host;
hosted content receives no generic filesystem, process, shell, dialog, opener,
or updater-plugin authority.

Qualification coverage

The packaged VM journeys now verify artifact downloads and completion toasts,
keyboard and mouse-wheel zoom, updater state and events, the absence of a
native menu, and continued browser behavior. Linux zoom coverage includes
trusted operating-system-level keyboard and wheel input in addition to
WebDriver observability. These checks run alongside the existing setup,
recovery, Custom Apps, host-boundary, lifecycle, and Windows NSIS journeys.

Known limitations

Preview packages do not yet carry paid publisher identities. Windows may show
a Microsoft Defender SmartScreen warning, and macOS may require explicit
approval in Privacy & Security. Native macOS and ARM64 execution remains
dependent on available dedicated hardware and is recorded separately from the
hosted build and static package contract.