Different AI AI coding tools

What's new

OpenWork v0.18.65 desktop release.

• Public artifacts use the openwork-* naming convention.
• Cloud artifacts use openwork-cloud-* and require sign-in without enterprise activation.
• Enterprise artifacts use openwork-enterprise-* while retaining the standard OpenWork app identity.
• Public, Cloud, and enterprise Electron builds use separate updater manifests on this release.

Windows installers are signed using Microsoft Artifact Signing.

What's new

OpenWork v0.18.64 desktop release.

• Public artifacts use the openwork-* naming convention.
• Cloud artifacts use openwork-cloud-* and require sign-in without enterprise activation.
• Enterprise artifacts use openwork-enterprise-* while retaining the standard OpenWork app identity.
• Public, Cloud, and enterprise Electron builds use separate updater manifests on this release.

Windows installers are signed using Microsoft Artifact Signing.

Known open fixes

Decision: OpenWork release operator, acting on the request to release through GitHub Actions without further questions. Ship the reviewed dev branch as-is; do not merge unrelated open PRs as part of a release. These changes remain deferred for separate review.

• #6900: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(desktop): keep session pins durable across crashes)
• #6892: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(documents): follow relative Microsoft Graph page links)
• #6891: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(workbot): keep teaching closed until explicitly opened)
• #6852: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(chat): resolve nested file links in the action menu)
• #6837: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(app): retain conversation history across workspaces)
• #6819: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(workbook): read [h]:mm elapsed-time cells as durations, not dates)
• #6810: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(server): make engine startup timeouts configurable)
• #6770: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(app): render right-to-left text right-to-left)
• #6767: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(features): keep remoteSessionAnswers off by default)
• #6731: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (chore(deps): bump fast-xml-parser from 5.8.0 to 5.11.2)
• #6701: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(server): keep env.json beside the active server config)
• #6555: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (feat(connectors): make Microsoft 365 credentials directly editable)
• #6551: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(connectors): show Slack MCP setup guidance on connection failure)
• #6478: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (feat(app): allow model selection on automation proposals)
• #6043: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(den): retry transient password screening failures)
• #5915: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(desktop): preserve Windows runtime PATH across env layers)
• #5749: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (Connectors page (platform + custom MCP) with engine-side MCP liveness probe)
• #5515: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (fix(mcp): accept WebSocket origins in MCP App connectDomains)
• #4680: Ship anyway — release reviewed dev as-is; this open PR is not merged or included. (feat(den-api): add a kubernetes worker provisioner)

Bring Claude conversations into OpenWork

• Bring your Claude history with you. Import Claude chats and Claude Code sessions into a workspace from Settings → Import, where they become regular OpenWork chats.
• Work with connected files on OpenCode v2. Bring Google Drive, OneDrive, and SharePoint files into your workspace and save edits back; attach workspace files to Gmail drafts and replies, or upload them to Google Drive. OpenWork asks you to approve each transfer.
• Use computer use on Windows and set it up once. Windows desktop users can use computer use with apps on This PC. Set it up in Settings → Computer use; chats no longer have a computer status button, and the browser has one button in the side rail.
• Desktop work keeps its place and gets easier to start. The window reopens at its previous size and position, Cmd+N (Ctrl+N) starts a session even while you type, and organization switching refreshes your skills, connected apps, and models. Verified sign-in no longer waits for organization discovery to finish. Show model reasoning now starts off; turn it on in Settings → Preferences to see readable reasoning.
• For admins: completed features are now available by default, with clearer controls. Local AI providers, Automation settings, agent-assisted connection removal, Workbot search, improved usage-limit cards, task-preserving sign-in, Claude imports, and organization Prompts are available without a special setup; retired OpenCode Zen models are no longer offered. Automations are on by default, with separate Desktop and Cloud controls for organizations; sandbox join links add admins by default, with a choice to add members instead.
• Workbot, models, and self-hosted setups are more dependable. Workbot handles brief sign-in interruptions and rebuilds outdated computers when resumed. OpenWork Models adds GPT-6.1 Terra, Kimi K3.1 Pro, and DeepSeek V4.1 Flash; self-hosted desktops no longer update beyond the server's supported release.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Work with OneDrive and SharePoint files in OpenWork

