openrig-herdr

OpenRig decides which agents make up a view (a rig, a pod, a mission, a slice, or a saved group); herdr renders the pixels. A view opens as live, interactive terminal tiles, each tile is a nested tmux attach to a daemon-owned agent session, so you get the real session, not a snapshot. OpenRig owns the semantics; herdr owns the surface. You drive it entirely through the rig terminal CLI, which rides the installed herdr binary at arm's length, never link, embed, or plugin it.

The whole surface, three verbs

rig terminal open <view> [--provider herdr|cmux|rex] [--json]   # herdr is the default provider
rig terminal views [--json]                                     # list openable views (saved + derived)
rig terminal status [--provider] [--json]                       # provider liveness / health

Inside Rex, rig terminal open <view> --window opens the view as a new Rex session instead, on the same Rex server as your terminal, and asks the Rex app to show it. --provider rex opens it there from anywhere.

<view> resolves, in order, to one of:

• a rig name, every live agent in that rig, auto-laid-out;
• pod:<rig>/<podNamespace>, every live agent in one pod of a rig (the rig's inventory filtered by pod);
• mission:<id>, the agents working that mission (derived live from topology);
• slice:<id>, the agents working that slice (derived live);
• a saved-view name, a user-defined group (see Saved views).

Compose a view from a sentence

An agent asked "open all my rigs plus a mission as views" runs one open per target:

rig terminal open acme-web                     # a whole rig, live agents as tiles
rig terminal open mission:site-relaunch        # exactly the agents working the mission
rig terminal open slice:search-filters      # the agents working one slice

No hand-listing of seats: the mission/slice membership is derived from live topology at open time.