Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Configures per-user sessions in a shared AI workspace with sandbox isolation, user profiles, and relationship-aware context. Each user gets their own session key, an optional Docker container for file isolation, and a profile file the assistant reads at session start. Relationship files define what information can cross user boundaries.
Enables multi-user AI workspaces on a single installation by routing sessions to per-user Docker containers based on session key patterns, without requiring separate deployments.
When to use it
- Giving a contractor sandboxed access to an AI assistant without exposing other users' files
- Running separate AI sessions for multiple team members on a shared server
- Tracking relationships between users to control cross-user information sharing
- Assigning different tool permissions to admins versus guests in one workspace
- Maintaining personalized assistant context for each user via profile files
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: start a session as bob
- 1Reads session key via session_status to extract userId 'bob'
- 2Loads FRIENDS/bob.md to retrieve Bob's profile and preferences
- 3Scans RELATIONS/ for files matching 'bob' to load relationship context
- 4Applies Bob's sandbox configuration from openclaw.json with isolated /workspace directory
- 5Greets Bob by name with personalized context loaded
Session initialized with Bob's profile, relationships, and sandboxed workspace mounted at /workspace
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.