# Redacted real XMAN operator session

```xstage
name: Redacted real XMAN operator session
tickMs: 26
charsPerTick: 2
lineDelayMs: 175
chapterPauseMs: 5600
palette.prompt: #B7F2C9
palette.heading: #EAC2D2
palette.pass: #96EFBD
palette.observed: #A7CAFF
palette.info: #8CBDF4
palette.wait: #F8C780
palette.redact: #F1A3B3
palette.metric: #F1E3CF
palette.neutral: #E5EBF4
palette.visitor: #C6F4D5
palette.simulated: #C4B2F2
```

## 01 / UPGRADE & STARTUP

```xstage
id: startup
tab: Startup
title: 01 / UPGRADE & STARTUP
proof: MANAGER ANSWERED STARTUP PROBE
```

```slide
id: upgrade
position: right
at: start
```

```slide
id: alex-updates
position: right
at: line:12
```

```terminal tone=prompt
$ ./xman.sh autosetup
```

```terminal tone=heading
XMAN  / START XMAN
```

```terminal tone=neutral
Step 1 of 4
```

```terminal tone=info
[INFO] Installing/checking XMAN…
```

```terminal tone=metric
DETECTED               Existing version — update available
```

```terminal tone=neutral
PREVIOUS VERSION SAVED
```

```terminal tone=redact
[REDACTED: private recovery location]
```

```terminal tone=info
[INFO] Starting XMAN…
[INFO] Waiting for the installed manager startup probe
```

```terminal tone=observed
[OBSERVED] The installed manager answered its startup probe. Checking
```

```terminal tone=neutral
setup access next.
```

```terminal tone=metric
AUTOMATIC STARTUP      Enabled for your user account
```

```terminal tone=pass
✅ [READY] Boot startup is enabled, including before you sign in.
✅ [READY] XMAN is installed and its manager is responding to setup.
```

## 02 / OPENCLAW CONNECTION

```xstage
id: bridge
tab: Bridge
title: 02 / OPENCLAW CONNECTION
proof: AUTHENTICATED CALL REACHED XMAN
```

```slide
id: connection
position: right
at: start
```

```terminal tone=heading
XMAN  / CONNECT OPENCLAW TO XMAN
```

```terminal tone=neutral
Automatic detection, narrow tool access, and a real agent test
```

```terminal tone=metric
NATIVE VERSION         OpenClaw 2026.10.9 (8b18b55)
```

```terminal tone=redact
CONNECTED AGENTS       [REDACTED: agent identifiers]
```

```terminal tone=info
[INFO] Checking the current master assignment
[INFO] Validating the completed native configuration.
[CONFIGURED] Plugin and native tool configuration applied. Checking the
```

```terminal tone=neutral
master connection next.
```

```terminal tone=heading
CONNECTION CHECKS
```

```terminal tone=metric
PLUGIN INSPECTION      loaded
TOOL REGISTRATION      Reported
```

```terminal tone=neutral
Verify the configured connection with a model call? [Enter = 1]
> [automatic Enter default]
```

```terminal tone=info
[INFO] Testing the selected agent through its configured model (command
```

```terminal tone=neutral
timeout 60s). This is separate from saving the settings.
```

```terminal tone=pass
✅ [PASS] An authenticated capability request from the tested agent reached
```

```terminal tone=neutral
XMAN. New turns can obtain its live role and instructions.
```

## 03 / RESOURCE BOUNDARIES

```xstage
id: resources
tab: Resources
title: 03 / RESOURCE BOUNDARIES
proof: MEASURED POLICY SAVED
```

```slide
id: budgets
position: right
at: start
```

```terminal tone=heading
XMAN  / CPU AND MEMORY PERMISSIONS
```

```terminal tone=neutral
Step 4 of 4
SAVED RESOURCE PERMISSIONS
```

```terminal tone=metric
CURRENT MODE           Automatic within saved limits
```

```terminal tone=heading
MEASURED HOST CAPACITY
```

```terminal tone=neutral
💻 PLANNING RAM CEILING  7330 MiB
💻 AVAILABLE RAM         4122 MiB
🧮 LOGICAL CPUS          4
```

```terminal tone=heading
PROPOSED ALLOCATION BOUNDARIES
```

```terminal tone=neutral
💻 MEMORY BUDGET         4096 MiB
🧮 CPU BUDGET            4 CPU equivalents
🏠 HOST HEADROOM         1832 MiB
👑 MASTER MEMORY         916 MiB
👑 MASTER CPU            0.75 CPU equivalents
💻 WORKER MEMORY POOL    3072 MiB
🧮 WORKER CPU POOL       3 CPU equivalents
```

```terminal tone=metric
AUTOMATIC CHANGES      Within these limits
```

```terminal tone=pass
✅ [PASS] Measured policy saved. Running container limits remain unchanged;
```

```terminal tone=neutral
future requests enforce the master allowance and combined budgets.
```

## 04 / VERIFIED ENROLLMENT

```xstage
id: containers
tab: Containers
title: 04 / VERIFIED ENROLLMENT
proof: FOUR NATIVE AGENTS VERIFIED
```

```slide
id: enrollment
position: right
at: start
```

```terminal tone=info
[INFO] Checking native ownership and automatically connecting containers
```

```terminal tone=neutral
(up to 90 seconds)
```

```terminal tone=metric
CONTAINER MANAGEMENT   Balanced — automatic verified enrollment
MANAGED CONTAINERS     4
```

```terminal tone=observed
[OBSERVED] Verified native containers are connected. New containers and
```

```terminal tone=neutral
replacements are checked every 30 seconds. Discovery leaves
current limits unchanged.
```

```terminal tone=pass
✅ [PASS] Deferred discovery completed: 4 native agents verified.
```

```terminal tone=heading
XMAN  / SETUP REVIEW
```

```terminal tone=metric
MANAGER                Running and responding
MASTER                 main
RESOURCE CHANGES       Automatic within your limits
SCRIPTS AND ROOT       Your review and explicit approval are required
CONTAINER MANAGEMENT   Balanced — automatic verified enrollment
MANAGED CONTAINERS     4
MASTER CONNECTION      Authenticated call observed during this setup
```

## 05 / OPERATOR APPROVALS

```xstage
id: approvals
tab: Approvals
title: 05 / OPERATOR APPROVALS
proof: ROOT ACTIONS WAIT FOR OPERATOR
```

```slide
id: approvals
position: right
at: start
```

```slide
id: nemoclaw-perspective
position: right
at: line:12
```

```slide
id: crew-invitation
position: right
at: end
```

```terminal tone=neutral
The goal is fewer routine interruptions: you set the boundaries, your
master plans, and XMAN checks requests before acting. Root scripts still
wait for your review. Setup explains each grant before you save it;
selecting a master does not grant unrestricted access.
The daemon schedules routine resources without a model. A coordinator can
advise on competing priorities and answer help requests; it cannot approve
root actions.
```

```terminal tone=wait
⚠️ [WARNING] Security mode: Balanced is the recommended starting point. It
```

```terminal tone=neutral
allows routine work within the permissions and resource limits
you approve. Root scripts and sensitive exceptions still
require your decision. Strict requires more human intervention;
Routine use inside this grant needs no repeated permission request.
Resource changes go directly to the daemon and its policy checks.
Additional capabilities use Special Requests. Review the exact connection
plan before it is applied.
```

```terminal tone=metric
SCRIPTS AND ROOT       Your review and explicit approval are required
```

```terminal tone=neutral
EXTRA NETWORK / MOUNTS Beyond the reviewed baseline: Special Request and
operator handoff
```

