multi-workplace
dickwu tarafından
Web & Frontend DevelopmentÖzet
Manage multiple workplaces (project directories) with multi-agent orchestration, isolated memory, and inter-agent.
Açıklama
Bu Beceri Ne Yapar
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.
Ne Zaman Kullanılır
- 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
Örnek İş Akışı
User asks: initialize a workplace for my project at ~/projects/api
- 1
Read current.json to check active workspace
- 2
Run workplace init ~/projects/api, scanning for .git and existing markdown files
- 3
Analyze project type and suggest agent roles (e.g. coder.md, reviewer.md)
- 4
Create .workplace/ structure, write config.json with UUID and path, register in registry.json
- 5
Set 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.
Kurulum
clawhub install dickwu/multi-workplaceCLI komutunu çalıştırın ya da istemi Claude Code, Cursor, Codex veya kullandığınız kodlama ajanına yapıştırın.