Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.227 Home All releases ←olderv2.1.226 v2.1.228newer→
Claude Code v2.1.227

/code-review can post its findings as a comment on a GitHub pull request

You'll notice
Useful4 Signal3
Code Review

Code review findings can be posted straight back to your GitHub pull request as a comment.

Feature flag
tengu_ultrareview_post_enabled Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.227: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.227. It isn't a statement about your account. What a flag value here can and cannot tell you

/code-review--post
What

After a review, Claude Code can now post the findings back to the pull request as a GitHub comment. It sets up an anthropic_cloud environment, registers a scheduled routine that is allowed only two GitHub tools (mcp__github__add_issue_comment and mcp__github__get_me), and runs it with the findings. Posting is controlled by tengu_ultrareview_post_enabled, which falls back to on; when it is off the reply is "Posting to the pull request is currently turned off".

Details
  • The routine's job config sets github_review_comment_only so it can only leave a review comment, and every other tool is on a disallowed list.
  • The routine's identifier is remembered in your settings under ultrareviewPostRoutines, along with a version; later runs re-verify it and refresh it rather than creating a new one.
  • New telemetry tengu_ultrareview_post records the outcome: fired, fire_failed, deadline (setup did not complete in time), or skipped_not_findings.
  • If the cloud environment cannot be set up, you get prose telling you to open claude.ai/code and rerun with --post.
Evidence

tengu_ultrareview_post

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.227 →