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 (oh-my-pi).
Download installers from ROX GitHub Releases:
| Platform | Artifact |
|---|---|
| macOS Apple Silicon | Rox-arm64.dmg or Rox-arm64.zip |
| Windows x64 | Rox-x64.exe |
The release manifest records artifact checksums, source commit and signing status. Current release automation targets these two platforms; Intel macOS and Linux desktop installers are not part of this release matrix.
Auto-update metadata is published with GitHub releases. Unsigned macOS builds can check for updates, but automatic installation is suppressed until a properly signed release is available.
- All session and task execution goes through OMP. Legacy backend selections migrate to a configured OMP connection.
- Each chat and auxiliary request automatically activates
orchestrate workflowz ultrathinkwith maximum thinking. - Native transcripts are resumed before a new prompt is sent after process restart.
- Branches fork at the selected answer in a private copy of the parent transcript. Parent history is preserved.
- Older sessions without native transcripts can reconstruct their stored ROX history. Missing provider metadata is explicitly marked as unavailable; malformed transcripts fail instead of silently dropping records.
- A persistent reset marker prevents cleared or undone messages from reappearing after restart.
- Assistant answers may carry one
openuiblock that ROX renders locally as charts, tables, forms or cards. No cloud gateway is involved, and the surrounding prose stands alone.
Implementation and wire contracts: OMP RPC notes, runtime specification, native fork/resume evidence.
The offline catalog contains 330 skills in 34 packs. It includes Superpowers, Impeccable, Obsidian, Matt Pocock, Vercel, Compound Engineering, gstack, gbrain, Telegram, Jev, Exa, acpx, oh-my-agent and the other requested skill integrations.
- Requested skill mapping: upstream sources, alternatives, licenses and prerequisites.
- Pinned pack manifest.
- Native Rox CLI discovery evidence.
Figma and Groma integrations use explicitly identified ROX adapters. DOCX/XLSX/PPTX use a licensed document implementation rather than copying restricted upstream packages. A discoverable skill does not by itself configure an external service, credential, browser or application.
Managed acpx CLI is pinned to 0.19.4, with verified package integrity and production dependency locks.
The configuration directory is the legacy hidden home ~/.rox by default. With the storage.visible-root.v1 flag on it is the visible ~/rox, and ~/.rox stays behind as a compatibility symlink (manual path: craft-cli migrate-config). Set ROX_CONFIG_DIR to use an isolated profile.
<config dir>/
config.json
credentials.enc
preferences.json
context/
workspaces/
<workspace>/
config.json
sources/
skills/
sessions/
<session>/omp/
Legacy configuration is imported by copying; original files are preserved. Deprecated identifiers remain only where compatibility and source attribution require them. New links use rox://.
Each OMP process receives the ROX system context, session tools and connected source tools. The private runtime profile provides the pinned skill tier and mandatory execution policy. Working-directory instruction files and workspace context are handled by the existing context pipeline.
Use the pinned Bun 1.4.2 toolchain.
git clone https://github.com/rox-one/rox-one.git
cd rox-one
bun install --frozen-lockfile
bun run electron:devbun run typecheck:all
bun run validate:ci
bun run electron:buildPackages use the @rox/* workspace namespace. Test preloads isolate configuration from the user's live profile. See AGENTS.md for repository conventions and the Russian documentation hub for operational guides.
Desktop builds and checksum verification are defined in Desktop Release Build. Publication uses Publish Desktop Release.
ROX is derived from the original upstream repository. Original copyright notices, licenses and third-party attribution are retained in LICENSE, NOTICE and third-party notices. Bundled skill packs carry their own source and license records.
See CONTRIBUTING.md and SECURITY.md.