The same files
The Agent edits the project you have open, through its own tools. When it changes a file while you have unsaved text, Rho tells you whose version is on screen before anything is written.
Scientific workbench for R
An Agent works in your project.You see everything it did.
Rho puts a person and an external Agent on the same R project: the same files, the same runs, the same results — and one record of how each result was reached. The Agent keeps its own tools and permissions. Rho is the workspace they share.
npm install -g @rho-workspace/rho
rho --root /absolute/projects --state-dir /absolute/service-state
The same runs
Commands run in your project and their output is kept with the exit code and duration. A failed run stays visible as a failure; nothing is retried behind your back under a new identity.
A record of what happened
Every question, file, run and decision is joined in one graph. It is the same record the Agent reads when you ask a follow-up, and the same record you export.
Understand a result before you accept it
The answer, with what produced it
An answer is not a paragraph. Rho shows the question, the result files, the method, the commands that ran, and the report they produced — each one openable at the version it was captured at.
What changed after a simulated projectConditional compositions
The record is the interface
What the Agent did, folded by what it means
Questions, findings, choices, files and runs become one graph. Meaning and process are separated so you can read the reasoning or the sequence, and failures stay in the count instead of disappearing from it.
One workspace, chosen by you
Arrange the views, keep the ownership
Code, tables, figures, notebooks and conversations are separate components with their own owners. Rho arranges them in tabs and splits without taking over their content, so closing a view releases the view, not the work.
What is actually established
Claims come with the evidence beside them
Rho is a research project, and its documentation records failures and open questions with the same weight as passes. Current work varies by area, so the Status page is the single summary.
Checked
- Each release of @rho-workspace/rho is published from the exact candidate the CI suite tested, with provenance.
- The suite runs on macOS, Linux and Windows; the packed candidate is installed offline on each, and on Linux also with Node 24 and 26.
- The example project ships with the application and is copied once into your projects folder.
Limited
- macOS x64 starts only under Rosetta.
- Releases since 0.5.2 carry platform installs and package checks; the full 0.5.1 acceptance was not repeated on them.
- Row questions on an ordinary CSV still need a declared key column or a row position.
Not established
- Use by an independent researcher is unobserved. No usability claim is made.
- Scientific novelty and human benefit are not established by the existing checks.
- The desktop client is deferred; this delivery is npm plus a local WebUI.
Four repositories, separate owners
Nothing here is one monolith
RhoApplication assembly, windows, layout and the shared interaction. This site.Rho-coreOptional managed execution, retained execution facts, the resident Host.Rho-pluginsDocuments, files, tables, charts, media, kernel, skills and the Agent adapter.Rho-paperThe research proposal, its claims and the related work it relies on.
Start
Node 22, 24 or 26, R, and one of your own Agent clients
Rho is a local service with a WebUI, on Node 22.22 or later, below 27. R and any project packages are yours to install, and so are the Agent clients: conversations drive the Claude Code or Codex you already have. DeepSeek Harness connects as an external Agent through the dsh-rho plugin. The service, documents and readers work without R.
Published to npm
@rho-workspace/rho