• Work with OneDrive and SharePoint files. Agents can search, open, edit, and save Word, Excel, and PowerPoint files, including files shared with you, once an admin enables the required permission.
• Workbot's Browser and Computer views connect again. If a computer needs an update, Workbot rebuilds it when you open the view; it avoids rebuilding while a task is running.
• Sign-in and connected admin tools are safer. The desktop app now blocks unsafe non-web links from remote MCP sign-in requests. For teams connecting OpenWork to other AI tools, Den admin changes require write access, scripts cannot call admin tools, and credential data cannot be read through den_query.
• For admins and self-hosters: Den gets security and recovery fixes. Self-hosted Den deployments should update for recent Next.js security fixes, and opt-in administrator permission recovery now works with common database encodings. Operators can also enable hashed sign-in session tokens without signing anyone out.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Keep agent work in view while you work elsewhere

• Keep agent work in view while you work elsewhere. Desktop users can pop the computer view and floating browser into their own windows above other apps, and browser full screen now fills the display.
• Dictate messages and use workspace commands again. On macOS and Windows, dictation shows your words as you speak, stops when you click the mic again, and keeps words across pauses. On OpenCode v2, / lists workspace commands and skills, and picking one runs it.
• Follow Workbot's browser work and longer tasks. Workbot shows browser activity live and links to pages it opened. Background tasks can pass files and read just the part they need, while longer scripts and documents can finish without a cut-off reply being mistaken for completed work.
• Invitations and connections take clearer paths. Invited teammates can join their workspace during sign-in, invitation emails explain who invited them and where to get help, and completed MCP sign-ins no longer appear to fail. Teams messages and Outlook meeting invitations now wait for your confirmation.
• For admins: organization and billing details are clearer. Compact organization rows, recent organizations, and week-over-week summaries make admin pages easier to scan. The Free plan covers up to five users, and pending invitations count until they expire.
• For self-hosters: web access and standalone installs are more predictable. openwork-server web answers only its own host names unless you add proxy names with --allowed-hosts. Standalone server and bootstrap installs require Node.js 24.x (24.22.1 or newer), and the bootstrap installer downloads a supported runtime when needed.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Move older OpenWork installs to OpenCode v2 in the background

• Older installs move to OpenCode v2 in the background. Existing installs still using OpenCode v1 are moved over automatically, with a backup made first so your chats are kept. Windows installers also carry less duplicate engine data, and Windows can identify OpenWork's signed app files.
• Computer use is more capable and predictable. For Mac users, the agent can script apps directly and keeps working while you use your computer; Take over and Stop return control, and Continue resumes the task. Workbot can also script supported desktop apps. Browser pages keep a steady desktop, tablet, or phone size while the panel changes, and forms take fewer steps. When available, you can dictate into OpenWork or Workbot.
• Chat can work with more of your existing tasks and connections. Type # to add another task as context, ask the agent to create or move sidebar groups, and find connected actions with everyday wording. You can finish or repair an API-key connection in chat without sharing the key with the agent, and OpenWork Cloud tools work again in older desktop versions.
• Documents and first launches are more dependable. Closing an edited document now gives clear save, discard, or cancel choices, and reloading or reopening it preserves your editing session and unsaved work. Workbot can open a requested document beside chat, explain why a file could not open, and show or rebuild a computer that will not connect. Fresh desktop installs can load built-in tools even if the package registry is unavailable; slow Windows sign-in and first launch no longer hide recovery options.
• For admins: team and organization controls are clearer. Platform administrators can manage feature access per organization member and, when enabled, grant organizations Web access or extra Free Auto usage. Admins can finish connector setup after a check fails, remove connectors, and save team-role changes reliably; Workbot settings show one default model and its availability. When available, Workbot can guide eligible people from free Auto to paid Luna without losing the conversation.
• Website visitors can find practical AI governance guidance. The expanded enterprise pages explain governing employee AI and planning an OpenWork rollout.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Known open fixes

Shipped without (decided by Ben, 2026-10-22: none is a regression introduced since v0.18.59; all are older fork PRs still in review): #6043, #5915, #5749, #5613, #4680, #4215, #4061, #4009, #4007, #4005, #3970, #3903, #3781, #3595, #3414, #3413. No PR opened since v0.18.59 matched the release fix filter.

Read, edit, and discuss documents in Workbot

