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.
