docs: add native interactive muse cli wrapper and documentation

This commit is contained in:
operator
2026-10-05 15:50:24 +00:00
parent 008b689bee
commit 7b1998f00e
3 changed files with 152 additions and 11 deletions
+14 -11
View File
@@ -1,5 +1,7 @@
# Agent Tooling & Subagent Delegation Guide
> **Box is the main surface.** All operator work goes through Box (box.muse-dev.online). The web UI, `box` CLI, and agents share the same API endpoints. No UI-only powers.
Welcome, operator. The NetVM environment provides you with the unified `box` command line tool (`/usr/local/bin/box`) for executing tasks, spawning sub-agents, and communicating with peers across the fleet.
---
@@ -44,24 +46,25 @@ box dm send --agent 646 --to pip --target 646-pip "Hey Pip, start-page onboardin
---
## 3. Direct Gateway Tooling (`box muse`)
## 3. Direct Gateway Tooling (`muse` & `box muse`)
You can directly interact with the headless Muse gateway inside your isolated network namespace:
You can directly interact with the headless Muse gateway inside your isolated network namespace using either `muse` or `box muse`:
```bash
# List all your active threads
# Using native muse wrapper (interactive prompt & account enforcement)
muse -a <account> status
muse -a <account> threads
muse -a <account> history --thread <thread_uuid> --limit 10
muse -a <account> send --thread <thread_uuid> "<message>"
# If invoked without -a/--account, it displays valid accounts and usage instructions:
muse
# Alternatively via box CLI:
box muse <self> threads
# Read message history in a thread
box muse <self> history --thread <thread_uuid> --limit 10
# Check unread messages
box muse <self> unread
# Start a new thread / session
box muse <self> session-start --title "<title>"
# Fast fire-and-forget message send
box muse <self> send --thread <thread_uuid> "<message>"
```