Claude Code v2.1.267 · 9 Sep 2026
New workflow keyword-trigger setting tracked via a settings change-log abstraction
Settings toggles like verbose mode and a new keyword-trigger option now go through a unified change-log system
Use it now Notable
No documentation found New Features
Copy link
Copy markdown
JSON
All of v2.1.267
Use it now Tier: how much it should matter to you
3 Useful: my rating, 1 to 5
3 Signal: worth watching, 1 to 5
Settings Area: what it touches
New Features Kind: in v2.1.267, 09 Sep 26
What probably matters to you Section of the release
Unclear The finding doesn't say what ultracodeKeywordTrigger does or how a user would use it.
What
Several settings toggles, including verbose , permissionMode , Fast mode, Default view, and a new ultracodeKeywordTrigger setting, are now updated through one shared change-log object with record, toggle, and clear methods, instead of each being updated with its own separate code.
Why
This is mainly an internal cleanup that makes settings changes more consistent and easier to track, and it surfaces a new ultracodeKeywordTrigger setting related to triggering workflows by keyword.
How sure we are
Something disagrees Something we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt The finding doesn't say what `ultracodeKeywordTrigger` does or how a user would use it.
See this entry in the whole of v2.1.267 →
9 Sep 2026 · 270 entries, this one is #36.
Use it now38 You'll notice86 Nothing to try yet21 Under the hood125
Open the release →
Names in this entry
setting verbose Show full tool output instead of truncated summaries; viewMode takes precedence when both are set
setting permissionMode SDK callers can let the CLI pick the permission mode from settings instead of forcing "default".
setting ultracodeKeywordTrigger Settings toggles like verbose mode and a new keyword-trigger option now go through a unified change-log system
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 35 of 270
New pointer-event handling for full-screen terminal UI panes
Use it now Plugin UI
In v2.1.267 What probably matters to you release-page order
Next → · 37 of 270
Turn events now include token usage data
Use it now Hooks