• Work on documents without leaving Workbot. When Documents is enabled for your workspace, preview Drive files before choosing Edit when editing is enabled, keep chat open beside a document, and continue your conversation with the file in view. Google Docs, Sheets, and Slides stay in Google and save to the original; on OpenWork Cloud, Office files can use an editor in your own workspace when enabled.
• AI models and providers work more smoothly across OpenWork. Desktop users can use existing Azure Foundry and custom OpenAI-compatible providers on OpenCode v2, see organization model changes in the picker when enabled, and find the same available models in Settings and shortcuts. When AI Gateway access is enabled, cloud agents can use supported models assigned by their organization.
• Admins can check setup before work gets stuck. Settings › Diagnostics brings desktop startup, AI provider, connector, and deployment-service checks together. Google Workspace settings can also identify APIs an admin needs to turn on, and Workbot explains when an organization needs an AI provider before it can answer.
• Chat keeps files, prompts, and agent work on track. Files saved from chat go to the opened folder, including files created in a conversation's own folder; links with spaces open correctly, failed writes are labeled as failed, and messages in side chats are easier to start. OpenCode v2 history copies can resume after restart; if a chat is too large to copy whole, its largest outputs or attachments stay in the original history.
• Team and Workbot tasks have clearer paths. When enabled, members can connect assigned accounts in Workbot; members with team-management access can open the right team's settings, and teams can follow tasks started on another computer. When available, admins can set team or organization defaults for new desktop chats and provider-specific spend limits, and inspect Library use and free Auto conversion insights. Workbot's link-only sharing is gone; authorized invitation emails remain available in Den.
• Self-hosting and connected tools get practical fixes. Self-hosters get updated AWS, Google Cloud, and Azure deployment options and clearer service checks. MCP clients can identify OpenWork and receive clearer tool guidance, and the website's Trust Center links now lead to the hosted Trust Center.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Known open fixes

Decision: @benjaminshafii explicitly chose Ship current dev on 2026-10-20 after the release preflight surfaced open startup/crash fixes. Ship without landing the following preflight PRs; defer them to a later release rather than expand this release scope. This is a scope decision, not a claim that the reported bugs are resolved.

• #6192: ship anyway; deferred by the release requester to keep this release on current dev.
• #6183: ship anyway; deferred by the release requester to keep this release on current dev.
• #6180: ship anyway; deferred by the release requester to keep this release on current dev.
• #6175: ship anyway; deferred by the release requester to keep this release on current dev.
• #6160: ship anyway; deferred by the release requester to keep this release on current dev.
• #6159: ship anyway; deferred by the release requester to keep this release on current dev.
• #6154: ship anyway; deferred by the release requester to keep this release on current dev.
• #6152: ship anyway; deferred by the release requester to keep this release on current dev.
• #6151: ship anyway; deferred by the release requester to keep this release on current dev.
• #6149: ship anyway; deferred by the release requester to keep this release on current dev.
• #6141: ship anyway; deferred by the release requester to keep this release on current dev.
• #6133: ship anyway; deferred by the release requester to keep this release on current dev.
• #6113: ship anyway; deferred by the release requester to keep this release on current dev.
• #6078: ship anyway; deferred by the release requester to keep this release on current dev.
• #6077: ship anyway; deferred by the release requester to keep this release on current dev.
• #6069: ship anyway; deferred by the release requester to keep this release on current dev.
• #6068: ship anyway; deferred by the release requester to keep this release on current dev.
• #6067: ship anyway; deferred by the release requester to keep this release on current dev.
• #6043: ship anyway; deferred by the release requester to keep this release on current dev.
• #6042: ship anyway; deferred by the release requester to keep this release on current dev.
• #6040: ship anyway; deferred by the release requester to keep this release on current dev.
• #6039: ship anyway; deferred by the release requester to keep this release on current dev.
• #5979: ship anyway; deferred by the release requester to keep this release on current dev.
• #5969: ship anyway; deferred by the release requester to keep this release on current dev.
• #5915: ship anyway; deferred by the release requester to keep this release on current dev.
• #5749: ship anyway; deferred by the release requester to keep this release on current dev.
• #5613: ship anyway; deferred by the release requester to keep this release on current dev.
• #5515: ship anyway; deferred by the release requester to keep this release on current dev.
• #5316: ship anyway; deferred by the release requester to keep this release on current dev.
• #4680: ship anyway; deferred by the release requester to keep this release on current dev.
• #4612: ship anyway; deferred by the release requester to keep this release on current dev.
• #4215: ship anyway; deferred by the release requester to keep this release on current dev.
• #4061: ship anyway; deferred by the release requester to keep this release on current dev.
• #4009: ship anyway; deferred by the release requester to keep this release on current dev.
• #4007: ship anyway; deferred by the release requester to keep this release on current dev.
• #4005: ship anyway; deferred by the release requester to keep this release on current dev.
• #3970: ship anyway; deferred by the release requester to keep this release on current dev.
• #3903: ship anyway; deferred by the release requester to keep this release on current dev.
• #3781: ship anyway; deferred by the release requester to keep this release on current dev.
• #3595: ship anyway; deferred by the release requester to keep this release on current dev.
• #3414: ship anyway; deferred by the release requester to keep this release on current dev.
• #3413: ship anyway; deferred by the release requester to keep this release on current dev.
• #3403: ship anyway; deferred by the release requester to keep this release on current dev.
• #3401: ship anyway; deferred by the release requester to keep this release on current dev.

