Zosma Cowork 🇮🇳

English | 中文 | Español | 日本語 | Deutsch | Français | Português | Русский | 한국어 | हिंदी

📖 Documentation: cowork.zosma.ai

A desktop agentic work harness built on pi, the minimal, language-agnostic coding agent harness. Streaming, thinking, tool calls, multi-turn sessions — all free, all open-source, all local.

Built by Zosma AI.

Gallery

Invoice processing with natural language agents. See more demos at zosma.ai/zosma-cowork/gallery

Why Zosma Cowork?

🌟 Built on pi

Zosma Cowork is a desktop application built on pi — the minimal, language-agnostic coding agent harness. pi's philosophy of simplicity and composability carries directly into your desktop experience. Every pi extension works out of the box, with zero wrappers or adapters.

🆓 Free & Open Source

Zosma Cowork is 100% free and open-source (MIT). Bring your own API key, use an existing subscription (Claude, ChatGPT, Copilot), or run local models — you stay in control.

🧩 Full pi Extension Ecosystem

The pi ecosystem includes hundreds of extensions, skills, tools, prompts, and themes — all compatible with Zosma Cowork. Plug them into your ~/.zosmaai/cowork/ directory and they just work. No wrapping, no porting, no lock-in.

Features

• Node.js agent sidecar — The pi-mono TypeScript SDK runs in a managed sidecar process for full agent capabilities (extensions, tools, providers)
• Thin Tauri relay — The Rust layer is a minimal IPC bridge between React and the sidecar, keeping the native desktop shell lightweight
• pi extension ecosystem — Compatible with pi extensions via DefaultResourceLoader — skills, tools, and prompts auto-discovered from ~/.zosmaai/cowork/
• Multi-turn sessions — Full conversation continuity with persistent session history
• Streaming responses — See the agent think, write, and call tools in real-time
• Thinking blocks — Expandable reasoning from the model
• Tool call timeline — Live bash/edit/write tool calls with args and results
• Session management — Persistent chat sessions saved to ~/.zosmaai/cowork/
• Light & dark mode — Warm cream light mode, warm charcoal dark mode
• Keyboard shortcuts — Cmd/Ctrl+Shift+K to focus, Cmd/Ctrl+N for new session
• Abort & steering — Stop a running agent mid-turn, send follow-up steering messages
• Claude-inspired UI — 3-column layout with sidebar, workspace, and info panel

Architecture

The diagram is generated from assets/architecture.mmd. To update:

# Edit assets/architecture.mmd, then re-render:
mmdc -i assets/architecture.mmd -o assets/architecture.png -t default -b white -w 900 -H 700 -s 2

See the full Product Roadmap for phased plans, competitive positioning, and technical decisions.

System Architecture — Full stack: React → Rust → Node sidecar → pi SDK

Communication Flow — Sequence diagram: streaming events pipeline

Extension Ecosystem — 4 tiers: installed, vendored, planned, future

Competitive Positioning — Quadrant chart vs Cursor, Hermes, Slack AI

Roadmap Timeline — Gantt chart: 6 phases, 28 weeks

Data Flow — User → App → Agent → Storage layers

Tech Stack

Development

Prerequisites

• Node.js 22+
• Rust 1.85+ (for Tauri desktop shell)

Quick Start

# Install frontend dependencies
npm install

# Install agent-sidecar dependencies
cd agent-sidecar && npm install && cd ..

# Run frontend dev server
npm run dev:frontend

# Run full Tauri app (frontend + Rust relay + Node.js sidecar)
npm run dev

npm run dev runs the sidecar from TypeScript source via tsx — no bundle needed. On a fresh checkout it auto-generates lightweight dev stubs for the Tauri bundle resources (src-tauri/agent-sidecar/index.cjs, src-tauri/binaries/node) so the Rust shell can compile. The real sidecar bundle and Node.js binary are produced only by the production build (npm run build).

Scripts

# Frontend
npm run lint          # Biome lint
npm run typecheck     # TypeScript check
npm run test          # Vitest run
npm run validate      # lint + typecheck + test
npm run format        # Biome format

# Tauri
npm run build:frontend
npm run build         # Build release binary

# Agent Sidecar
cd agent-sidecar
npm run build         # TypeScript → JavaScript
npm run dev           # tsx watch (standalone development)

# Rust (Tauri relay only)
cargo fmt --all --check
cargo clippy --workspace -- -D warnings

Staging builds

Every merge to main produces unsigned cross-platform installers via the Staging Build workflow (.github/workflows/staging-build.yml). The bundles are attached as workflow artifacts (14-day retention) and a Discord embed with auth-free nightly.link download URLs is posted to whatever channel the DISCORD_STAGING_WEBHOOK repo secret points at (typically #staging-builds).

This flow does not create a GitHub Release, tag a commit, or publish to AUR / winget / Homebrew — those side-effects remain gated on the tag-triggered release.yml. See issue #133 for the design.

To run a staging build on demand, trigger Staging Build from the Actions tab via Run workflow.

One-time setup: in Discord, open the target channel → Edit Channel → Integrations → Webhooks → New Webhook, copy the URL, then add it as a GitHub repo secret named DISCORD_STAGING_WEBHOOK (Settings → Secrets and variables → Actions → New repository secret). The workflow degrades gracefully — if the secret is unset the notify job emits a warning and exits 0, so the build itself still succeeds and the artifacts are still uploaded.

Config & Data

IPC Protocol

The Tauri relay communicates with the Node.js sidecar via stdin/stdout JSON lines:

Commands (→ sidecar):

Events (← sidecar):

Project Structure

zosma-cowork/
├── agent-sidecar/                # Node.js agent process
│   └── src/
│       └── index.ts              #