Redrob OS is an agentic desktop operating system for PCs, laptops and the Raspberry Pi 5. A resident agent works for you inside a sandbox, connected to the channels you already use (Slack, Discord, Google), while the desktop itself stays out of your way: it updates itself in the background and rolls back on its own if an update does not boot.
한국어: README.ko.md
Download the installer ISO (older versions on Releases), write it to a USB stick, boot it and follow the guided installer (disk selection, dual boot with Windows, disk encryption, your user account). Raspberry Pi 5 uses a raw disk image instead. Full steps: docs/install.md.
The desktop is redrob-comp, Redrob's own Wayland compositor and shell (Smithay,
compositor/redrob-comp/), drawn with the Redrob design system. Pick a Mac layout (menu
bar + dock) or a Windows layout (taskbar + start button), dark or light, in Redrob
Settings (⌘, / Win+I), which also covers shortcuts, input, sound and display
(resolution, scale). App search, window switcher, overview, lock screen, screenshots and
notifications are built in. Apps are current GTK4 apps (Ptyxis, Files, Text Editor, ...);
the Redrob Launcher installs the Redrob apps (Browser, Office, Canvas, Code) on first
login. Korean input is Fcitx 5 (right Alt, Shift+Space or Ctrl+Space; Hanja on right Ctrl).
Tour: docs/desktop.md.
The whole OS is one signed image. The device checks for a new image once a day, stages it in the background and switches to it at the next reboot. A boot health check runs after every update; if it fails, the device boots the previous image by itself. You can also pick the previous version from the boot menu at any time. Details: docs/maintenance.md and docs/decisions/0001-bootc-base.md.
The agent runs as a system service and executes tasks (including coding) in a sandbox that cannot see your credentials or the rest of the machine. First boot shows a QR code to pair your phone; after that you talk to it over your channels. How it is wired into the image: docs/agent-on-bootc.md. Reaching the device from a phone, on the same Wi‑Fi or through a relay you run: docs/remote-access.md.
| Path | Role |
|---|---|
image/ |
The OS image: Containerfile, base pin (base.env), artifact pins (pins.env), file overlays (files/, agent/, branding/), build scripts and installer config (installer/) |
agent/ |
Resident agent runtime: channels, cron, secrets, tool sandbox client (vendored, see below) |
tools/ |
Small on-device helpers (redrob-pairing: first-boot pairing QR) |
modules/ |
Optional on-device services: credential-broker, usb-broker, local-inference |
docs/ |
Install and desktop guides, requirements, design notes, decisions (ADRs), maintenance |
.github/ |
CI: build, sign and publish the image; build the installer on release tags; dependency bumps |
Redrob Code (the coding tool that runs inside the sandbox) lives in its own repository, redrob-labs/redrob-code.
Two upstreams, pinned in one place each and recorded in UPSTREAM.md and
upstream-base.json:
| What | How it is tracked |
|---|---|
agent/ |
git subtree with full history from zeroclaw-labs/zeroclaw; synced tag by tag |
| Base OS image | An OCI image reference in image/base.env: Fedora Atomic base-atomic (quay.io/fedora-ostree-desktops/base-atomic), which supplies the kernel, systemd and bootc (no desktop: that is redrob-comp); the tag is bumped by Renovate pull requests |
Everything else the image contains comes from the base distribution's own package
repositories and is listed in NOTICE.
Apache-2.0. See LICENSE and NOTICE. Third-party notices and trademark statements
are in NOTICE.