Windows installers are signed using Microsoft Artifact Signing.

Released artifact verification

Verified the downloaded v0.18.59 Cloud and Enterprise mac-arm64 ZIPs (not local builds):

openwork-enterprise-mac-arm64-0.18.59.zip: sha512 OK
OpenWork Enterprise.app: codesign --verify --deep --strict PASSED
OpenWork Enterprise.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: Different AI inc. (F5DJWB4CCV)
openwork-cloud-mac-arm64-0.18.59.zip: sha512 OK
OpenWork Cloud.app: codesign --verify --deep --strict PASSED
OpenWork Cloud.app: accepted
source=Notarized Developer ID
origin=Developer ID Application: Different AI inc. (F5DJWB4CCV)
All 12 updater manifests: version 0.18.59 OK
Every manifest URL references an existing release asset: OK

Scope: signature, notarization, manifest version/asset references, and the two mac-arm64 ZIP checksums. This does not prove application startup or sign-in. The latest successful scheduled test run was on a different commit, so packaged boot coverage on the exact release commit is not established by this verification.

Run OpenWork Web on your own self-hosted deployment

• Self-host OpenWork Web and team tools on AWS. For self-hosters: run OpenWork Web with sandboxed browser workspaces, and deploy Slack, Workbot, and Automations that run without a desktop. AWS deployments can use existing networks and load balancers, and can connect to an existing cluster or runner fleet.
• Connect OpenCode 2 to your organization. If you use OpenWork from OpenCode: the opencode-openwork plugin brings in your organization's AI Gateway models, tools, and skills after sign-in, without the desktop app. You can also upgrade desktop chats to OpenCode 2 with a backup first; its conversations can use the built-in browser and discover connected tools reliably.
• Admins get clearer controls and reporting. Organization Analytics is back, with restored usage and workflow history where available. When enabled, admins can also report on skills, plugins, and connectors, set member, admin, and team permissions, and choose a default model for cloud agents; Audit Logs now cover more organization activity.
• Chat and daily work recover more smoothly. Pasted text and images stay at the cursor, reopened Apps load their data, migrated chats with a missing agent can answer again, and OpenWork keeps the Working status visible during quiet stretches. Ollama keeps multiple selected models and their thinking choices; Drive uploads respect your chosen Google account.
• Calendar, Workbot, and connections do more. When Calendar features are enabled, add or edit Automations alongside meetings; Workbot can recover stopped tasks. When enabled, admins can check when connections were last verified, and compatible MCP clients can subscribe to remote-session updates.
• Some familiar pages and searches have changed. Organization dashboards and admin-assigned dashboards in Desktop are gone, while personal dashboards remain. “Search sessions” now searches session titles and workspace names, not message text; for organizations with OpenWork Models, Auto is replaced in the model picker by GPT-6 Luna.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Move your Claude Cowork setup to OpenWork with one prompt

