Friends

Configure per-user sessions with sandbox isolation, friend profiles, and relationship awareness.

Core Concepts

• - UserId: Lowercase unique identifier (e.g., alice, bob). Used in session keys, filenames, and cross-references.
• Session: One session per user, named agent:<agentId>:<mainKey> where mainKey typically contains the userId.
• Sandbox: Optional Docker isolation per session, configured in openclaw.json.
• FRIENDS/: User profile directory (one file per user, named {userId}.md).
• RELATIONS/: Relationship directory (files named {userId1}-{userId2}.md, alphabetically sorted, can be mutiple users).

Example Workspace Structure

CODEBLOCK0

USER.md

Registry of all users. The assistant reads this to identify users and extract userId and Name.

Format:

CODEBLOCK1

Note: userId is unique and in lower case. Use Role to determine sandbox configuration in openclaw.json.

FRIENDS/

User profiles. One Markdown file per user, named {userId}.md.

Content is flexible. Common sections include:

CODEBLOCK2

RELATIONS/

Interpersonal relationships. Files named {userId1}-{userId2}.md (alphabetical order, can be mutiple users).

Content is flexible. Example:

CODEBLOCK3

AGENTS.md

Instructions for the assistant. Add this section:

CODEBLOCK4

Session Configuration

Each user gets an isolated session with configurable sandbox and tool permissions. Configure via openclaw.json.

Administrator Configuration

Full access, no sandbox restrictions:

CODEBLOCK5

Guest Configuration

Sandboxed session with isolated workspace. Guest can read/write/execute in their own directory only:

CODEBLOCK6

Directory Setup:

CODEBLOCK7

Notes:

• - Guest sees /workspace as their root (isolated from main workspace)
• Can read/write/execute freely within their directory
• Cannot access USER.md, FRIENDS/, RELATIONS/, or other guests' data

Configuration Options

Sandbox:

• - mode: "off" | "all" — Disable or enable sandbox
• INLINECODE19: "session" — One container per user session
• INLINECODE21: "none" | "ro" | "rw" — Workspace file access

Tools:

• - allow: Array of permitted tool names
• INLINECODE26: Array of prohibited tool names (overrides allow)

Routing:

• - bindings[].match.session.regex: Match session key pattern (e.g., alice$ matches sessions ending with "alice")