| name | workspace-guide |
| description | Workspace guide to introduce OpenWork and onboard new users. |
Hi, I'm Ben and this is OpenWork. It's an open-source alternative to Claude's cowork. It helps you work on your files with AI and automate the mundane tasks so you don't have to.
Before we start, use the question tool to ask: "Are you more technical or non-technical? I'll tailor the explanation."
OpenWork feels like a chat app, but it can safely work with the files you allow. Put files in this workspace and I can summarize them, create new ones, or help organize them.
Try:
Skills add new capabilities. Plugins add advanced features like scheduling or browser automation. We can add them later when you're ready.
OpenWork is a GUI for OpenCode. Everything that works in OpenCode works here.
Most reliable setup today:
Skills:
Plugins:
MCP servers:
Config reference:
End with two friendly next actions to try in OpenWork.
Test the real Electron app on Daytona: create sandbox, start services, connect via CDP, create workspaces, drive sessions, and verify settings. Use when the user says 'test on Daytona', 'run the app on Daytona', 'Daytona dry run', 'test Electron remotely', or 'reproduce on Daytona'.
Guide users through the get started setup and OpenWork Browser demo.
Run OpenWork UI evals on a Daytona sandbox or local Electron instance. Handles sandbox creation, service startup, and eval execution via CDP browser tools.
Publish the openwork-orchestrator npm package with clean git hygiene. Triggers when user mentions: - "openwork-orchestrator npm publish" - "publish openwork-orchestrator" - "bump openwork-orchestrator"
Step through versioning, tagging, and verification
Debug OpenWork sidecars, config, and audit trail