• Move your Cowork setup with one prompt. Ask the agent you already use to follow openworklabs.com/migrate.md to bring your Claude Cowork and Claude Code plugins and skills into OpenWork. Re-running picks up changes without duplicates, reuses connections your organization already has, and explains when a connection still needs setup.
• Give each teammate their own connector key. For admins: external connections can use individual keys instead of one shared key. Members can add or replace their key from the Library or Den, using a masked entry form; desktop chat can guide them to add one when needed. For admins who use LiteLLM, connecting your own proxy is also available as a preview on request.
• Auto and Apps are available to more organizations. Free Auto no longer needs an organization-by-organization rollout, and every organization can build Apps without a platform admin enabling them. Auto can also read images you attach or that tools return, and signed-out Linux desktops no longer need a system keyring to use it.
• Self-hosting gains a Google Cloud Run starting point. For self-hosters: starter deployment files and instructions cover the Den API, Den web app, and migration job on Cloud Run. Old self-hosted Den settings that had no effect are no longer read.
• Everyday work is clearer and more dependable. Your first organization message now gets an answer before you have a workspace; videos made in a conversation's work folder play in chat; and stopping a run no longer leaves a bold “Step interrupted” row. Agent-led installs open on Setup complete without requiring Node first, and teammate invites survive workspace claiming. Model names and provider details are clearer. Workbot uses one quiet activity line and can react with emoji, while Slack runs wait for slow desktop work instead of reporting that they are stuck.
• Some desktop options have changed or are gone. Workspace sharing and remote-workspace connections have been removed. Organization Analytics is gone, while usage reporting remains in AI Gateway. Plugins now come from your organization's Library instead of being installed into workspaces, and the “From GitHub” plugin import is gone. The Library no longer has a card view. Automation choices now say Desktop or Cloud, and computer use has been removed from that editor.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Find shared connectors that still need your sign-in

• Shared connectors are easier to find. The Library now has a “Needs sign-in” filter for connectors shared with you that still need your sign-in. In Den, a sidebar dot also points out when something is waiting on you.
• Self-hosted first runs are faster. For self-hosters: openwork-server web opens your first folder in about a second on a fresh install, instead of taking 10+ seconds on Windows. It also no longer fails with “resource busy or locked” while installing the engine.
• Side chats no longer crowd the sidebar. Their chips have been removed from session rows, leaving more room for session names. Open a session to see its side chat.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Workflows and artifacts can use your connected tools

• Connected tools work in Workflows and artifacts. Live artifacts, on-demand Workflows, and scheduled Automations can now use connection tools and perform write actions. Large tool inputs, such as Notion database queries, also work.
• Work sent to your desktop reports back. If you use OpenWork from Slack or another connected app, you can now follow a desktop task's progress, read its conversation, send a follow-up, or stop it. Slack reports the result in the original thread, and tasks appear as normal chats using your chosen model.
• Auto works in more situations. Eligible organization members can use Auto alongside other models, and signed-out Auto is available to OpenWork builds and compatible clients. Deployments can disable Auto while keeping other models available.
• Chat and the built-in browser are clearer and more dependable. Model choices explain why a model is unavailable; OpenCode v2 now shows a Connect card when a service needs sign-in. The browser explains when a page cannot connect and offers Reload, and HTML file previews are isolated from the rest of OpenWork.
• For admins and self-hosters: Admins can choose “Only models you provide,” enable Slack progress updates, and review free Auto usage. Self-hosters can deploy with draft Terraform modules for AWS ECS Fargate or Kubernetes, including an existing ECS cluster.
• Other changes: OpenWork-built items are now called artifacts. Browser login sync and its setup controls are gone; sign in directly in the built-in browser. Organization-managed Dashboards are disabled by default and must be enabled per organization.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Enterprise sign-in and version pinning are back, plus Amazon Bedrock and model shortcuts

This release covers everything since v0.18.52. v0.18.53 was never published, so its changes are included here.

