opencode-primitives
🎯Skillfrom different-ai/openwork
|opencode-primitives skill from different-ai/openwork
Installation
npx skills add https://github.com/different-ai/openwork --skill opencode-primitivesSkill Details
Overview
[](https://discord.gg/VEhNQXxYMB)
# OpenWork
> The easiest way to create safe agentic workflow and share them with your team
OpenWork is built on top of [opencode](https://opencode.ai) it lets you turn your opencode config into usable experiences for non-technical users.
It's an extensible, open-source alternative to “Claude Work”.
Openwork is desgined around the idea that you can easily ship your
It’s a native desktop app that runs OpenCode under the hood, but presents it as a clean, guided workflow:
- pick a workspace
- start a run
- watch progress + plan updates
- approve permissions when needed
- reuse what works (commands + skills)
The goal: make “agentic work” feel like a product, not a terminal.
Alternate UIs
- Owpenbot (WhatsApp bot): a lightweight WhatsApp bridge for a running OpenCode server. Install with:
- curl -fsSL https://raw.githubusercontent.com/different-ai/openwork/dev/packages/owpenbot/install.sh | bash
- run owpenbot setup, then owpenbot whatsapp login, then owpenbot start
- full setup: [packages/owpenbot/README.md](./packages/owpenbot/README.md)
Quick start
Download the dmg here https://github.com/different-ai/openwork/releases (or install from source below)
Why
Current CLI and GUIs for opencode are anchored around developers. That means a focus on file diffs, tool names, and hard to extend capabilities without relying on exposing some form of cli.
OpenWork is designed to be:
- Extensible: skill and opencode plugins are installable modules.
- Auditable: show what happened, when, and why.
- Permissioned: access to privileged flows.
- Local/Remote: OpenWork works locally as well as can connect to remote servers.
What’s Included
- Host mode: runs opencode locally on your computer
- Client mode: connect to an existing OpenCode server by URL.
- Sessions: create/select sessions and send prompts.
- Live streaming: SSE
/eventsubscription for realtime updates. - Execution plan: render OpenCode todos as a timeline.
- Permissions: surface permission requests and reply (allow once / always / deny).
- Templates: save and re-run common workflows (stored locally).
- Skills manager:
- list installed .opencode/skills folders
- install from OpenPackage (opkg install ...)
- import a local skill folder into .opencode/skills/
Skill Manager
Works on local computer or servers
Quick Start
Requirements
- Node.js +
pnpm - Rust toolchain (for Tauri): install via
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh - Tauri CLI:
cargo install tauri-cli - OpenCode CLI installed and available on PATH:
opencode
Install
```bash
pnpm install
```
OpenWork now lives in packages/app (UI) and packages/desktop (desktop shell).
Run (Desktop)
```bash
pnpm dev
```
Run (Web UI only)
```bash
pnpm dev:ui
```
Arch Users:
```bash
yay -s opencode # Releases version
```
Architecture (high-level)
- In Host mode, OpenWork spawns:
- opencode serve --hostname 127.0.0.1 --port
- with your selected project folder as the process working directory.
- The UI uses
@opencode-ai/sdk/v2/clientto:
- connect to the server
- list/create sessions
- send prompts
- subscribe to SSE events
- read todos and permission requests
Folder Picker
The folder picker uses the Tauri dialog plugin.
C
More from this repository6
solidjs-patterns skill from different-ai/openwork
tauri-solidjs skill from different-ai/openwork
openwork-core skill from different-ai/openwork
opencode-bridge skill from different-ai/openwork
opencode-mirror skill from different-ai/openwork
get-started skill from different-ai/openwork