rimio-ai/rimz

██╔══██╗██║████╗ ████║ ╚══███╔╝
██████╔╝██║██╔████╔██║ ███╔╝
██╔══██╗██║██║╚██╔╝██║ ███╔╝
██║ ██║██║██║ ╚═╝ ██║ ███████╗
╚═╝ ╚═╝╚═╝╚═╝ ╚═╝ ╚══════╝
The control room for your coding agents
agent fleet · harness dashboard · loops · local & remote · tmux & zellij · token insight
Status ·
What it does ·
Get started ·
Everyday moves ·
Configuration ·
Agents ·
How it works ·
Docs ·
llms.txt
AI agents / LLMs: fetch the live index / full docs blob .
---
RimZ puts your coding agents in one Zellij or tmux room and routes your attention to whichever one needs you. Every agent gets a live card in the sidebar (state, task, context health, live cost), so one human follows tens of agents at a glance, and one click lands in the pane that is waiting.
The sidebar triages the fleet on the left; agents work in their own panes.
RimZ is one lightweight binary inside the Zellij or tmux you already run. Your keybinds stay, the agent CLIs run stock, and the official web, desktop, and mobile apps keep working untouched.
That small footprint carries the primitives **harness engineering** and **loop engineering** build on: the sidebar for observability, one command grammar for every supported agent, durable messages that steer and queue, supervised runs with exit codes for scripts and CI, teams and subagents that split work across models, wakeups that put the fleet on a clock or on an event, and dollar budgets that bound what it spends. The harness itself (guardrails, policies, self-running loops) is yours to build on top.
Project status
RimZ is **beta software**. The basic features work smoothly for daily use, and the surface is moving fast: commands, flags, config keys, and output formats can change between releases, and you will meet the occasional rough edge. The changelog records what moved in each release.
It is also heavily used, on itself. RimZ is built with RimZ. Driven through teams and loops, most of the routine engineering here (features, bug fixes, CI repair) already flows through the harness with little hand-holding.
Read that as: ready for personal, daily use today; for production workflows that need a stable interface, wait for the 1.0 release.
What it does
Realtime harness dashboard, with rich information at a glance
See the fleet
- Each agent card shows working state and task, model and effort, context health and compactions, live token stats and dollar cost, and the subagent tree.
- The cockpit line (? 2 ! 1 …) reads the whole fleet in one glance, the column below it arrives already triaged, and one click drops you into the pane that is waiting.
- Spending and token insight covers today, the week, and the month, with plan and 5h/7d budget bars for providers that expose those account surfaces, so one look tells you where the week is going.
- A pet, an animated sprite on the provider dashboard, keeps you company: it runs while the agents run and waves when one waits.
Run agents together
- One layout spec opens agents side by side in an isolated Git worktree: claude,codex starts Claude planning beside Codex reviewing, and vim,codex+term puts your editor, an agent, and a shell in one tab.
- A team pairs models by role, such as a Fable planner with an Astra coder, and launches as one unit, each role on the model best at its job (reasoning depth, instruction following, speed, price). A mixed team catches what a single model lets through.
- A staged team keeps its progress on a board in the worktree and hands a stage to the next role with one command, so a member that crashed or compacted picks the run back up.
- Every agent answers to a handle (@codex, @planner). Messages are durable, park at the turn boundary or steer the live turn, and carry agent-to-agent talk inside channels the same way they carry yours.
- An agent launches supervised children with rimz subagents, each a full agent in its own pane with a nested sidebar row, a durable transcript, and its spend credited to the parent. Children mix providers freely.