• Organization sign-in and allowed versions work again. OpenWork Enterprise and OpenWork Cloud desktops once again ask people to sign in to their organization before they start working, and desktop updates skip any version an admin removed from Allowed desktop versions. Other desktop policies stay saved but are not enforced on the desktop while they are redesigned.
• Amazon Bedrock in AI Gateway. For admins: add Amazon Bedrock and Amazon Bedrock (OpenAI) with an AWS region and access keys, and reuse the saved keys for the second one. Anthropic effort choices are kept through the gateway.
• Switch models with a key. In Settings › Keyboard shortcuts you can bind a key to a saved model with its reasoning level and Fast. ⌃⇧F (Ctrl+Alt+F on Windows and Linux) turns Fast on or off, and the model name shows "· Fast" while it's on.
• Chat keeps its place. Editing a message while a reply is running replaces it instead of queueing the edit. Conversations stay in their folder when an agent changes directory, and questions and approvals no longer disappear. You can switch between OpenCode engines from the command palette and choose whether to copy older chats across. Agent tool work is summarized by what it did instead of raw tool names.
• Simpler connector setup. For admins in OpenWork Cloud: API-key, custom sign-in, Google Workspace and Microsoft 365 connectors use the new setup flow and can be edited in place, and Plugins has clearer filters. Apps like Claude Code, Codex and Cursor can connect to OpenWork Connect without registering first, failed sign-ins explain what to do next, and the MCP docs have one-click Cursor and VS Code install links.
• Also in this release. Windows installers are published again. Updating no longer fails with a checksum error after a release is re-run. Update controls in Settings are more compact, a second OpenWork profile no longer stops the first one's engine, and the website shows OpenWork's completed SOC 2 Type II audit.

Self-hosted upgrades from v0.18.46 or earlier: this release applies database migrations 0095–0110. Stop den-api/den-web writers first, then run helm upgrade with --set migrations.writersStoppedFor0097=true --timeout 30m (and without --reuse-values). See the den-db README for details.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Manage your Library from the desktop, find anything from one + menu, and a rebuilt AI Gateway

• Your Library works fully on the desktop. You can now add, share, edit and delete skills, connectors and plugins without leaving the app. A new Connectors tab lists your connectors, adding one starts from a catalog with service logos, and an MCP server's address is checked before it's saved. Each item's page has Chat, which starts a task with that item ready to use, and Share on items you own. When a skill shapes an answer, chat names the skill. Signed out, the Library shows one clear Sign in to OpenWork Cloud button instead of an "Add to library" button that did nothing. Lists also load faster.
• One + menu in the composer finds everything. The paperclip and tools buttons are now a single + menu that opens on a search across your files, skills, connectors, plugins and commands. It still finds what you meant when you make a typo ("hubsopt" finds HubSpot). Attaching a file is the first option, or press ⌘U (Ctrl+U on Windows and Linux).
• Usage limits are clearer. When you reach your organization's usage limit, the chat says which limit you hit and when it resets, and you can ask for more right there. The account menu shows how much of each limit you have left, and the new Settings › Usage page has the details. The chat no longer also shows a misleading "too many requests" error under the limit.
• AI Gateway is rebuilt and available to every organization. For admins: AI Gateway is now a regular page in the sidebar. Add a provider from a catalog, then set its key, who can use it and which models in one form. Overview shows who spends what and on which models, with a page for each person. Limits lets you cap spend per day, week or month for everyone, a team or one person, and you can undo a deleted limit. Users & Teams shows everyone's providers, limits and last 31 days of spend. Mistral is now supported. Members can sign in to Gemini and Claude on Google Cloud with their own Google account from the new Models section of My Library, which replaces the old My Model Connections page.
• Connectors and plugins are simpler to manage. For admins in OpenWork Cloud: add a connector in a few steps, choose whether each person signs in or one account is shared by everyone, and pick which teams get it. Add any MCP adds a server that isn't in the catalog, or you can paste its address into the search. Manage › Plugins lists every plugin with who has it. You can create one and give it to teams right there, then search by name or filter by team or person. Removing a connector or plugin now asks first, and switching a connector to one shared account warns you before it signs you out. Owners can also approve their self-hosted OpenWork web address in Org settings so members can sign in there, even if they belong to several organizations.
• Also in this release. The first time you click a link, OpenWork asks whether to open it in OpenWork or your usual browser and can remember your choice. You can change it later in Settings › Preferences › Browser, or right-click a link to choose once. Session search and notifications sit next to the OpenWork name at the top of the sidebar, and window controls look native on macOS, Windows and Linux. The built-in browser no longer has a Suspend button. After you sign in, Settings › AI providers works right away, even before you create your first workspace. If you use OpenWork from Claude Code, Cursor or Codex, agents can update shared skills. When a long document or email is cut short, they're told the full length and how to read the rest.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Run OpenWork on your own server with one command

