2.8 KiB
name, description
| name | description |
|---|---|
| ruflo-browser | Browser session lifecycle dispatcher -- ls/show/replay/export/fork/purge/doctor over RVF-backed session containers |
$ARGUMENTS Browser session management via RVF cognitive containers + AgentDB index. Parse the verb from $ARGUMENTS.
Usage: /ruflo-browser [args]
Verbs:
-
ls [--query ""] [--host ] [--verdict pass|fail|partial] List browser sessions. Backs onto AgentDB
browser-sessionsnamespace.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 ruvector@0.2.25 rvf status <session-id>.rvf npx -y ruvector@0.2.25 rvf segments <session-id>.rvfThen
Readthe trajectory.ndjson tail and the findings.md. -
replay
<session-id>[--url ] [--mutate ] Invoke thebrowser-replayskill on the named session. When thebrowser_session_replayMCP tool ships, this verb shells through to it. -
export
<session-id>[-o ] [--federate]npx -y ruvector@0.2.25 rvf export <session-id>.rvf -o <path>With
--federate, also push via theruflo-federationplugin. -
fork
<session-id>[--name ]npx -y ruvector@0.2.25 rvf derive <session-id>.rvf <new-name>.rvfLineage tracked. Cookies, selectors, templates inherited.
-
purge
<session-id>[--keep-manifest] Destroy the RVF container. Default keeps a redacted manifest inbrowser-sessionsso future searches still find the trace; pass--no-keep-manifestto wipe completely. -
doctor Run the structural health check:
bash plugins/ruflo-browser/scripts/smoke.shPlus dependency probes:
- Playwright runner reachable (
mcp__claude-flow__browser_openagainstabout:blank) - AgentDB controllers initialized (
mcp__claude-flow__agentdb_health) - AIDefence loaded (
mcp__claude-flow__aidefence_stats) - ruvector pinned to 0.2.25 (
npx -y ruvector@0.2.25 --version)
- Playwright runner reachable (
Notes:
- Verbs
replay,fork, and thebrowser_session_*MCP tools are part of the v0.2.0 architecture but their MCP-tool implementation is pending (see ADR-0001 Verification §4 spike). - Until the lifecycle MCP tools ship,
replayandforkoperate at the RVF-container level; the actual browser drive is invoked through thebrowser-replayskill, not a single MCP call. - For interactive primitive operations (open/click/fill/eval) use the existing
browser-record/browser-test/browser-extractskills, not this dispatcher.