plugins/ruflo-browser/commands/ruflo-browser.md
$ARGUMENTS Browser session management via RVF cognitive containers + AgentDB index. Parse the verb from $ARGUMENTS.
Usage: /ruflo-browser <verb> [args]
Verbs:
ls [--query "<text>"] [--host <host>] [--verdict pass|fail|partial]
List browser sessions. Backs onto AgentDB browser-sessions namespace.
npx -y @claude-flow/cli@latest memory list --namespace browser-sessions
# or with semantic filter:
npx -y @claude-flow/cli@latest memory search --namespace browser-sessions --query "QUERY"
For active (live) sessions, also call mcp__claude-flow__browser_session-list.
show <session-id>
Print the session manifest + last 20 trajectory entries + verdict.
npx -y [email protected] rvf status <session-id>.rvf
npx -y [email protected] rvf segments <session-id>.rvf
Then Read the trajectory.ndjson tail and the findings.md.
replay <session-id> [--url <new-url>] [--mutate <json>]
Invoke the browser-replay skill on the named session.
When the browser_session_replay MCP tool ships, this verb shells through to it.
export <session-id> [-o <path>] [--federate]
npx -y [email protected] rvf export <session-id>.rvf -o <path>
With --federate, also push via the ruflo-federation plugin.
fork <session-id> [--name <new-name>]
npx -y [email protected] rvf derive <session-id>.rvf <new-name>.rvf
Lineage tracked. Cookies, selectors, templates inherited.
purge <session-id> [--keep-manifest]
Destroy the RVF container. Default keeps a redacted manifest in browser-sessions so future searches still find the trace; pass --no-keep-manifest to wipe completely.
doctor Run the structural health check:
bash plugins/ruflo-browser/scripts/smoke.sh
Plus dependency probes:
mcp__claude-flow__browser_open against about:blank)mcp__claude-flow__agentdb_health)mcp__claude-flow__aidefence_stats)npx -y [email protected] --version)Notes:
replay, fork, and the browser_session_* MCP tools are part of the v0.2.0 architecture but their MCP-tool implementation is pending (see ADR-0001 Verification §4 spike).replay and fork operate at the RVF-container level; the actual browser drive is invoked through the browser-replay skill, not a single MCP call.browser-record / browser-test / browser-extract skills, not this dispatcher.