opschain recommendations
packs:agent-governance
Inspect agent recommendations — the ADVISE output of an agent, as the
approver sees it. A recommendation is one card per (agent, subject node
path, incident): the platform de-duplicates a second proposal for the same
incident into the open card (duplicate_of), and the card lists every
proposal linked to it with its lane (stable, shadow, canary or an
operator label), so a shadow-lane build's proposal sits beside the stable
lane's for comparison and never becomes a second change. Every card carries
the correlation id of the incident that triggered it — the handle into
opschain chains show. recommendation is accepted as an alias.
| Subcommand | Does |
|---|---|
opschain recommendations list | A project's recommendations as a table: status, agent, lane, node, title, correlation id and the duplicate linkage — opschain docs cli/recommendations-list |
opschain recommendations show | One card with its lane, chain, disposition and every linked provenance — opschain docs cli/recommendations-show |
Accepting or dismissing a card stays where the approver works: the
recommendations API (POST …/recommendations/{id}/accept|dismiss) and the
GUI. Both verbs need a server target (--server <url> or the active
context) and the packs:agent-governance entitlement on the server.
See also
opschain docs agent-releases— lanes, the shadow lane and the rollover.opschain docs agent-plane— the recommendations lifecycle and its events (info:recommendation:filed|duplicate|accepted|…).opschain docs cli/chains-show— following a card's correlation id.