OpenWork Release Notes

• 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.</Update>

<Update label="October 3rd" tags={["🚀 New Features", "🐛 Bug Fixes", "🏗️ Refactoring"]}>

• 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. …

• 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. …

• 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. …

• 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. …

• Desktop connection status now uses one clear native card, while sign-in and managed credentials recover more reliably.
  • Browser tasks can use site tools, page controls, tab suspension and reload, selected logins, and user takeover.
  • Agent runs recover more smoothly from stalled sends, interruptions, restarts, and follow-up turns, with drafts and sent messages staying visible.
  • Computer Use adds hosted approval, native previews, scoped sessions, and continuation after takeover or refresh.
  • Organization access, workflow apps, analytics, onboarding, and desktop policies are clearer and more dependable.</Update>

<Update label="September 2nd" tags={["🚀 New Features", "🐛 Bug Fixes", "🏗️ Refactoring"]}>

• 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.
  • Published the SOC 2 badge and compliance status on the landing page.
  • Hardened security by fixing static-analysis findings and isolating provider sync contexts, alongside internal test and release tooling improvements.</Update>

<Update label="August 31st" tags={["🚀 New Features", "🐛 Bug Fixes", "🏗️ Refactoring"]}>