• Self-host OpenWork with one command. For self-hosters: npm i -g openwork-server && openwork-server web now runs the full OpenWork web app on a home server or VPS. It downloads the matching engine on first run and keeps its access tokens across restarts, and npm i -g openwork-server@latest updates it. Before, you had to clone and build the repo, install the engine yourself, and recreate tokens after every restart.
• Connecting an account in chat no longer gets stuck. When the agent needs you to connect a service, you now always get a clear card to connect or skip, with Try again if sign-in doesn't finish. Before, chat could wait forever on "Checking connection request…".
• Chat replies are simpler. Creating or sharing a skill, asking for a mockup, being asked for an environment variable, and browsing connectors now reply in plain text instead of embedded cards. The connection card is the only one that stays.
• Your email stays out of the sidebar. The account row now shows your name and "OpenWork Cloud" instead of your email address. Your email is still at the top of the account menu.
• If you use OpenWork from Claude Code, Cursor, or Codex: agents can now list your organization's skills and open any of them directly. Before, they had to guess search keywords, so organization skills often went unused.
• Clearer pricing everywhere. The website, docs, and sign-up now all show the same plans: Free, Team at $10 per seat per month, and Enterprise at $40 per user billed annually, with Cloud Computer and OpenWork models as add-ons. The website and docs also have refreshed branding.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Known open fixes

• #5218 (fatal browser-tab-limit crash) is not included. The release requester chose on 2026-09-22 to ship current reviewed dev without waiting for it.
• Open fork fixes #4317, #4215, #4061, #4007, #4005, #3970, #3903, #3414, #3413, #3403, #3401, #3389, #3373, #3352, #3326, #3317, #3180, #3134, #3119, #2907, #2901, #2838, #2611, #2466, #2355 remain unmerged; deferred for separate review, not claimed fixed here.
• Open fork PRs #4680, #4009, #3781, #3595, #3355, #2423, #2367 are broader or unrelated changes; #5190, #5215, #5221 concern translations. None were selected for this patch cut.

Agent sessions recover more reliably and provider connections stay consistent

• Conversations now reopen and continue more reliably, with history pages filling correctly and background streaming preserved.
• Mobile chat is easier to use, with steadier submission, scrolling, keyboard, composer, and sidebar behavior.
• Provider connections and cloud workspace startup now handle credentials, readiness, and recovery more reliably.
• Removed custom agents and added clearer linked task references and alpha build information.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Live workflow apps and session recovery become more dependable

• Live workflow authoring and generated apps now update and run with clearer, bounded behavior.
• Sessions recover more reliably, keeping the send button usable and opening sidebar-created threads in the main pane.
• Browser tabs, consent, scrolling, and session origins now stay aligned across desktop and web flows.
• Organization tools and saved apps now present and connect more consistently.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

MCP Apps become easier to set up and safer to use

• MCP Apps now show external setup links, can use bound resources, and appear in a more compact dashboard layout.
• Live apps now have a read-only execution boundary, while gated actions use clearer in-app approval.
• Fixed app discovery, actions, errors, and refresh behavior so interactive apps stay available and dependable.
• Sessions preserve workbench continuity and message order more reliably during navigation and streaming.
• Improved browser previews, OAuth refreshes, model settings, and cloud runtime behavior.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Enterprise updates and policy plugins stay safely scoped

• Managed policy engine plugins are unregistered cleanly.
• The updater stays inactive until enterprise activation.
• The compose evaluation stack stays pinned to the 0.18.45 images.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Cloud connections unify and desktop recovery gets stronger

• Google Workspace support now runs through Cloud Connect, with working Gmail, Calendar, Drive, Sheets, and Microsoft 365 actions.
• Desktop now recovers credentials and cloud sessions more reliably, while startup errors show a recovery screen instead of a blank window.
• Browser and desktop users get native page context menus and right-click menus.
• Launchable openwork-server and AUR binaries ship reliably, and published desktop releases can open to a blank starting point.
• Automation runs, analytics pagination, Gmail draft attachments, and session transcript loading are more dependable.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.

Sessions preserve live progress and drafts

• Sessions now preserve live progress when cached threads are restored.
• Composer drafts stay in place, and instant sends are verified.
• Shared callback modes are recorded correctly for isolated MCP rows.
• Removed the legacy embedded connection app and gateway launch path.

Full changelog: https://openworklabs.com/docs/changelog · Compare

Windows installers are signed using Microsoft Artifact Signing.