omnideck app 0.5.2

omnideck app 0.5.2

Changed

• Integrations: Integration access is now stored and enforced as an explicit per-tool allowlist. Existing connections migrate automatically, and brokered model providers remain available without appearing as tool integrations. Integration setup now uses a modal catalog, connection, tool-selection, and review flow; cancelling removes setup-owned credentials, while connected accounts can replace credentials without changing their saved tool choices, even when OAuth scopes narrow. Vault metadata upgrades run before brokers start and leave encrypted credentials unchanged. Older permission-format requests are rejected with a prompt to refresh the app. Action required for previously read-only HTTP integrations: migration disables the API tool for these integrations while preserving their configuration and credentials. To resume using the tool, explicitly enable it under Settings → Integrations → Change tools. Enabling it permits both read and write requests, subject to the upstream token's permissions; the old read-only restriction is no longer available. Previously read/write HTTP integrations retain API tool access. Google connections now use the scopes actually granted during authorization when determining which tools are available. Connection-list responses now use a single connections field. Integration catalog listings retain integrations; saved connection IDs and existing agent tool arguments are unchanged. Connection details now show a read-only summary of selected tools. Change tools and Rename open focused editing dialogs; Connection settings provides service-specific actions to update credentials. Tool pickers have searchable, collapsible groups and a consistent background for controls and rows. Integration discovery now refreshes in the background and after connection edits. Each agent run keeps its starting tool availability, while later runs pick up changes; revoked permissions remain enforced when tools are called. Tool selections now update without restarting the connection or interrupting already-running calls. Failed live updates stop the connection rather than restore revoked access. Healthy brokers now accept credential updates without restarting. Rejected replacements keep the existing connection; credential activation may interrupt an in-progress call. Generic HTTP and model-provider credentials are checked for valid configuration, not guaranteed upstream access.

Fixed

• Browser: Click, press-and-hold, and page inspection failures now include the underlying browser or vision-provider error, making problems such as detached elements or unavailable vision models easier to diagnose.
• Browser: Page browsing now traverses forms whose fields or custom properties shadow the browser's child collections, preserving visible content and interactive controls instead of failing to render the page.
• Browser: Browser tools now reconsider embedded content after the host page finishes loading, so a slowly loading dominant iframe does not leave its controls hidden behind a cached view of the host page.
• Browser: Image-only links and buttons now appear in page browsing with names from their images' alt text and usable click references. When no label is available, image filenames provide a last-resort name.
• Browser: Dropdown selection now goes directly to the requested option without committing intermediate choices, and no longer reports a false failure when the selection navigates or reloads the selected frame.
• Browser: Reading or saving pages now includes web-component shadow content, including nested components and slotted text, while preserving Markdown formatting, search, and chunk navigation.
• Browser: Reading or saving pages no longer includes inert HTML template contents, such as unexpanded headline placeholders. Content instantiated from templates remains readable.