Answers to a pairing request now go to the target machine's operator agent, which approves or denies on clear intent and asks back when it isn't sure.
Answers to a pairing request now reach the target's kernel operator. When the target has an operator that can receive them, typed words and Approve or Deny choices in the TUI, Steering or Slack go to that agent as replies, and receiving one neither grants nor denies access. The operator acts on clear intent with rig host approve <code> or rig host deny <code> and asks back when the answer is unclear. Both commands also work from a plain terminal on the target, using its operator bearer (OPENRIG_AUTH_BEARER_TOKEN, or --bearer <token>). An Approve click on a request the operator owns waits for the operator to act; a stopped operator keeps the request, and the answer waits in its queue.
Checked on this package: real Slack with a real operator agent in one run (a button or a typed yes approved, a no denied, and a qualified reply got a clarifying question before the refusal denied it); the real TUI without a model (answer credentials, typed answers asked again with no operator, plain-terminal approve and deny, and expiry); and 29 of 29 contained cases with synthetic credentials. Not run: an agent reading answers given in the TUI, Slack thread replies beyond the tested path, and Steering in a browser.
- Pull request
- #2900
- Release
- OpenRig 0.7.11 release notes