// changelog
v1.22.0
remote pr writes a JSON report while it posts and can cap the verdict at comment; config set reads secrets from stdin.
Released November 14, 2026
Added
remote pr --jsonwrites a machine-readable report in posting mode. The run still posts its inline comments and submits the verdict, and also writes one JSON v1 document to stdout (or to--output): the full findings list after suppression, ametablock with token usage, cost and latency summed over every provider call of the run, and a new optionalremoteblock with the status, PR and head commit, the verdict before and after the ceiling, whether the run was full or incremental, the sync counters and a list of stable warning codes.schemastays1, and every other command’s document is unchanged. Once a provider call has returned, every way the run ends writes the document, so the spend is never invisible. Exit codes are unchanged.remote pr --max-verdict <approve|comment>. Withcomment, the review never submits anapprove: a PR with no findings, or onlyinfofindings, gets acommentreview instead. Inline comments, the reviewed marker and--request-changes-onare unaffected. The default,approve, keeps today’s behaviour.config set <key> -reads the value from stdin. A secret such as an API key no longer has to appear in the process arguments, wherepsshows it:printf '%s' "$KEY" | commitbrief config set providers.anthropic.api_key -. One trailing newline is removed, the value is capped at 64 KiB, an empty stdin is rejected, and a terminal on stdin is refused with a pointer tocommitbrief setup. A validation error never echoes a value read from stdin. The new--literalflag stores a value of-as-is.
Changed
config set <key> -now reads stdin instead of storing a literal-. If a script relied on the old behaviour, add--literal.remote pr <ID> --jsonno longer stops at a usage error. It now posts comments, submits a verdict and also writes the report. Use--no-postfor a local preview.- The
remote prfooter counts a superseded retry attempt. When the PR head moved during the review, tokens and cost in the footer are summed over both attempts and matchmeta.usageandmeta.cost_usdof the same run. remote prnever runsreview.sandbox_command. It never did; the guarantee is now enforced on both the posting and--no-postpaths and covered by a regression test.