openrig-herdr

1# openrig-herdr
2 
3OpenRig decides **which** agents make up a view (a rig, a pod, a mission, a slice, or a saved
4group); **herdr** renders the pixels. A view opens as live, interactive terminal tiles — each tile
5is a nested `tmux attach` to a daemon-owned agent session, so you get the real session, not a
6snapshot. OpenRig owns the semantics; herdr owns the surface. You drive it entirely through the
7`rig terminal` CLI, which rides the installed herdr binary at arm's length — never link, embed, or
8plugin it.
9 
10## The whole surface — three verbs
11 
12```bash
13rig terminal open <view> [--provider herdr|cmux|rex] [--json]   # herdr is the default provider
14rig terminal open <view> --provider herdr-app                    # in the herdr-app window this runs in; plain open inside herdr-app does the same when the window answers (--window always asks for a new desktop window; the open installs OpenRig's mods there)
15rig terminal views [--json]                                     # list openable views (saved + derived)
16rig terminal status [--provider] [--json]                       # provider liveness / health
17```
18 
19Inside Rex, `rig terminal open <view> --window` opens the view as a new Rex session instead, on the same Rex
20server as your terminal, and asks the Rex app to show it. `--provider rex` opens it there from anywhere.
21 
22`<view>` resolves, in order, to one of:
23- a **rig name** — every live agent in that rig, auto-laid-out;
24…