Biggest misconceptions bout OpenWork is that we're a desktop app. OpenWork is a way to deploy AI capabilities safely to your team. Whether it's MCPs, AI Models, or skills - admins can configure them all in OpenWork and distribute them across a wide way of surfaces. Different harnesses, slack, simple chat interfaces, or the desktop app are all supported.

Live Artifacts are live in OpenWork. You can know create small dashboard directly from the chat. The OpenWork twist on "Artifacts" is that it can use any data from your MCPs and package them into shareable widget-like surfaces. Check this example where I create a dashboard for a Notion CRM.

We have ZDR at home The ZDR at home:

We invested a lot in custom testing tooling for OpenWork. We can test complex setups across different OS and network conditions, and make it repeatable. All in deterministic .ts code. Not agent-driven, but made for agents to write, run, and debug.

You can now create Custom Dashboards right from within OW. Custom dashboard takes any tools from the MCPs you connect to OpenWork and allows you to display rich interactive UIs. All built on standards (MCP Apps + Code Mode)

We shipped Workflows in @getopenwork Workflows give you n8n-type determinism with the convenience of LLMs. When you do some tool calls you can say something like "remember this as a workflow" and it will create a deterministic script that can be (re-)run. We didn't re-invent the wheel this is possible via Code Mode pattern. And it composes with everything else we've been building: - Works from the Web or Desktop - Works against automations (much cheaper to run automations) Let us know if you find it cool

Introducing OpenWork Web OpenWork Web gives you a computer in the cloud with the entire @getopenwork experience. Just sign in and you get access to your entire OW ecosystem right there. All the skills, MCPs, and AI providers are instantly available.

Introducing OpenWork Dashboard (powered by MCP Apps) OpenWork Dashboard is a way to provide instant information to your team. Yeah, yeah, you're probably thinking, "We used to have dashboards in the past. Isn't it all about chatting now?" It is still about the chat, but the chat isn't a good way to get information fast. Custom dashboards are still the way to go. So how is this different? We use MCP Apps under the hood. If you don't know what they are, check out the video below (spoiler alert: it's MCP that outputs some UI).

Today we’re releasing OpenWork Connect. OpenWork started as a free, open-source desktop app. The goal was to make the fully configured agent experience I had in OpenCode available to coworkers who did not want to set up repositories, copy configuration files, or learn a new developer tool. But we tried to put too much into one app. The person building workflows and the person using them often need completely different interfaces. OpenWork Connect separates those two experiences. You can now take the skills, MCPs, and workflows you already use in OpenCode, Codex, Claude Code, Cursor, or OpenWork and share them directly with your coworkers. Assign a workflow to Susan and it appears inside her OpenWork automatically. She does not need to install the skill or copy an MCP configuration. If a service requires her account, she signs in once and continues. The same setup also works in the other direction. Add the OpenWork MCP to Codex, Claude Code, OpenCode, or another compatible agent and you can access the same skills and connections from there too. Your setup is no longer tied to one app, one agent, or one computer. This is live today for OpenWork users. It replaces a lot of copying, manual installation, and forcing everyone on a team to use the same interface. It also changes where OpenWork can go next. The desktop app remains the main surface today, but we are working toward bringing the same workflows to Slack, mobile, and wherever people already communicate and work.

VCs are big-braining what "ai multiplayer" means. Multiplayer is not a new UX, it's making old UX work seamlessly with AI agents. Your coworkers are already using notion, slack, google docs, gmail - you're already doing multiplayer. The problem with agents is: a) how can you securely (and easily) give them access to the same tools. b) how to give them shared context while they use these various tools.

Introducing AI Adoption Dashboard in @getopenwork Companies spent the last 6 months investing in AI tools. Now they’re asking: Is anyone actually using this? Today, we shipped the first version of the dashboard. Starts simple: - who in your org uses ai - how active they are - how many sessions / tasks are happening Next up, we're going to map out how it actually helps save time and where the bottlenecks are.

ok sorry guys, but openai realtime is really dope super scrappy demo of how it works inside of openwork shipping tomorrow in the app

I should've stopped at that tweet, but I didn't.

We just crossed 15k stars on github + our daily signups 10x in May.

Day 2 of making OpenWork 💅 - New org onboarding screen — sign in and immediately see what your team set up (providers, marketplaces, workers) - Pick your default model right from onboarding - Cloud vs local provider badges so you know where things come from - Toast when new providers get added — click to pick a new default - Model picker redesign: provider accordions, recommended models, choose exactly which models show up in your session - Can't accidentally disconnect cloud-managed providers anymore - Clean sign-out that actually cleans up

The big one: shell customization. You can now toggle sidebar, status bar, docs, feedback, model picker, browser panel, welcome page -- all from settings. This is the foundation for white-labeling. Change the app name, hide what you don't want users touching. Locally today, cloud-managed soon.

AI providers/models got their own global settings section. Separated from General so it's not buried. Uses the same components as the Cloud dashboard.