Sessions
Agent sessions on OMP
All session and task execution goes through OMP. Each chat and auxiliary request activates orchestrate, workflowz and ultrathink with maximum thinking. Native transcripts resume after a restart.
Windows desktop app
ROX for Windows is a desktop workspace for agent sessions, connected sources, documents, skills and automations. Sessions, tasks and auxiliary agent calls run through OMP. Your Markdown vault stays on the PC in front of you.
01 — Workspace
ROX is built as a calm desktop command center: sessions, a knowledge vault, tasks, and a browser panel share one workspace instead of scattering across separate tools.
Sessions
All session and task execution goes through OMP. Each chat and auxiliary request activates orchestrate, workflowz and ultrathink with maximum thinking. Native transcripts resume after a restart.
Branches
A branch forks at the selected answer in a private copy of the parent transcript. The parent history stays intact. A reset marker keeps cleared or undone messages from returning.
OpenUI
An assistant answer may carry one openui block. ROX renders it locally. No cloud gateway is involved, and the surrounding prose still stands on its own.
Tasks
The task surface keeps today, upcoming work, projects and calendar context beside the session that produced them, so a plan does not leave the workspace.
Browser
Read a page in the same workspace as the session. The browser is a panel in the desktop app, not a separate research tab you have to reconstruct later.
Map
The session map is a pipeline trace and draft surface. It stays separate from document editing, so a run and a note never share the same controls.
02 — Knowledge
Local knowledge is a first-class surface. Notes are Markdown you can write, link, outline and comment on. Creating a note does not depend on an optional external kernel being online.
ROX keeps its files in a .rox folder inside your user profile, for example C:\Users\You\.rox. Set ROX_CONFIG_DIR when you want a separate profile. Credentials stay in credentials.enc.
config.json
credentials.enc
preferences.json
context/
workspaces/
<workspace>/
sources/
skills/
sessions/
03 — Skills
The offline catalog includes Superpowers, Impeccable, Obsidian, Matt Pocock, Vercel, Compound Engineering, gstack, gbrain, Telegram, Jev, Exa, acpx and oh-my-agent. A listed skill does not by itself configure an external service, credential, browser or application.
Documents
Office documents use a licensed document implementation. Figma and Groma integrations use explicitly identified ROX adapters rather than an unnamed upstream copy.
Toolchain
Managed acpx is pinned to 0.19.4, with verified package integrity and production dependency locks. Desktop builds record checksums, the source commit and signing status in the release manifest.
04 — Download
The official build on rox-one.org is the 64-bit Windows installer, Rox-x64.exe. macOS and Linux downloads are not offered here.
Windows
64-bit Windows installer.
Rox-x64.exe
05 — Questions
ROX is a desktop workspace for agent sessions, connected sources, documents, skills and automations. The execution engine for sessions, tasks and auxiliary agent calls is OMP, short for oh-my-pi.
Download Rox-x64.exe, the official 64-bit Windows installer, from rox-one.org.
Not right now. This site offers the Windows 64-bit installer only.
On Windows, configuration and workspace data live in a .rox folder in your user profile. Credentials are kept in credentials.enc. An older configuration is imported by copying, and the original files are preserved.
OMP is the agent runtime ROX uses for every session and task. Older backend selections migrate to a configured OMP connection. After a process restart, native transcripts are resumed before a new prompt is sent.
No. ROX is a separate project derived from Craft Agents and published at github.com/rox-one/rox-one. The source is Apache License 2.0. Craft and Craft Agents are trademarks of Craft Docs Ltd. This site does not imply endorsement by Craft Docs Ltd.