Official Verified

workplace

Manage multiple workplaces (project directories) with multi-agent orchestration, isolated memory, and inter-agent communication. Use when the user mentions: workplace init/list/switch/scan/status/agents/export/import, managing projects, switching between codebases, multi-agent workflows, agent handoff, kernel agent, workspace structure, deploy environments, or any variation of "workplace" commands. Also triggered by /workplace slash command. Auto-detects .git folders as workplaces. Each workplace has its own agents, memory, skills, and deployment configs in a .workplace/ directory. Syncs context to Cursor, Claude Code, and OpenCode. Interactive Telegram/Discord UI with inline buttons for switching workplaces, starting agents, and deploying.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/dickwu/workplace

Download Source Code (.zip)

Workplace Skill

Manage multiple project workplaces with per-workspace agents, isolated memory, and Swarm-style agent orchestration.

/workplace Command (Telegram / Slash)

Hierarchical navigation with parent → child drill-down.

/workplace or /workplace list → Show top-level view: parent workspaces and standalone workplaces as buttons. Parents show (N) child count. Current workspace marked with ✓.
Click a parent button → Drill into children. Shows child buttons + "Use parent" + "← Back".
/workplace <name> → If standalone or child, switch directly. If parent with children, show drill-in.
/workplace parent:child → Direct switch using colon syntax (e.g. log-stream:logstream).
/workplace status → Current workspace card with parent, linked, agents, deploy envs.
/workplace agents → Agent list with start/stop buttons.

Colon Syntax

/workplace log-stream:logstream resolves parent by name, then finds child under that parent. Supports quick switching without navigating menus.

Context Switching

When the user switches workplaces (via button click, name, or colon syntax):

Update ~/.openclaw/workspace/.workplaces/current.json with the selected UUID and path
Update lastActive in registry.json
Load the new workspace's .workplace/config.json for context
Send confirmation: name, path, parent (if any), linked workplaces, agent list
Check sessions.json for the target workplace UUID:
- Has sessions → show session buttons ("Continue: {label}" + "New chat session")
- No sessions → auto-create a new session, confirm in the switch message
Subsequent messages in the session should be aware of the active workspace context

Read current.json at the start of any workplace operation to know which workspace is active.

See telegram-ui.md for full button layouts, callback routing, and platform fallbacks.

Quick Reference

Read Full Documentation on GitHub

Metadata

Author@dickwu

Stars2387

Updated2026-03-09

View Author Profile

AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill

Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-dickwu-workplace": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.

Related Skills

workplace

dickwu 2387