Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.229 ·

A built-in /commit command, off unless a server gate turns it on

A built-in commit command with a strict git workflow exists but is off unless a server enables it.

Nothing to try yet Notable In Development
JSON All of v2.1.229
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Slash CommandsArea: what it touches
In DevelopmentKind: in v2.1.229,
What probably matters to youSection of the release

A commit slash command with fixed git rules and limited tool access is compiled in with its gate set false.

What

A command named "commit" is registered that gathers git status, the diff against HEAD, the branch and the last 10 commits, then follows a fixed workflow: never amend after a failed pre-commit hook, never use --no-verify, prefer naming files over git add -A, and never push unless asked. Its tool access is limited to git add, status and commit. It appears only when the tengu_cinder_relay gate resolves true; the value compiled into the build is false, so whether it shows up is decided by server config.

Details
  • It is separate from the existing commit-push-PR flow.
Evidence

Create a git commit. Use whenever you are about to create a commit, tengu_cinder_relay

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

Read from
Names in the bundle/commit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged /commit-push-pr so git/gh commands with dangerous flags (--force, --amend, --no-verify, etc.) are no longer auto-approved

See this entry in the whole of v2.1.229 →

Feedback