workplace

What This Skill Does

The Workplace skill acts as the central orchestration hub for OpenClaw, enabling users to manage multiple project environments simultaneously. By organizing projects into discrete workplaces—each with its own isolated memory, specific agent configurations, and deployment settings—the skill ensures that an agent's context remains relevant to the current codebase. It auto-detects .git repositories to initialize projects and maintains a hidden .workplace/ configuration directory for each. The skill features a powerful hierarchical navigation system via the /workplace slash command, allowing users to drill down into parent-child workspace structures or use colon-based shorthand for immediate switching. It also manages agent lifecycles, including starting and stopping background kernel agents, and provides robust synchronization for IDEs like Cursor and Claude Code.

Installation

To integrate this skill into your OpenClaw environment, use the internal skill registry via your terminal or management interface: clawhub install openclaw/skills/skills/dickwu/multi-workplace Once installed, you can trigger the functionality via the /workplace command or by referencing 'workplace' in your natural language prompts. Ensure you have the necessary write permissions in your project root to allow the .workplace directory creation.

Use Cases

• Multi-Project Management: Developers handling multiple microservices or monorepo components can switch between contexts instantly without manual path navigation.
• Agent Orchestration: Users can launch specialized 'kernel' agents that persist throughout a session, or toggle specific sub-agents tasked with automated testing or documentation generation.
• Environment Deployment: Configure and deploy specific environments (staging, production, or testing) that are strictly bound to the active workplace, reducing the risk of cross-environment errors.
• Context Synchronization: Keep your AI IDEs (Cursor/Claude Code) in sync with the current active project by running the sync command to generate relevant context markers.

Example Prompts

1. "/workplace list and switch to the 'auth-service' directory, then start the test-runner agent."
2. "I need to deploy the current project to staging. Can you use the workplace deploy command to set that up?"
3. "Sync my current codebase context to Cursor so it can see the changes in the user-profile module."

Tips & Limitations

• Colon Syntax: Use parent:child notation to skip the menu system and switch directly to nested sub-projects.
• Persistence: Always use workplace kernel stop when finishing work to avoid orphaned agent processes in the background.
• Permissions: The skill requires read/write access to your local filesystem to manage the .workplace/ directory and registry files. If you encounter issues, ensure your IDE or terminal has sufficient system permissions to modify project hidden files.