Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Hierarchical /workplace navigation: parent→child drill-down with inline buttons, parent:child colon syntax for direct switching, auto-init parent folders (no .git) with recursive child init and cross-linking
What This Skill Does
Manages multiple project directories as named workplaces, each with isolated memory, agent role definitions, and deployment configs stored in a .workplace/ folder. Auto-detects git repos and registers them in a central registry. Supports switching between workplaces and syncing context to Cursor, Claude Code, and OpenCode.
Per-workspace isolation means agent memory, skills, and deployment docs never bleed across projects, which flat single-workspace setups cannot guarantee.
When to use it
- Switching between client codebases without losing per-project agent context
- Running a reviewer agent in one project while a coder agent works in another
- Syncing active project context to Cursor or Claude Code before starting a session
- Discovering all git repos under a directory and registering them as workplaces
- Exporting a workplace config to share project setup with a teammate
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: initialize a workplace for my project at ~/projects/api
- 1Read current.json to check active workspace
- 2Run workplace init ~/projects/api, scanning for .git and existing markdown files
- 3Analyze project type and suggest agent roles (e.g. coder.md, reviewer.md)
- 4Create .workplace/ structure, write config.json with UUID and path, register in registry.json
- 5Set new workplace as current and run workplace sync all to update IDE context files
Workplace 'api' initialized at ~/projects/api with 2 agents (coder, reviewer). Context synced to CLAUDE.md and .cursor/rules/workplace.mdc.