OpenWork Release Notes

The Working indicator now tells the truth: it stops when a run errors or the engine is unreachable, and shows minutes once a run passes the first hour.

Sessions reconcile more cleanly — completions are detected while you’re working elsewhere, queued messages send even when the session is out of view, and archiving works from any workspace.

Cloud providers now connect using the credentials saved on your desktop, and Google Workspace retrieval is more resilient.

OpenWork is SOC 2 Type I — the landing page now shows the badge and live status.

Hardened security by fixing static-analysis findings and isolating provider sync contexts, alongside internal test and release tooling improvements.

OpenWork can now import and run portable Agent Plugins, bringing Anthropic-compatible plugin packs into the desktop app.

Automations can be pinned to a specific workspace, and remote-session commands now arrive in native local sessions on your desktop.

Fixed request storms and reload loops across Settings, the Library, the composer, and desktop policies, so long sessions stay fast.

Gmail replies support collapsible quoting and attachments, and OpenWork Cloud members get complimentary OpenWork Web access.

Strengthened sign-in and access security and made the desktop recover cleanly from socket and renderer crashes.

Session files now live in the artifact rail instead of interrupting the chat transcript, with safer badge layout and responsive behavior on narrow screens.

Markdown can render Mermaid diagrams safely, and code blocks offer a word-wrap control for long lines.

Agent runs recover more reliably from idle admissions, queued follow-ups, event-stream restarts, Settings visits, and large workspace session histories.

OpenWork Cloud adds per-member managed-model credentials, paid browser access, desktop delivery for remote-session commands, and more reliable worker recovery.

Electron file transfers now work correctly across the remote bridge, and LiteLLM examples include synchronized model metadata.

Added cross-workspace split view and transcript actions for resuming interrupted runs.

Live session status now survives navigation, workspace switches, and reattachment while long-running streams remain responsive.

Refined tool-call activity, thought grouping, artifact controls, and Library choices so active work is easier to follow and manage.

Cloud extension status now reflects real connectivity, remote-session capabilities reach cloud targets, and worker recovery avoids competing owners.

Added a pull-only Docker evaluation stack and strengthened enterprise licensing documentation and stewardship metadata.

Organization-managed MCP App dashboards now render on desktop, with a personal grid and an add-from-Connect picker that refreshes automatically.

Code Mode and MCP Apps are enabled by default, and Dashboard visibility follows each deployment’s availability controls.

Added an artifact code browser, branded connector tool calls, delegated-task shimmer, and smoother keyboard, Library, model, and chat controls.

Improved streaming and render performance, stabilized sidebar ordering and Settings state, and kept composer focus through refreshes.

Fixed Azure managed-provider credential selection and clarified Azure Foundry resource names for bring-your-own-key setup.

Hosted MCP Apps now render through the credential-bound Den gateway, and Connect refreshes its MCP App catalog when cached inventory is incomplete.

Fixed Den callback routing, API-origin derivation, and cookie forwarding so hosted sign-in remains on the correct domain.

Workspace switches preserve live agent runs under load, while stale tool activity and scrolling no longer disrupt the active transcript.

Desktop update channel selection stays stable, Automation control-plane traffic is bounded, and standalone MCP requests stop retrying indefinitely.

Clarified the difference between local setup, managed OpenWork Cloud, OpenCode models, and OpenWork-managed models.

First-party MCP App cards now guide connection, plugin, and skill-created flows directly in chat, including useful recovery cards when a connection fails.

Desktop automations report outcomes, open their execution threads, and recover missed runs and credential failures more reliably.

Programs are now called Workflows, with obsolete selection tools and legacy MCP App surfaces removed.

MCP connections are more resilient to server recovery, protocol changes, OAuth refresh bursts, and stale credentials.

Added current product screenshots, enterprise desktop deployment guidance, and a deployment-level Automation control.