ruflo-ruos

Reviewed at commit 13af5f1

Sends data to ruOS fleet MCP and jobs API (ruos.cognitum.one)

Run ruflo swarm agents on your own ruOS cloud desktops via the tenant-authenticated fleet MCP or per-tenant SSH; optional and removable (ADR-405)

Made by
ruvnet
What we checked

Shows how many ruflo agents run on your ruOS cloud desktops in ruflo's status line, by re-reading a small file in your project every 15 seconds. Its commands and skill have Claude run a bundled Node script that sends task prompts to your ruOS desktops through ruos.cognitum.one (or SSH), runs claude -p there, and saves the output and run logs under .claude-flow/ruos in your project.

Review details

Static review of the source at the pinned commit; not run. Delta review of the changes since 828a8d7; the rest carries over from the review at that commit. The only change is a repository field in plugin.json; no code or prompt changed. The hook module registers session.start and prompt.submit; both only re-read <project>/.claude-flow/ruos/hosts.json with $.session.root and $.fs.read and pass a sanitised text of at most 48 characters to $.ruflo.segment (wrapped in try/catch, so nothing is drawn without the ruflo mod); $.clock.every refreshes it every 15 s. The prompt hook does not read or change the prompt, and the hook makes no network calls. The commands (hosts, run, view, deploy), the ruos-host-operator agent and the ruos-host-run skill drive scripts/cli.mjs, which reads RUOS_MCP_URL/RUOS_MCP_TOKEN or ~/.config/ruos/credentials.json (its own ruOS token) and POSTs JSON-RPC tools/call requests to the fleet MCP (default https://ruos.cognitum.one/mcp, https enforced except localhost, port 17870 refused) and the REST jobs API on the same origin (or RUOS_API_URL). Task prompts are base64-staged on the remote desktop and run there with claude -p (no permission bypass flags); remote shell strings come only from a builder with strict allow-list validation, and desktop_delete/secret_delete are refused in code. The optional SSH transport spawns ssh with a fixed argv (no shell, StrictHostKeyChecking=accept-new) to <fly-id>.vm.<app>.internal:2222 using the key path in RUOS_SSH_KEY. Starting a desktop needs --start; stopping a run or desktop needs --confirm. It writes events.jsonl, audit.jsonl, hosts.json and runs/<id>.log (full remote output, mode 0600) under .claude-flow/ruos in the project, and records agents through ruflo's callMCPTool when it can import it, resolving @claude-flow/cli from the plugin's own install location (or RUFLO_CLI_MCP_CLIENT) rather than the opened project's node_modules. The skill pre-approves Bash(node *) plus the ruos MCP tools desktop_status, desktop_exec, desktop_keepawake, desktop_start and llm_route_get (no unpinned packages); commands suggest npx ruflo agent list/status, which Claude still asks about. deploy-info only reads git state on the desktop and never pushes. scripts/bench.mjs and scripts/smoke.sh are not loaded by the plugin and were not reviewed.

What it uses
  • Reads your prompts: no
  • Sees tool calls: no
  • Blocks or changes tool calls: no
  • Reads or writes files: yes
  • Runs programs on your machine: yes
  • Calls the model (uses tokens): no
  • Sends data over the network: yes
  • Stores data: yes
  • Shows something on screen: yes
Hooked events
Made this mod? Add a badge to your README

modsforClaude badge for ruflo-ruos

Paste this into your README. The badge says reviewed once the current version has been reviewed, and links readers to this page.

[![Listed on modsforClaude](https://modsforclaude.com/badge/ruflo-ruos.svg)](https://modsforclaude.com/mods/ruflo-ruos/)

← All mods