OpenWork v0.18.59

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.