chimera approve
Answer a decision the agent is waiting on, from anywhere. Without a terminal the approval gate collapsed to a refusal: `ask` degraded to `deny`, so every REVIEW verdict on the VPS, in a container or under cron was a no, and the mandate that says "confirm before billing, before a destructive migration, before touching RLS" had nothing to confirm with. The question is written down and sent to wherever this deployment delivers; this is how it gets answered. Silence is still a refusal — a question times out. That is deliberate: a gate that reads silence as consent produces a record of an approval nobody gave.
Arguments
REQUEST_IDstrThe id from the message. Omit to list what is waiting.
Options
--yes, -ybooleanApprove it.
--no, -nbooleanRefuse it.