claude.nagdy.me

Changelog

What's been shipped and fixed.

v1.24.32 · Jul 23, 2026

Verify audit PRs #391 (advanced-features quiz) and #392 (commands): the /code-review background-subagent note (v2.1.218) and the --no-session-persistence flag, both confirmed against the official docs

Today's pass opened on two auto-generated audit PRs. Both claims were checked against the official Claude Code docs before anything was applied. (1) #392 (commands) — /code-review now runs as a background subagent so review work no longer fills the conversation; the Claude Code CHANGELOG's v2.1.218 entry states verbatim 'Changed /code-review to run as a background subagent, so review work no longer fills your conversation'. Added a v2.1.218 sentence to the commands module prose and to the /code-review quiz explanation. (2) #391 (advanced-features quiz) — the headless-mode Q4 decoy named the non-existent flag --no-conversation; the official CLI reference lists --no-session-persistence as the print-mode flag that disables session saving and has no --no-conversation, so the decoy option text was corrected. CodeRabbit and Codex both flagged that #391 left the matching explanation still saying --no-conversation, so this pass fixes the explanation too (the decoy now teaches the real flag), and applies the same --no-conversation → --no-session-persistence correction to the workflows quiz q1 decoy, which carried the identical non-existent flag. Both PRs are closed in favour of this consolidated change; full EN + AR parity.

Fixed

commands: /code-review runs as a background subagent as of Claude Code v2.1.218 — EN + AR

The commands module and the /code-review quiz explanation described the command without noting that, as of v2.1.218, it runs as a background subagent so review work no longer fills the conversation. Per the Claude Code CHANGELOG v2.1.218 ('Changed /code-review to run as a background subagent, so review work no longer fills your conversation'), added that behaviour to the commands module prose and the quiz explanation. Applied to the EN + AR module and quiz. Incorporates audit PR #392.

advanced-features + workflows quizzes: replace the non-existent --no-conversation flag with --no-session-persistence — EN + AR

The advanced-features headless-mode Q4 decoy and the workflows CI/CD Q1 decoy both named --no-conversation, a flag that does not exist. The official CLI reference lists --no-session-persistence as the print-mode (claude -p) flag that disables session saving and has no --no-conversation entry. Corrected both the decoy option text and its explanation in each quiz so the decoy teaches the real flag while remaining an incorrect answer (the CI/CD flag is still --permission-mode bypassPermissions). Incorporates audit PR #391 and resolves the CodeRabbit + Codex review notes that its explanation text was left stale.

Arabic

Arabic parity for every change in this pass

Every change was applied to the Arabic side alongside the English: the v2.1.218 /code-review background-subagent note (commands module + quiz) and the --no-conversation → --no-session-persistence correction (advanced-features and workflows quizzes, option text and explanation).

v1.24.31 · Jul 22, 2026

Verify 4 open audit PRs (#386–#389) against the official docs: incorporate the 2 supported fixes, reject the doc-contradicted claims

Today's pass opened with four auto-generated audit PRs (#386–#389). Each finding was checked against the official Claude Code docs and CHANGELOG, then split into supported fixes (folded into this one consolidated change) and doc-contradicted claims (rejected). Supported and incorporated: (1) getting-started (#386) — the PowerShell tool is now enabled by default on Windows for Bedrock, Vertex, and Foundry users (opt out with CLAUDE_CODE_USE_POWERSHELL_TOOL=0), and rolls out progressively for other providers; the CHANGELOG states verbatim 'The PowerShell tool is now enabled by default on Windows for Bedrock, Vertex, and Foundry users. Opt out with CLAUDE_CODE_USE_POWERSHELL_TOOL=0'. (2) workflows (#389, partial) — /ultrareview's version attribution is corrected to 'added in v2.1.111'; the CHANGELOG's introducing entry is under v2.1.111 ('Added /ultrareview for running comprehensive code review in the cloud…'), with no v2.1.86 or v2.1.112 addition, so the old 'new in v2.1.86, highlighted in v2.1.112' line was wrong. Rejected: #387 (skills) re-proposed the already-rejected skill-listing budget 1% → 2% change — the /en/skills docs state verbatim 'The budget scales at 1% of the model's context window' (0.02 = 2% is given there only as the example for raising it) — and tried to trim the skill `effort` values to low/medium/high, but /en/model-config lists `low`, `medium`, `high`, `xhigh`, `max` for Sonnet 5 / Opus 4.8 / Opus 4.7 and the skills frontmatter reference lists the same five, so both findings were rejected and the original 1% / five-value content stands. #388 (slash-commands) tried to drop `max` from /effort, but /en/model-config confirms `max` is a valid effort level (the deepest, session-only), so it was rejected. #389's second finding claimed `disableWorkflows` / `CLAUDE_CODE_DISABLE_WORKFLOWS=1` don't exist and should become CLAUDE_CODE_DISABLE_BUNDLED_SKILLS, but the workflows docs 'Turn workflows off' section lists both `"disableWorkflows": true` in settings and `CLAUDE_CODE_DISABLE_WORKFLOWS=1` verbatim, so the original workflows-disable wording and the reference cheatsheet entry were kept. All four PRs are closed in favour of this consolidated change; full EN + AR parity.

Fixed

PowerShell tool is enabled by default on Windows for Bedrock/Vertex/Foundry — getting-started, advanced-features, terminal (EN + AR)

The Windows setup guidance said the PowerShell tool 'is rolling out progressively' and led with CLAUDE_CODE_USE_POWERSHELL_TOOL=1 to opt in. Per the Claude Code CHANGELOG, the tool is now enabled by default on Windows for Bedrock, Vertex, and Foundry users — opt out with CLAUDE_CODE_USE_POWERSHELL_TOOL=0 — and only rolls out progressively for other providers. Rewrote the wording to lead with the default-on behavior in the getting-started module and, for consistency across the site, in the advanced-features module and the advanced-features terminal-steps description as well. Incorporates audit PR #386 and a Codex review note about the remaining stale references.

workflows: /ultrareview was added in Claude Code v2.1.111 — EN + AR

The workflows module attributed /ultrareview to 'new in v2.1.86, highlighted in v2.1.112'. The CHANGELOG's introducing entry ('Added /ultrareview for running comprehensive code review in the cloud…') is under v2.1.111, with no matching v2.1.86 or v2.1.112 addition. Corrected the attribution to 'added in v2.1.111', aligning the workflows module with the skills module's existing v2.1.111 reference. Incorporates the first finding of audit PR #389.

changelog: correct the stale v1.22.4 /ultrareview attribution to v2.1.111

The historical v1.22.4 changelog entry still attributed /ultrareview to v2.1.86, which contradicted this release's correction to v2.1.111. Updated that entry's version references (EN + AR) so the public changelog is internally consistent on the official v2.1.111 attribution. Addresses a CodeRabbit data-integrity review comment.

Content

Rejected audit PRs #387 (skills), #388 (slash-commands), and #389's second finding

#387 re-proposed the skill-listing budget 1% → 2% change (already rejected as #288/#290) — the /en/skills docs say 'The budget scales at 1% of the model's context window' — and tried to trim skill `effort` to low/medium/high, but /en/model-config and the skills frontmatter reference both list `low`, `medium`, `high`, `xhigh`, `max`; rejected, original kept. #388 tried to drop `max` from the /effort values, but /en/model-config confirms `max` is a valid (deepest, session-only) effort level; rejected. #389's second finding claimed `disableWorkflows` / `CLAUDE_CODE_DISABLE_WORKFLOWS=1` don't exist, but the workflows docs 'Turn workflows off' section documents both verbatim; rejected, and the original module wording plus the reference cheatsheet entry were kept. All of #386–#389 are closed in favour of this consolidated PR.

Arabic

Arabic parity for every change in this pass

Every change in this pass was applied to the Arabic side alongside the English: the PowerShell default-on wording (getting-started module, advanced-features module, and advanced-features terminal-steps), the /ultrareview v2.1.111 attribution (workflows module), and the corrected v1.22.4 changelog entry. No Arabic quiz, template, cheatsheet, or catalog content asserted the corrected facts, so no further Arabic parity fixes were needed.

v1.24.30 · Jul 21, 2026

project-setup: date the experimental plugin manifest fields — note that `monitors` was added in v2.1.105 (#384)

The project-setup module explains that the `monitors` and `themes` plugin-manifest fields are experimental and should be nested under `experimental: {}` in `plugin.json`. This adds the release that introduced background monitors so readers can tell when the field became available. Verified against the official plugins reference (code.claude.com/docs/en/plugins-reference, 'Experimental components': `themes` and `monitors` live under the `experimental` key, top-level still works, `claude plugin validate` warns, a future release will require `experimental.*`) and the Claude Code CHANGELOG (v2.1.105: 'Added background monitor support for plugins via a top-level `monitors` manifest key'; v2.1.129 introduced the `experimental` nesting guidance). Consolidates auto-generated audit PR #384, which is closed in favour of this change; full EN + AR parity.

Fixed

project-setup: note that plugin `monitors` support was added in Claude Code v2.1.105 — EN + AR

The guidance on experimental plugin-manifest fields (`monitors` and `themes` under `experimental: {}`) now dates the `monitors` field to its introducing release. Per the Claude Code CHANGELOG, background monitor support for plugins landed in v2.1.105; the `experimental` nesting requirement followed in v2.1.129. Applied to the EN + AR module. Incorporates audit PR #384.

v1.24.29 · Jul 20, 2026

Advisor Tool: replace the fabricated CLAUDE_CODE_ENABLE_EXPERIMENTAL_ADVISOR_TOOL env var with the real enablement paths (#382), and fix the Arabic 'disable' wording flagged in review

The advanced-features module claimed the Advisor Tool is enabled via a CLAUDE_CODE_ENABLE_EXPERIMENTAL_ADVISOR_TOOL environment variable. The official advisor docs (code.claude.com/docs/en/advisor) list no such variable: the advisor is enabled by setting a model via the /advisor command, the advisorModel setting, or the --advisor flag, and the ONLY advisor-related env var is CLAUDE_CODE_DISABLE_ADVISOR_TOOL, which turns the tool off. This consolidates auto-generated audit PR #382 (which corrected the EN + AR module and both quiz files) and folds in the review feedback on it: the Arabic content had translated CLAUDE_CODE_DISABLE_ADVISOR_TOOL as 'بينعّم' (softens) instead of 'بيعطّل' (disables) in the module and quiz, and carried a 'بيتتفعّل' typo in the quiz — both corrected. PR #382 is closed in favour of this consolidated change; full EN + AR parity across module + quiz.

Fixed

advanced-features: Advisor Tool is enabled via /advisor, advisorModel, or --advisor — not a fabricated env var — EN + AR

The module and both quiz files stated the Advisor Tool is enabled via CLAUDE_CODE_ENABLE_EXPERIMENTAL_ADVISOR_TOOL. Per the official advisor docs (code.claude.com/docs/en/advisor), no such env var exists — the advisor is enabled by setting a model through the /advisor command, the advisorModel setting, or the --advisor flag, and CLAUDE_CODE_DISABLE_ADVISOR_TOOL is the only advisor env var (it disables the tool). Corrected the claim across the EN + AR module and EN + AR quizzes. Incorporates audit PR #382.

advanced-features (AR): correct 'disable' wording and a typo in the advisor content

The Arabic module and quiz described CLAUDE_CODE_DISABLE_ADVISOR_TOOL as 'بينعّم الأداة' (softens the tool) rather than 'بيعطّل الأداة' (disables the tool), and the quiz carried a 'بيتتفعّل' → 'بتتفعّل' typo. Both fixed per review feedback on PR #382.

v1.24.28 · Jul 18, 2026

Verify 8 open audit PRs (#372–#379) against the official docs: incorporate the 6 supported fixes, reject the doc-contradicted ones, close the no-op

Today's pass opened with a pile-up of eight auto-generated audit PRs (#372–#379). Each was checked against the official Claude Code docs and split into supported fixes (folded into this one consolidated change) and doc-contradicted claims (rejected). Supported and incorporated: (1) subagents (#378) — built-in subagents CAN be name-overridden; the sub-agents docs (code.claude.com/docs/en/sub-agents) state verbatim 'A user or project subagent named Explore overrides the built-in and keeps its own model field', so the old 'always available and not part of the name-override system' line was wrong. (2) project-setup (#376) — the docs confirm `--add-dir` scans a `.claude/agents/` folder in the added tree and loads those subagents, while CLAUDE.md/rules still need `CLAUDE_CODE_ADDITIONAL_DIRECTORIES_CLAUDE_MD=1`. (3) workflows/routines (#379) — the routines docs (code.claude.com/docs/en/routines) state routines require 'Claude Code on the web enabled' in addition to a Pro/Max/Team/Enterprise plan. (4) plugins (#375, partial) — the plugins reference confirms the LSP `restartOnCrash`/`shutdownTimeout` fields (v2.1.205+, with the pre-v2.1.205 skip-at-startup behavior) and that a plugin's `settings.json` supports only `agent` and `subagentStatusLine`; the PR's unverified `--plugin-dir (v2.1.145+)` version tag was dropped (not in the docs). (5) memory (#374, partial) — kept the `/init` multi-phase expansion, the decline-import dialog note, and the quiz clarification that rules without `paths` load unconditionally (all doc-exact); dropped the PR's 'whichever is smaller' change (the memory docs say 'whichever comes first') and the misattributed '(behavior stable since ~v2.1.198)' tag (v2.1.198 is about symlink path matching, not the trigger behavior). Rejected: advanced-features (#372) flipped the ultracode↔workflow rename direction, which both contradicts the current keyword and makes the paragraph self-contradictory ('ultracode triggers a run' + 'renamed from ultracode to workflow'); mcp (#373) tried to collapse the three MCP scopes to two and claim local scope lives in `.mcp.json` and is private, but the MCP docs list three scopes — Local (`~/.claude.json`, not shared), Project (`.mcp.json`, shared via git), User — so only its `which channel plugins` wording fix was kept. #377 (skills) had an empty diff and was closed as a no-op. All 8 PRs were closed; this single PR consolidates the verified fixes with full EN+AR parity.

Added

plugins: document LSP restartOnCrash/shutdownTimeout and settings.json supported keys — EN + AR

Per the plugins reference (code.claude.com/docs/en/plugins-reference), the LSP `restartOnCrash` and `shutdownTimeout` fields require v2.1.205+ (before which setting either skipped that LSP server at startup), and a plugin's `settings.json` supports only the `agent` and `subagentStatusLine` keys — all other fields are silently ignored. Added both to the plugins module. The unverified `--plugin-dir (v2.1.145+)` tag from audit PR #375 was NOT added (no doc support). Partially incorporates #375.

memory: expand /init multi-phase flow, add decline-import note, clarify no-paths rules — EN + AR

Per the memory docs (code.claude.com/docs/en/memory): expanded the `CLAUDE_CODE_NEW_INIT=1` description (asks which artifacts to set up, explores with a subagent, presents a reviewable proposal); noted that declining a first-time external-import dialog leaves imports disabled and the dialog doesn't reappear; added that files are concatenated in load order (managed → user → project → local, closest read last); and clarified in the quiz that rules without a `paths` field load unconditionally and apply to all files. Partially incorporates #374 — its 'whichever is smaller' change was dropped (docs say 'whichever comes first') and its '~v2.1.198' tag was dropped (misattributed to symlink matching).

Fixed

subagents: built-in agents CAN be name-overridden by a custom subagent — EN + AR

The module claimed built-in subagents are 'always available and not part of the name-override priority system'. The sub-agents docs (code.claude.com/docs/en/sub-agents) say the opposite: 'A user or project subagent named Explore overrides the built-in and keeps its own model field.' Rewrote the sentence to describe the override behavior. Incorporates audit PR #378.

project-setup: --add-dir loads subagent definitions from .claude/agents/ — EN + AR

The `--add-dir` paragraph said the flag 'only grants file access, not the rest of .claude/ configuration'. Per the docs, `--add-dir` also scans a `.claude/agents/` folder in the added directory and loads those subagents; CLAUDE.md files and rules still require `CLAUDE_CODE_ADDITIONAL_DIRECTORIES_CLAUDE_MD=1`. Corrected the sentence. Incorporates audit PR #376.

workflows: routines require Claude Code on the web enabled — EN + AR

The routines availability line named the plans (Pro/Max/Team/Enterprise) but omitted the prerequisite. The routines docs (code.claude.com/docs/en/routines) state routines are available on those plans 'with Claude Code on the web enabled'. Added the clause. Incorporates audit PR #379.

Content

Rejected audit PRs #372 (ultracode/workflow rename) and #373 (MCP scope reduction); closed no-op #377

#372 flipped the ultracode↔workflow rename direction, contradicting the current dynamic-workflow keyword and leaving the paragraph self-contradictory — rejected, original kept. #373 tried to reduce the three MCP scopes to two and claim local scope is stored in `.mcp.json` and private, but the MCP docs (code.claude.com/docs/en/mcp) list three scopes with Local in `~/.claude.json` and Project in the shared `.mcp.json`; only its `which channel plugins` allowedChannelPlugins wording fix was kept. #377 (skills) had an empty diff and was closed as a no-op. All of #372–#379 are closed in favor of this consolidated PR.

Arabic

Arabic parity for every change in this pass

Mirrored all module edits (subagents, project-setup, workflows, plugins, memory, mcp) and the memory quiz clarification in the Arabic content and quiz files, matching the existing Egyptian-Arabic style.

v1.24.27 · Jul 17, 2026

Fix the slash-commands quiz /branch explanation (drop the stale '/fork' framing); reject audit PRs #367–#368 as doc-contradicted

Today's pass opened with the two auto-generated audit PRs, and both were rejected after checking the official docs. #367 (plugins) wanted to change `claude plugin prune` from 'aliased autoremove' to '`autoremove` is not confirmed as a CLI alias', but the Plugins reference (code.claude.com/docs/en/plugins-reference) explicitly lists '**Aliases:** autoremove' under the `plugin prune` command (v2.1.121+) — so the repo's existing content is correct and the PR would have removed a true claim; closed. #368 (slash-commands) wanted to add '`/fork` is its alias' to the `/branch` bullet, but the commands reference (code.claude.com/docs/en/commands) and sub-agents docs confirm that from v2.1.161 `/fork` is a distinct command that hands a side task to a background forked subagent — it was only an alias for `/branch` *before* v2.1.161 — so the addition would have been wrong for current versions; closed. The one genuine inaccuracy was in the slash-commands quiz: Q2's explanation described `/branch` as '(formerly /fork)', which is misleading (nothing was renamed; `/fork` is now a separate command) and had already drifted from the Arabic quiz, which omits it. Rewrote the EN explanation to describe `/branch` accurately and add a short, correct note that `/fork` is now a separate background-subagent command, not a `/branch` alias — matching how the subagents module already documents it.

Fixed

slash-commands quiz: correct the /branch Q2 explanation's stale /fork framing

Q2's explanation called `/branch` '(formerly /fork)', implying `/branch` was renamed from `/fork`. Per the commands and sub-agents docs, `/fork` was an alias for `/branch` only before v2.1.161; from v2.1.161 `/fork` is a distinct command that hands a side task to a background forked subagent. Reworded the explanation to describe `/branch` on its own terms and note that `/fork` is now a separate command, not an alias — consistent with the subagents module (src/content/modules/subagents.md).

Content

Rejected audit PRs #367 (plugins prune/autoremove) and #368 (slash-commands /fork alias)

Both auto-generated audit PRs contradicted the official docs and were closed. #367 would have removed the correct 'aliased autoremove' note on `claude plugin prune` — the Plugins reference lists 'Aliases: autoremove' for that command. #368 would have added a false '`/fork` is its alias' claim to the `/branch` bullet — `/fork` is a distinct background-subagent command from v2.1.161. The repo's existing module content on both topics is already accurate and left unchanged.

Arabic

Arabic parity confirmed for the /branch quiz explanation

The Arabic slash-commands quiz Q2 already omits the '/fork' parenthetical, so the EN fix brings the two languages back into agreement; no Arabic change was needed for this correction.

v1.24.26 · Jul 16, 2026

Document screen-reader accessibility mode (CLAUDE_AX_SCREEN_READER / --ax-screen-reader / axScreenReader); merge audit PRs #364–#365

Today's pass started with the two open auto-generated audit PRs. Both were verified against the official docs, CodeRabbit-clean, and Cloudflare-green, so they were merged: #364 (mcp) reframes the Channels note to say the `--channels` flag was added in v2.1.80 as a research preview and to suggest checking `claude --version`; #365 (plugins) clarifies that `${CLAUDE_PLUGIN_DATA}` is a shell-expansion variable for persistent state and softens the `claude plugin tag` wording to 'introduced in v2.1.118'. Then, checking the Claude Code changelog past the already-documented v2.1.207 surfaced screen-reader mode (v2.1.208), which the settings docs (code.claude.com/docs/en/settings) confirm as the `axScreenReader` setting (v2.1.181+): 'Render screen-reader friendly output: flat text without decorative borders or animations. Screen-reader mode uses the classic renderer, so the tui setting has no effect while it is active. The CLAUDE_AX_SCREEN_READER environment variable and the --ax-screen-reader flag take precedence.' Documented the environment variable in the advanced-features module (EN + AR), added the `--ax-screen-reader` flag to the CLI-flags cheatsheet (EN + AR), added the `CLAUDE_AX_SCREEN_READER` env var to the EN env-vars cheatsheet, and added a catalog entry so the accessibility feature is searchable (EN + AR).

Added

advanced-features: document the screen-reader accessibility mode — EN + AR

Per the settings docs (code.claude.com/docs/en/settings), Claude Code exposes a screen-reader mode as the `axScreenReader` setting (v2.1.181+), the `CLAUDE_AX_SCREEN_READER=1` environment variable, and the `--ax-screen-reader` flag — the variable and flag take precedence over the setting. It renders flat text with no decorative borders or animations for assistive technology, and always uses the classic renderer so the fullscreen/tui preference has no effect while active. Added the environment variable to the advanced-features env-vars section, next to the existing accessibility-related CLAUDE_CODE_NATIVE_CURSOR entry.

reference + catalog: add the --ax-screen-reader flag and CLAUDE_AX_SCREEN_READER env var

Added the `--ax-screen-reader` flag to the CLI-flags cheatsheet (EN + AR), the `CLAUDE_AX_SCREEN_READER` variable to the EN env-vars cheatsheet, and an `env-ax-screen-reader` feature-catalog entry (EN + AR) so the accessibility feature is discoverable through catalog search in both languages.

Content

Merged audit PRs #364 (mcp Channels wording) and #365 (plugins storage wording)

Both auto-generated audit PRs were verified against the official docs, CodeRabbit-clean, and Cloudflare-green. #364 clarifies that `--channels` was added in v2.1.80 as a research preview and suggests checking `claude --version`; #365 clarifies `${CLAUDE_PLUGIN_DATA}` is a shell-expansion variable for persistent state and reframes `claude plugin tag` as 'introduced in v2.1.118'. Squash-merged with clearer commit titles (#364's original title was flagged as too vague by CodeRabbit).

Arabic

Arabic parity for the screen-reader-mode additions

Mirrored the advanced-features env-var paragraph, the CLI-flags cheatsheet entry, and the feature-catalog entry in Arabic.

v1.24.25 · Jul 15, 2026

Document the WebSocket (ws) MCP transport and Auto Mode's default availability; reject the --max-turns → --runs claim (audit PRs #359–#361)

Today's pass reviewed three open PRs (all auto-generated by claude-kb-fixer), verified each against the official Claude Code docs, consolidated the two doc-supported ones into this single change, and rejected the third. (1) mcp (#360): the MCP docs (code.claude.com/docs/en/mcp) document a fourth transport type — WebSocket. WebSocket servers hold a persistent bidirectional connection for servers that push events unprompted; they must be configured via JSON (`type: "ws"` in `.mcp.json`) rather than the `claude mcp add --transport` flag, and they support neither OAuth nor `--transport`. Added `ws` to the transport-selection guidance (EN + AR) and corrected the WebSocket feature-catalog entry, which incorrectly described the config as `transport: websocket` (EN + AR). (2) advanced-features (#359): the permission-modes docs (code.claude.com/docs/en/permission-modes) confirm Auto Mode is now available by default on the Anthropic API, Amazon Bedrock, Google Cloud Vertex AI, and Microsoft Foundry — the `CLAUDE_CODE_ENABLE_AUTO_MODE=1` opt-in that applied in v2.1.158–v2.1.206 was removed in v2.1.207 (the variable is still accepted for backwards compatibility but has no effect). Updated the module (EN + AR), and corrected the supported-model list on the three non-Anthropic providers to Claude Sonnet 5, Opus 4.7, and Opus 4.8 — the docs list Sonnet 5, which both the module and PR #359 omitted. (3) workflows (#361): REJECTED. The PR replaced the valid `--max-turns` flag with a non-existent `--runs <n>` flag, citing a third-party changelog rather than the official docs. The CLI reference (code.claude.com/docs/en/cli-reference) confirms `--max-turns` exists ('Limit the number of agentic turns (print mode only)') and lists no `--runs` flag, so the repo's existing `--max-turns` content is correct and left unchanged; #361 is closed. #359 and #360 are superseded and closed.

Added

mcp: document the WebSocket (ws) transport — EN + AR

Per the MCP docs (code.claude.com/docs/en/mcp), WebSocket is a fourth MCP transport for remote servers that push events unprompted over a persistent bidirectional connection. Added `ws` to the transport-selection guidance, noting it must be configured with `type: "ws"` in `.mcp.json` (not `claude mcp add --transport`, which doesn't accept `ws`) and supports neither OAuth nor `--transport`. Consolidates audit PR #360.

Fixed

mcp: correct the WebSocket feature-catalog config — EN + AR

The WebSocket MCP Transport feature-catalog entry described the config as `transport: websocket`, which is not how it's configured. Corrected to `type: "ws"` in `.mcp.json`, matching the module and the official docs.

advanced-features: Auto Mode is available by default on all four providers — EN + AR

Per the permission-modes docs (code.claude.com/docs/en/permission-modes), Auto Mode is now available by default on the Anthropic API, Amazon Bedrock, Google Cloud Vertex AI, and Microsoft Foundry; the `CLAUDE_CODE_ENABLE_AUTO_MODE=1` opt-in that applied on the non-Anthropic providers in v2.1.158–v2.1.206 was removed in v2.1.207 (still accepted for compatibility, no effect). Also corrected the supported-model list on the three non-Anthropic providers to Claude Sonnet 5, Opus 4.7, and Opus 4.8 — the previous text and PR #359 both dropped Sonnet 5. Consolidates audit PR #359.

Content

Rejected audit PR #361's --max-turns → --runs replacement

#361 proposed replacing `--max-turns` with a `--runs <n>` flag across the workflows module and templates (EN + AR), citing a third-party changelog. The official CLI reference (code.claude.com/docs/en/cli-reference) confirms `--max-turns` exists and lists no `--runs` flag, so the change would have introduced a non-existent flag. The existing `--max-turns` content is correct and left unchanged; #361 is closed.

Arabic

Arabic parity for the mcp and advanced-features updates

The Arabic mcp and advanced-features modules and the Arabic feature-catalog mirror all three EN changes — the WebSocket (ws) transport guidance, the corrected WebSocket config, and the Auto Mode default-availability and supported-model updates.

v1.24.24 · Jul 14, 2026

Correct MCP tool-search fallback, memory @import cost, and plugin marketplace sources; consolidate audit PRs #355–#357

Today's pass reviewed three open PRs (all auto-generated by claude-kb-fixer) and consolidated the doc-supported parts into one change, each verified against the official docs. (1) mcp (#355): the MCP docs (code.claude.com/docs/en/mcp#scale-with-mcp-tool-search) confirm tool search is on by default and that 'in configurations without tool search, such as Google Cloud's Agent Platform, a custom ANTHROPIC_BASE_URL, or ENABLE_TOOL_SEARCH=false, Claude uses the WaitForMcpServers tool instead.' Replaced the module's older 'off by default only on Vertex AI / non-first-party proxy' aside with this doc-verified phrasing naming the WaitForMcpServers fallback (EN + AR). (2) memory (#356): the memory docs (code.claude.com/docs/en/memory#import-additional-files) state imported files 'are expanded and loaded into context at launch' and 'imported files still load and enter the context window at launch' — so the module's '@path/to/file lets you reference existing documentation rather than duplicating it' wrongly implied imports avoid loading. Corrected to note imports load at launch and still consume context tokens (EN + AR). #356 also proposed collapsing the CLAUDE.md scopes to 'three truly distinct locations: managed policy, user/project instructions, and local instructions' — this is NOT supported: the docs list four distinct scopes (managed, user, project, local) and explicitly separate user (~/.claude/CLAUDE.md, personal) from project (./CLAUDE.md, team-shared). Applied only the accurate half of that finding (./CLAUDE.md and ./.claude/CLAUDE.md are two alternative supported locations for the project scope, not one shared file) and dropped the misleading 'three locations' sentence. (3) plugins (#357): the discover-plugins docs (code.claude.com/docs/en/discover-plugins#add-marketplaces) list marketplace sources as GitHub repositories (owner/repo), git URLs, local paths, and remote URLs to marketplace.json files — npm is not among them. Removed the incorrect 'npm, or other supported package sources' claim (EN), and added the corrected sentence to the AR module, which was missing it entirely (pre-existing parity gap). #357 also reordered the Arabic plugins quiz: AR q5–q7 were rotated out of sync with English (AR q5 was the subagents question that maps to EN q7), so AR now matches EN — q5 cache cleanup, q6 version tag, q7 subagent restrictions. #355, #356, and #357 are superseded and closed.

Fixed

mcp: name the WaitForMcpServers fallback when tool search is disabled

Per the MCP docs (code.claude.com/docs/en/mcp), tool search is on by default, and in configurations without it — Google Cloud's Agent Platform, a custom ANTHROPIC_BASE_URL, or ENABLE_TOOL_SEARCH=false — Claude uses the WaitForMcpServers tool instead. Replaced the older 'off by default on Vertex AI / non-first-party proxy' aside with this doc-verified phrasing. Consolidates audit PR #355.

memory: @import loads files into context at launch and still consumes tokens

Per the memory docs (code.claude.com/docs/en/memory), the @path/to/file import syntax expands imported files and loads them into context at launch alongside the CLAUDE.md that references them — they still consume context tokens. Replaced the misleading 'reference rather than duplicate' phrasing. Also clarified that ./CLAUDE.md and ./.claude/CLAUDE.md are two alternative supported locations for the project scope, not one shared file. Consolidates the doc-supported part of audit PR #356.

plugins: correct marketplace sources (npm is not one) — EN + AR

Per the discover-plugins docs (code.claude.com/docs/en/discover-plugins), plugin marketplaces source from GitHub repositories (owner/repo), git URLs, local paths, and remote marketplace.json URLs — not npm. Removed the incorrect npm claim in the EN module and added the corrected sentence to the AR module, which previously lacked it. Also reordered the Arabic plugins quiz (q5 cache cleanup, q6 version tag, q7 subagent restrictions) to match the English sequence. Consolidates audit PR #357.

Content

Rejected audit PR #356's 'three memory locations' reframing

#356 proposed collapsing the CLAUDE.md scopes to 'three truly distinct locations: managed policy, user/project instructions, and local instructions.' The memory docs list four distinct scopes and keep user (~/.claude/CLAUDE.md, personal) separate from project (./CLAUDE.md, team-shared), so this reframing is not supported and was dropped; only the accurate clarification that ./CLAUDE.md and ./.claude/CLAUDE.md are two alternative supported locations for the project scope (not one shared file) was kept.

Arabic

Arabic parity for the mcp, memory, and plugins corrections

The Arabic mcp and memory modules mirror the WaitForMcpServers fallback and the @import context-cost correction; the Arabic plugins module gains the corrected marketplace-sources sentence; and the Arabic plugins quiz is realigned to the English question order (q5–q7).

v1.24.23 · Jul 12, 2026

Drop retired Opus 4.6 fast mode and fix the Shift+Tab cycle order; consolidate audit PR #352, reject #351 and #353

Today's pass reviewed three open PRs (all auto-generated by claude-kb-fixer). PR #352 (commands) checked out in part against the official docs and is consolidated with corrections. (1) Fast mode: the fast-mode docs (code.claude.com/docs/en/fast-mode) state 'Fast mode is supported on Opus 4.8 and Opus 4.7' and not on other models, so the module's claim that Opus 4.6 is supported (removed 'about 30 days after the Opus 4.8 launch') is stale — Opus 4.6 fast mode is gone. #352 fixed this but invented version numbers ('deprecated in v2.1.154 and removed in v2.1.176') the docs don't carry; this change instead uses the doc-supported facts: Opus 4.8 + 4.7 only, and Opus 4.7 fast mode is deprecated as of June 25, 2026 and removed July 24, 2026 (after which requests error out, no fallback). It also fixes the downstream line #352 missed, flagged by CodeRabbit — the rate-limit pool is 'shared across Opus 4.8 and 4.7', not 4.8/4.7/4.6. (2) Shift+Tab: the permission-modes docs (code.claude.com/docs/en/permission-modes) give the cycle as `default` → `acceptEdits` → `plan`, with `auto` appearing on eligibility, `bypassPermissions` appearing after `--permission-mode bypassPermissions`, `--dangerously-skip-permissions`, or `--allow-dangerously-skip-permissions` (the `--allow-` variant adds without activating), and `dontAsk` never in the cycle. #352 fixed the module prose but omitted the `--allow-dangerously-skip-permissions` variant (CodeRabbit flagged this); this change adds it and corrects the same wrong order (`default → plan → acceptEdits → auto`) that had leaked into three other surfaces the audit didn't touch: the terminal simulator's `/permissions` output, the project-setup terminal step, and the reference cheatsheet — EN and AR. #352 is superseded and closed. PR #351 (advanced-features) is rejected: it re-labels `enforceAvailableModels` as 'managed-only … cannot be set in user or project settings', but the settings docs (code.claude.com/docs/en/settings) describe it as a setting that can be set in any scope whose effect constrains the Default model — the existing prose is already accurate, and the managed-only qualifier isn't supported. PR #353 (skills) is rejected on both findings, each an already-litigated regression: renaming `/fewer-permission-prompts` to `/less-permission-prompts` (the live skill and the commands reference both use `/fewer-permission-prompts`; reverted before in v1.24.8 and rejected as audit #326), and changing the skill-listing budget from 1% to 2% (the /en/skills docs say verbatim 'The budget scales at 1% of the model's context window', with 0.02 = 2% only as the raise-it example; rejected before as #288/#290).

Fixed

commands: fast mode supports Opus 4.8 and 4.7 only — Opus 4.6 fast mode is retired

Per the fast-mode docs (code.claude.com/docs/en/fast-mode), fast mode is supported on Opus 4.8 and Opus 4.7 only; earlier Opus models like 4.6 are no longer supported. Replaced the stale 'supports Opus 4.6, removed ~30 days after the Opus 4.8 launch' copy with the doc-supported facts (Opus 4.7 fast mode deprecated June 25, 2026, removed July 24, 2026, no fallback), and corrected the rate-limit pool to 'shared across Opus 4.8 and 4.7'. Avoided the unverified v2.1.176 version claim from audit #352.

commands + terminal + cheatsheet: Shift+Tab cycles default → acceptEdits → plan

Per the permission-modes docs (code.claude.com/docs/en/permission-modes), Shift+Tab cycles `default` → `acceptEdits` → `plan`; `auto`, `bypassPermissions` (added by `--permission-mode bypassPermissions`, `--dangerously-skip-permissions`, or `--allow-dangerously-skip-permissions`), and `dontAsk` are not in that default cycle. Rewrote the commands module prose to include the `--allow-dangerously-skip-permissions` variant (missed by audit #352) and fixed the wrong order (`default → plan → acceptEdits → auto`) in the terminal `/permissions` output, the project-setup terminal step, and the reference cheatsheet.

Content

Rejected audit PR #351 (enforceAvailableModels) and #353 (/fewer-permission-prompts rename, skills budget 1%→2%)

#351's 'managed-only, cannot be set in user or project settings' qualifier for `enforceAvailableModels` is not supported by the settings docs, which describe a setting settable in any scope; the existing prose stays. #353 re-proposed two already-rejected regressions — the `/less-permission-prompts` rename (live skill and commands reference use `/fewer-permission-prompts`) and the skills budget 1%→2% change (docs say the budget scales at 1% of the context window) — so both are declined.

Arabic

Arabic parity for the fast-mode and Shift+Tab corrections

The Arabic commands module, project-setup terminal step, terminal `/permissions` output, and reference cheatsheet mirror the fast-mode Opus 4.8/4.7 update and the corrected `default → acceptEdits → plan` cycle order.

v1.24.22 · Jul 11, 2026

Document that alwaysLoad blocks startup until the MCP server connects; consolidate audit PR #349

Today's pass reviewed the one open PR (auto-generated by claude-kb-fixer). PR #349 checked out against the MCP docs (code.claude.com/docs/en/mcp): the docs state that setting `alwaysLoad: true` on a server 'also blocks startup until the server connects, capped at the standard 5-second connect timeout,' since the tools must be present when the first prompt is built, while other servers keep connecting in the background. The site's MCP module described only the tool-search-deferral side of `alwaysLoad` and omitted this startup-blocking behavior. This consolidated change applies #349's correction (EN + AR) with a slightly clearer phrasing that addresses two review comments: it labels the 5-second cap as a distinct connect attempt (not a change to the default MCP startup timeout, per CodeRabbit) and notes other configured servers keep connecting in the background — both directly supported by the docs. It also adds the version bump and changelog entry #349 lacked (flagged by Codex). #349 is superseded and closed. No quiz, terminal, template, or cheatsheet surface referenced this `alwaysLoad` detail, so none needed changing; the mcp quiz and terminal `/help` already cover `alwaysLoad` at the tool-search level.

Fixed

mcp: alwaysLoad: true also blocks startup until that server connects (5-second connect cap)

Per the MCP docs (code.claude.com/docs/en/mcp), `alwaysLoad: true` doesn't only exempt a server from tool-search deferral — it also blocks startup until that server connects, capped at the standard 5-second connect timeout, because the tools must exist when the first prompt is built. Other configured servers keep connecting in the background. Added this to the MCP module, which previously described only the deferral-exemption behavior.

Arabic

Arabic parity for the alwaysLoad startup-blocking note

The Arabic MCP module mirrors the added note (alwaysLoad blocks startup on that server's connect, 5-second cap, other servers keep connecting in the background).

v1.24.21 · Jul 9, 2026

Remove the invalid 'auto' effort level from the hooks and subagents modules; consolidate audit PR #344, reject #345

Today's pass reviewed two open PRs (both auto-generated by claude-kb-fixer). PR #344 checked out: the hooks docs (code.claude.com/docs/en/hooks) list the hook-input `effort` object's levels verbatim as `low`, `medium`, `high`, `xhigh`, `max` — no `auto`. The site's hooks module had listed a sixth value, `auto`, which is wrong: per the model-config docs (code.claude.com/docs/en/model-config), `auto` is a `/effort` *command* argument that resets to the model default (and a `CLAUDE_CODE_EFFORT_LEVEL` value), not an effort level the runtime ever reports. This consolidated change applies #344's hooks correction (EN + AR) and extends it to the subagents module, where the same bad `auto` value had crept into the frontmatter `effort` description — the sub-agents docs (code.claude.com/docs/en/sub-agents) list that field's options as `low`, `medium`, `high`, `xhigh`, `max` only. Both erroneous `auto` values trace back to the same earlier audit (v1.19.x, 'Hooks and subagents modules now list the full effort set — low, medium, high, xhigh, max, auto'), so fixing hooks alone would have left subagents wrong; #344 is superseded and closed. The `/effort` command entries in the commands and slash-commands modules keep `auto`, because there it is a correct command argument (reset to model default), not a claimed effort level. The hooks and advanced-features quizzes already listed the levels correctly (low/medium/high/xhigh/max), so no quiz, terminal, or template surface needed changing. PR #345 (subagents quiz q7) is rejected: it only reordered and reworded option (a)'s already-correct, already-version-scoped explanation of `/agents` in v2.1.198 — the sub-agents docs confirm the existing text ('/agents no longer opens the interactive wizard, prints a notice') is accurate, and both the old and proposed wording keep the 'as of v2.1.198' framing, so the audit's stated rationale (that it reads as permanent behavior) doesn't hold. No factual change, so the existing explanation stays.

Fixed

hooks + subagents: 'auto' is not an effort level (hook input and subagent frontmatter list low/medium/high/xhigh/max)

Per the hooks docs (code.claude.com/docs/en/hooks) and sub-agents docs (code.claude.com/docs/en/sub-agents), the hook-input `effort` object and the subagent frontmatter `effort` field each accept only `low`, `medium`, `high`, `xhigh`, `max`. Removed the invalid `auto` value from both modules. `auto` remains a valid `/effort` command argument (reset to model default) in the commands and slash-commands modules, so those are unchanged.

Arabic

Arabic parity for the effort-level correction

The Arabic hooks and subagents modules mirror the corrected effort-level list (low/medium/high/xhigh/max, no auto).

v1.24.20 · Jul 8, 2026

Correct the --bare flag description; consolidate audit PR #342, reject #341

Today's pass reviewed the two open PRs (both auto-generated by claude-kb-fixer). PR #342 (--bare) checked out against the headless docs (code.claude.com/docs/en/headless): '--bare' reduces startup time by skipping auto-discovery of hooks, skills, plugins, MCP servers, auto memory, and CLAUDE.md — only explicitly-passed flags and settings take effect. The site's old copy framed it as producing the 'cleanest scripted output', which is wrong: it's a startup-speed/reproducibility flag, not an output-formatting one. This consolidated change applies that correction on both surfaces where --bare appeared — the workflows module prose (which #342 fixed) AND the reference cheatsheet's --bare entry (which #342 missed and still described it as 'Cleanest output... no formatting or decoration') — EN and AR, plus the changelog and version bump #342 lacked. #342 is superseded and closed. PR #341 (subagents) is rejected: it wanted to relabel the removal of TeamCreate/TeamDelete as a 'regression from v2.1.177', but the agent-teams docs (code.claude.com/docs/en/agent-teams) present it as intentional streamlining ('spawning a teammate no longer needs a setup step') and only state the tools 'no longer exist' — nothing supports the 'regression' framing, so the existing 'were removed' wording stays. No quiz/terminal/template surface referenced --bare, so none needed changing.

Fixed

workflows + cheatsheet: --bare is a startup-speed flag, not an output-formatting one

Per the headless docs (code.claude.com/docs/en/headless), `--bare` reduces startup time by skipping auto-discovery of hooks, skills, plugins, MCP servers, auto memory, and CLAUDE.md, so only explicitly-passed flags and settings take effect. Replaced the misleading 'cleanest scripted output' framing in the workflows module and the 'Cleanest output... no formatting or decoration' description in the reference cheatsheet.

Arabic

Arabic parity for the --bare correction

The Arabic workflows module and reference cheatsheet mirror the corrected --bare description (startup speed and reproducibility over output cleanliness).

v1.24.19 · Jul 7, 2026

Clarify the Ctrl+G plan-edit shortcut; reject audit PRs #334–#339

Today's pass reviewed six auto-generated audit PRs (claude-kb-fixer, all opened 2026-07-07) against the official Claude Code docs. All six are rejected. (1) Five of them (#335 hooks, #336 skills, #337 slash-commands, #338 subagents, #339 workflows) each cited a fabricated CHANGELOG line — 'Simplified effort levels to low/medium/high (removed max)' at v2.1.202 — that does not exist anywhere in the CHANGELOG. The v2.1.202 entry covers dynamic-workflow settings and crash fixes only, and v2.1.154 is the release that introduced `/effort xhigh`. The official model-config docs (code.claude.com/docs/en/model-config) still document `low`, `medium`, `high`, `xhigh`, `max` for Fable 5 / Sonnet 5 / Opus 4.8 / Opus 4.7, and confirm `/effort ultracode` sends `xhigh` plus dynamic-workflow orchestration — so the effort-level pages are correct and stay unchanged. (2) #334 claimed `Ctrl+G` does not open the plan and deleted the sentence — but the permission-modes docs (code.claude.com/docs/en/permission-modes) state, under 'Review and approve a plan': 'Press Ctrl+G to open the proposed plan in your default text editor and edit it directly before Claude proceeds.' The original content was correct, so #334 is rejected too. #334's audit had only checked the interactive-mode/CHANGELOG surfaces (which describe Ctrl+G's general behavior — editing your prompt) and missed the plan-mode behavior. This change keeps the correct plan-edit content and makes two accuracy refinements flagged in review (Codex): the reference cheatsheet's Ctrl+G entry now distinguishes the general behavior (opens your prompt) from the plan-mode behavior (opens the proposed plan), and the terminal simulator's /plan output no longer implies Ctrl+G exits plan mode — Ctrl+G edits the plan, Shift+Tab exits. EN and AR.

Fixed

Ctrl+G opens the proposed plan in your editor when approving in plan mode

Per the permission-modes docs (code.claude.com/docs/en/permission-modes), pressing `Ctrl+G` at the plan-approval prompt opens the proposed plan in your default text editor to edit before Claude proceeds. Kept this correct content (audit PR #334 had wrongly removed it) and refined two surfaces for precision: the reference cheatsheet now separates the general behavior (opens your prompt) from the plan-mode behavior, and the terminal simulator's /plan output no longer suggests Ctrl+G exits plan mode.

Arabic

Arabic parity for the Ctrl+G plan-edit clarification

The Arabic advanced-features module, reference cheatsheet, terminal simulator /plan output, and guided terminal step mirror the clarified Ctrl+G plan-edit content.

v1.24.18 · Jul 4, 2026

Correct the Desktop App Linux availability; consolidate audit PR #331

Today's pass reviewed the one open PR (#331, auto-generated by claude-kb-fixer) against the official Claude Code docs. The claim checked out: the 'Claude Desktop on Linux (beta)' page (code.claude.com/docs/en/desktop-linux) states that Linux support for the desktop app is in beta with the Chat, Cowork, and Code tabs all available, requires Ubuntu 22.04+ or Debian 12+ on x86_64/arm64, and installs via Anthropic's apt repository or a downloaded .deb — so the getting-started module's 'not available on Linux' line was outdated. PR #331 fixed the prose (EN + AR) but two reviewer notes were valid: it used a root-relative [/en/desktop-linux] link that would 404 on this static site, and it left package.json unbumped. This consolidated change applies the correction with the full code.claude.com/docs/en/desktop-linux URL, adds the beta's known gaps (Computer Use, dictation, and Fedora/RHEL aren't in the Linux beta yet; the CLI still covers more distros), bumps the version, and updates the changelog — EN and AR. The claim lived only in the getting-started module prose (the feature-catalog Desktop App entry is platform-agnostic and advanced-features makes no Linux-availability claim), so no quiz, terminal, or catalog surface needed changing. #331 is superseded by this change and closed.

Fixed

getting-started: the Desktop App now supports Linux in beta (Ubuntu 22.04+/Debian 12+)

Per the official docs (code.claude.com/docs/en/desktop-linux), the Claude desktop app is in beta on Linux — Ubuntu 22.04+ or Debian 12+, x86_64/arm64, installed via Anthropic's apt repository or a downloaded .deb — with Computer Use, dictation, and Fedora/RHEL not yet included. Replaced the outdated 'not available on Linux' line in the getting-started module, using the full docs URL rather than a root-relative link that would 404 on the static site.

Arabic

Arabic parity for the Desktop App Linux-beta correction

The Arabic getting-started module mirrors the Desktop-App-on-Linux-beta correction, including the beta's known gaps and the full docs URL.

v1.24.17 · Jul 3, 2026

Correct /agents behavior everywhere; consolidate audit PR #329

Today's pass reviewed the one open PR (#329, auto-generated by claude-kb-fixer) against the official Claude Code docs. The claim checked out: the 'Run agents in parallel' page (code.claude.com/docs/en/agents) states that 'As of v2.1.198, /agents no longer opens a panel; it prints a notice pointing to the subagent file locations. To create and edit custom subagents, ask Claude or edit the files directly.' PR #329 corrected only the subagents module prose (EN + AR) and left package.json unbumped — codex flagged the missing version bump. This consolidated change fixes the claim on every surface it appeared, EN and AR: the subagents module prose, the reference cheatsheet's /agents entry, the terminal simulator's /agents output, the subagents module's guided terminal step, three subagents quiz explanations (the interactive-menu distractor plus the two 'lists/manages definitions' mentions), and the /agents feature-catalog entry so search stays accurate. #329 is superseded by this change and closed.

Fixed

subagents: /agents no longer opens an interactive panel (v2.1.198)

Per the official docs (code.claude.com/docs/en/agents), as of v2.1.198 /agents no longer opens a panel — it prints a notice pointing to the subagent file locations, and custom subagents are created or edited by asking Claude or editing the files directly. Corrected across the subagents module prose, the reference cheatsheet, the terminal simulator's /agents output, the subagents guided terminal step, three subagents quiz explanations, and the /agents feature-catalog entry.

Arabic

Arabic parity for the /agents behavior correction

The Arabic subagents module, reference cheatsheet, terminal simulator, guided terminal step, subagents quiz, and feature catalog mirror the /agents-prints-a-notice correction.

v1.24.16 · Jul 2, 2026

Correct the Explore agent's model everywhere; consolidate audit PR #327 and reject #326

Today's pass reviewed two auto-generated audit PRs against the official Claude Code sources. (1) subagents (#327): the CHANGELOG (v2.1.198, 'The built-in Explore agent now inherits the main session's model (capped at opus) instead of running on haiku') confirms the Explore agent no longer runs on Haiku. PR #327 fixed only the module prose and the q4 correct answer, and CodeRabbit flagged that the quiz distractors still described Haiku. This consolidated change corrects the claim on every surface it appeared, EN and AR: the subagents module prose, all four subagents quiz options (correct answer + the a/c/d distractor explanations), the skills quiz explanation for `agent: Explore`, the reference cheatsheet's built-in agents line, the terminal simulator's `claude agents` output, and the Explore feature-catalog entry so search stays accurate. #327 is superseded by this change. (2) slash-commands (#326): rejected. It re-proposed renaming `/fewer-permission-prompts` to `/less-permission-prompts` — a change this project already investigated and reverted (see v1.24.8): the current CHANGELOG has no mention of either name, and the live Claude Code skill is `/fewer-permission-prompts`, so the existing content is correct and stays.

Fixed

subagents: the built-in Explore agent inherits the main session model (capped at opus), not Haiku

Per the Claude Code CHANGELOG (v2.1.198), the built-in Explore agent now inherits the main session's model, capped at opus, instead of running on Haiku. Corrected across the subagents module prose, all four subagents quiz options (the correct answer and the a/c/d distractor explanations), the skills quiz explanation for `agent: Explore`, the reference cheatsheet, the terminal simulator's `claude agents` output, and the Explore feature-catalog entry.

slash-commands: kept /fewer-permission-prompts (rejected audit PR #326)

Auto-generated PR #326 re-proposed renaming `/fewer-permission-prompts` to `/less-permission-prompts`, a change already investigated and reverted in v1.24.8. The current CHANGELOG mentions neither name and the live skill is `/fewer-permission-prompts`, so the existing content is correct and unchanged.

Arabic

Arabic parity for the Explore agent model correction

The Arabic subagents module, subagents and skills quizzes, reference cheatsheet, terminal simulator, and feature catalog mirror the Explore-inherits-the-session-model correction.

v1.24.15 · Jul 1, 2026

Document fallback model chains (--fallback-model / fallbackModel)

With no open PRs or issues, today's pass checked recent Claude Code releases against the official docs for an uncovered, doc-confirmed feature. Fallback model chains (from v2.1.166) were entirely missing from the platform. The model-config reference (code.claude.com/docs/en/model-config, 'Fallback model chains') confirms that when the primary model is overloaded, unavailable, or returns another non-retryable server error, Claude Code switches to a fallback model instead of failing — while authentication, billing, rate-limit, request-size, and transport errors never trigger a switch. Chains are tried in order, capped at three models after de-duplication, and the switch lasts the current turn only. Set a chain per session with `claude --fallback-model sonnet,haiku`, or persist it with a `fallbackModel` array in settings; the flag takes precedence over the setting and `"default"` expands to the account default. The changelog's separate 'post-session hook' wording (v2.1.169) was checked too but the official hooks docs name the event `SessionEnd`, not `post-session`, so nothing was invented there. Added the fallback-model section to the advanced-features module, the reference cheatsheet, the feature catalog (so search picks it up), and a new quiz question — EN and AR.

Improved

advanced-features: document fallback model chains

Added a Fallback Model Chains section covering the `--fallback-model` flag and the `fallbackModel` settings array: tried in order when the primary model is overloaded, unavailable, or returns a non-retryable server error; auth/billing/rate-limit/size/transport errors never switch; capped at three models; the switch lasts the current turn only; the flag takes precedence over the setting (code.claude.com/docs/en/model-config).

Reference cheatsheet and feature catalog: --fallback-model entry

Added the `--fallback-model <list>` CLI flag to the reference cheatsheet and the feature catalog so the search palette surfaces fallback model chains.

advanced-features quiz: new question on fallback behavior

Added quiz q30 testing what happens when the primary model returns an overloaded error mid-turn with a fallback chain configured (switch for the current turn only, then retry the primary).

Arabic

Arabic parity for fallback model chains

Mirrored the Fallback Model Chains section, the cheatsheet and feature-catalog entries, and quiz q30 in the Arabic advanced-features module and data files.

v1.24.14 · Jun 30, 2026

Consolidate three audit PRs (memory, getting-started, advanced-features); reject one unsupported claim

Today's pass reviewed three auto-generated audit PRs against the official Claude Code docs and shipped only what the docs confirm, EN and AR. (1) memory (#323): applied verbatim from code.claude.com/docs/en/memory — `CLAUDE.md` and `CLAUDE.local.md` files above the working directory are loaded in full at launch, while subdirectory files load on demand when Claude reads files there. (2) getting-started (#322): the auto-generated text claimed the PowerShell tool is now the default on all Windows and that Git for Windows is no longer required. The docs (code.claude.com/docs/en/setup) and the changelog don't support that blanket claim — Git Bash is used when Git for Windows is installed; PowerShell is the shell tool only when Git Bash is absent; with Git Bash present the PowerShell tool is still rolling out progressively (opt in with `CLAUDE_CODE_USE_POWERSHELL_TOOL=1`), and is default-on only for Bedrock, Vertex, and Foundry users. Rewrote the paragraph to state each case accurately, mirroring the fix in Arabic, as CodeRabbit/Codex flagged. (3) advanced-features (#321): rejected. The PR added that `cleanupPeriodDays` also cleans `~/.claude/tasks/`, `~/.claude/shell-snapshots/`, and `~/.claude/backups/`. The official settings docs enumerate only session files and orphaned subagent worktrees — backups are intentionally kept — and no changelog entry supports the wider scope, so the claim was not added. The Arabic module and its quiz already carried this unsupported claim from an earlier pass; both were corrected back to session-files-plus-orphaned-worktrees to match the English and the docs. PRs #321–#323 are superseded by this consolidated change.

Improved

memory: CLAUDE.md/CLAUDE.local.md above the cwd load in full at launch

Clarified that `CLAUDE.md` and `CLAUDE.local.md` files in the directory hierarchy above the working directory are loaded in full at launch, while subdirectory files load on demand when Claude reads files in those directories (code.claude.com/docs/en/memory).

Fixed

getting-started: qualify the Windows PowerShell-tool behavior

Corrected an over-broad claim that PowerShell is the default shell tool on all Windows and that Git for Windows is no longer required. Git Bash is used when Git for Windows is installed; the PowerShell tool is the shell only when Git Bash is absent; with Git Bash present it is rolling out progressively (opt in with CLAUDE_CODE_USE_POWERSHELL_TOOL=1) and is default-on only for Bedrock, Vertex, and Foundry users (code.claude.com/docs/en/setup).

advanced-features: remove unsupported cleanupPeriodDays cleanup scope

The Arabic advanced-features module and quiz claimed cleanupPeriodDays also removes ~/.claude/tasks/, shell-snapshots/, and backups/. The official settings docs list only session files and orphaned subagent worktrees, so the extra scope was removed to match the English module and the docs. The auto-generated PR that tried to add the same claim to the English module was not merged.

Arabic

Arabic parity for the memory, getting-started, and cleanupPeriodDays fixes

The Arabic memory and getting-started modules mirror the English wording changes, and the Arabic advanced-features module and quiz q7 were corrected back to the documented cleanupPeriodDays scope (session files plus orphaned worktrees).

v1.24.13 · Jun 29, 2026

Document claude mcp login / logout CLI authentication

With no open PRs or issues, today's pass checked recent Claude Code releases against the official docs for an uncovered, doc-confirmed feature. The mcp module documented OAuth only through the in-session `/mcp` panel and never mentioned the command-line equivalent. The MCP reference (code.claude.com/docs/en/mcp, 'Authenticate from the command line') confirms `claude mcp login <name>` runs a configured server's OAuth flow directly from the shell (from v2.1.186) so you don't need to open `/mcp`, and `claude mcp logout <name>` clears stored credentials. As of v2.1.191 the command detects when no local browser is available (SSH, headless Linux) and prints the authorization URL; `--no-browser` forces that prompt. Added to the mcp module, the reference cheatsheet, the terminal simulator (new `claude mcp login` and `claude mcp logout` commands plus a hint in the `/mcp` output), and the feature catalog so search picks it up — EN and AR.

Improved

mcp: document the claude mcp login / logout CLI authentication commands

`claude mcp login <name>` runs a configured server's OAuth flow from the shell without opening the in-session `/mcp` panel (from v2.1.186), and `claude mcp logout <name>` clears its stored credentials. `--no-browser` prints the authorization URL instead of opening a browser — useful over SSH, where you open the URL locally and paste the redirect URL back at the prompt. Added to the mcp module, reference cheatsheet, and feature catalog.

terminal: add claude mcp login and claude mcp logout to the simulator

The terminal simulator now responds to `claude mcp login` (with the --no-browser flag and an OAuth success output) and `claude mcp logout`, and the `/mcp` panel output lists `claude mcp login` under its manage-servers hint.

Arabic

Arabic parity for the MCP CLI authentication commands

The Arabic mcp module, reference cheatsheet, terminal simulator, and feature catalog mirror the `claude mcp login` / `claude mcp logout` documentation, including the --no-browser / SSH note.

v1.24.12 · Jun 28, 2026

Consolidate five audit PRs across memory, mcp, plugins, subagents, and workflows (supersedes #314–#318)

Today's pass reviewed five auto-generated audit PRs against the official Claude Code docs and shipped all five confirmed findings as one consolidated change, EN and AR. (1) mcp/channels (#314): reworded the Channels intro to lead with the research-preview status and the v2.1.80 minimum, matching code.claude.com/docs/en/channels ('Channels are in research preview and require Claude Code v2.1.80 or later'). (2) memory (#315): added that path-scoped rules trigger when Claude reads matching files (not on every tool use), that rules without a paths field load at launch with .claude/CLAUDE.md priority, and that circular symlinks are handled gracefully, plus a new 'Write effective instructions' section (context-window visualization, target under 200 lines per CLAUDE.md) — all verbatim-confirmed against code.claude.com/docs/en/memory. Critically, the auto-generated PR #315 had deleted the module's `<!-- terminal: guided -->` marker in the English file (the Arabic kept it); we restored the marker and placed the new paragraph before it, keeping the guided terminal step working and EN/AR in parity. (3) plugins (#316): documented that a single-skill plugin may place SKILL.md at the plugin root and that the frontmatter name field becomes the invocation name (code.claude.com/docs/en/plugins). (4) subagents (#317): noted that the built-in Explore and Plan agents skip CLAUDE.md and git status to keep research fast, while every other built-in and custom subagent loads both (code.claude.com/docs/en/sub-agents). (5) workflows (#318): clarified that dynamic-workflow resume only works within the same Claude Code session — exiting Claude Code starts the workflow fresh next session (code.claude.com/docs/en/workflows). PRs #314–#318 are superseded by this consolidated change.

Improved

memory: clarify path-scoped rule activation and add a 'Write effective instructions' section

Path-scoped rules in .claude/rules/ trigger when Claude reads files matching the pattern, not on every tool use; rules without a paths field load at launch with the same priority as .claude/CLAUDE.md; circular symlinks are detected and handled gracefully. A new 'Write effective instructions' section covers the context-window visualization and the under-200-lines-per-CLAUDE.md target. Added to the memory module.

mcp, plugins, subagents, workflows: document four confirmed doc nuances

Channels lead with their research-preview status and v2.1.80 minimum (mcp); a single-skill plugin can place SKILL.md at the plugin root with the frontmatter name as the invocation name (plugins); the built-in Explore and Plan agents skip CLAUDE.md and git status while every other subagent loads both (subagents); and dynamic-workflow resume only works within the same Claude Code session, restarting fresh after you exit (workflows).

Fixed

memory: restore the deleted guided-terminal marker from audit PR #315

Auto-generated PR #315 replaced the English memory module's `<!-- terminal: guided -->` marker with its new paragraph, which would have broken the guided terminal step and left EN out of parity with AR (which kept the marker). The marker is restored and the new paragraph now sits before it, matching the Arabic structure.

Arabic

Arabic parity across all five module updates

The Arabic memory, mcp, plugins, subagents, and workflows modules mirror every English change — path-scoped rule behavior and the effective-instructions section, the Channels rewording, the single-skill SKILL.md note, the Explore/Plan skip note, and the workflow resume clarification.

v1.24.11 · Jun 27, 2026

Distinguish MCP startup timeout from tool-execution timeout (supersedes audit PR #312)

Today's pass reviewed auto-generated audit PR #312 (mcp) against the official MCP reference (code.claude.com/docs/en/mcp). The PR proposed re-wording the MCP_TIMEOUT line to 'a per-server startup timeout, not a general per-server timeout' — but the module already correctly called it the 'MCP server startup timeout', and the proposed clause was both awkward and imprecise (MCP_TIMEOUT is a launch-time environment variable, not a per-server setting). Rather than ship that, we addressed the real, documented gap: the module covered only the startup timeout and never mentioned the separate tool-execution timeout. The docs document a per-server `timeout` field in `.mcp.json` (milliseconds) that caps how long any single tool call may run, overrides the `MCP_TOOL_TIMEOUT` environment variable for that server, acts as a hard wall-clock limit that progress notifications don't extend, and ignores values below 1000. That distinction now lives in the mcp module, EN and AR. PR #312 is superseded by this change.

Improved

mcp: distinguish the server startup timeout from the per-server tool-execution timeout

MCP_TIMEOUT sets the server startup/connection timeout at launch. Tool execution has a separate cap: a `timeout` field in milliseconds on a server's `.mcp.json` entry (e.g. "timeout": 600000 for ten minutes) limits how long any single tool call may run, overrides MCP_TOOL_TIMEOUT for that server only, is a hard wall-clock limit that progress notifications don't extend, and ignores values below 1000. Added to the mcp module.

Fixed

mcp: reject the imprecise MCP_TIMEOUT re-wording from audit PR #312

Audit PR #312 wanted to relabel MCP_TIMEOUT as 'a per-server startup timeout, not a general per-server timeout'. The docs call it the 'MCP server startup timeout' — a launch-time environment variable, not a per-server field — so the awkward clause was dropped in favor of the accurate startup-vs-tool-execution split.

Arabic

Arabic parity for the MCP timeout distinction

The Arabic mcp module mirrors the startup-timeout (MCP_TIMEOUT) versus tool-execution-timeout (per-server `timeout` field / MCP_TOOL_TIMEOUT) split, matching the English change.

v1.24.10 · Jun 26, 2026

Document claude plugin prune accurately, reject the auto:N removal (consolidates audit PRs #308–#310)

Today's pass reviewed three auto-generated audit PRs (#308 mcp, #309 plugins, #310 workflows) against the official Claude Code docs and shipped only what held up. (1) PR #309 (plugins) is partly correct and was incorporated with a fix: the plugins reference (code.claude.com/docs/en/plugins-reference) confirms claude plugin details shows a component inventory grouped as Skills, Agents, Hooks, MCP servers, and LSP servers plus a projected per-session token cost, so that enhancement was kept. But #309 described claude plugin prune as removing 'orphaned artifacts left behind by uninstalled plugins', which the docs contradict — prune removes auto-installed plugin *dependencies* no longer required by any installed plugin (aliased autoremove, requires v2.1.121+), and directly-installed plugins are never touched. The corrected wording landed in the plugins module, the reference cheatsheet (new entry), and the feature catalog, EN and AR. (2) PR #308 (mcp) was rejected as a regression: it removed the ENABLE_TOOL_SEARCH=auto:N variant, but the MCP reference (code.claude.com/docs/en/mcp, 'Configure tool search') documents auto:N verbatim — 'Threshold mode with a custom percentage, where N is 0-100. For example, auto:5 for 5%.' The mcp module and quiz were left unchanged. (3) PR #310 (workflows) was an empty no-op (the quiz was already sound) and was closed. PRs #308, #309, and #310 are superseded by this consolidated change.

Improved

plugins: document claude plugin prune accurately + the plugin details inventory (PR #309)

claude plugin prune (new in v2.1.121, aliased autoremove) removes auto-installed plugin dependencies that no other installed plugin still requires — directly-installed plugins are never touched, and 'uninstall <plugin> --prune' does both in one step. claude plugin details now lists the component inventory grouped as Skills, Agents, Hooks, MCP servers, and LSP servers with a projected per-session token cost. Added to the plugins module, the reference cheatsheet, and the feature catalog, EN and AR.

Fixed

mcp: keep ENABLE_TOOL_SEARCH=auto:N (rejected audit PR #308)

An audit PR removed the auto:N variant of ENABLE_TOOL_SEARCH. The MCP reference documents it verbatim — 'auto:N: Threshold mode with a custom percentage, where N is 0-100' (e.g. auto:5 for 5%) — so the variant stays. The mcp module and quiz were left unchanged.

Arabic

Arabic parity for the plugin prune / details updates

The Arabic plugins module mirrors the corrected claude plugin prune description and the expanded claude plugin details inventory, matching the English changes.

v1.24.9 · Jun 25, 2026

Clarify /code-review is the renamed /simplify, keep Console in the account list (consolidates audit PRs #304–#306)

Today's pass reviewed three auto-generated audit PRs (#304 getting-started, #305 mcp, #306 slash-commands) against the official Claude Code docs and shipped only what held up. (1) PR #306 (slash-commands) is correct and applied: the '(new in v2.1.147)' phrasing implied /code-review was a brand-new command, but the changelog records /simplify being renamed to /code-review in v2.1.147, so the module and quiz now describe it as the bundled skill formerly called /simplify. (2) PR #304 (getting-started) was a regression and rejected: it dropped 'Console' from the account list, but the install doc (code.claude.com/docs/en/install) states verbatim 'Claude Code requires a Pro, Max, Team, Enterprise, or Console account.' We kept Console and only adopted the clearer 'requires' verb. (3) PR #305 (mcp) was rejected entirely: it removed 'claude mcp add-from-claude-desktop' and 'claude mcp serve' — both documented in the MCP reference (code.claude.com/docs/en/mcp, the 'Import MCP servers from Claude Desktop' and 'Use Claude Code as an MCP server' sections) — and changed the startup-retry version from v2.1.121 to v2.1.187, but the docs date the startup retry behavior to v2.1.121 (v2.1.187 is the separate 5-minute remote-tool idle timeout). The mcp module was left unchanged. EN + AR parity. PRs #304, #305, and #306 are superseded by this consolidated change.

Improved

slash-commands: /code-review is the renamed /simplify, not a brand-new command (PR #306)

The '(new in v2.1.147)' tag implied /code-review was new; the changelog records /simplify being renamed to /code-review in v2.1.147. The module and quiz now describe /code-review as the bundled skill formerly called /simplify, in EN and AR.

Fixed

getting-started: keep Console in the account requirement list (corrects rejected audit PR #304)

An audit PR dropped 'Console' from the supported account list. The install doc states 'Claude Code requires a Pro, Max, Team, Enterprise, or Console account' — Console stays. We adopted the docs' clearer 'requires … account' phrasing while keeping all five account types.

mcp: keep 'claude mcp serve' / 'add-from-claude-desktop' and the v2.1.121 startup-retry version (rejected audit PR #305)

An audit PR removed two documented commands and re-dated the startup-retry behavior to v2.1.187. The MCP reference documents both 'claude mcp add-from-claude-desktop' and 'claude mcp serve', and dates the up-to-three startup retries on transient errors to v2.1.121 (v2.1.187 is the unrelated 5-minute remote-tool idle timeout). The original mcp content was correct and was kept unchanged.

Arabic

Arabic parity for the /code-review and account-list updates

The Arabic slash-commands module and quiz mirror the /code-review-formerly-/simplify clarification, and the Arabic getting-started module keeps Console in the account list with the 'requires' phrasing.

v1.24.8 · Jun 24, 2026

Correct the /fewer-permission-prompts command name and the subagent priority order (consolidates audit PRs #300–#302)

Today's pass consolidated three auto-generated audit PRs (#300 advanced-features, #301 slash-commands, #302 subagents), verified each against the official Claude Code docs, and shipped the two that held up. (1) v1.24.5 had 'renamed' the permission-prompts command from /fewer-permission-prompts to /less-permission-prompts, but the official command — per the v2.1.105–v2.1.113 release notes (code.claude.com/docs/en/whats-new/2026-w16) and the live skill — is /fewer-permission-prompts. The wrong name is reverted everywhere it leaked: the slash-commands and skills modules, the reference cheatsheet, and the feature catalog (entry id + name), EN and AR. (2) PR #302's subagent-priority fix (managed > CLI flag > project > user > plugin, with built-ins excluded from the name-override system) was verified against the features-overview docs and applied. PR #300 proposed moving the ultracode trigger rename from v2.1.160 to v2.1.154: the GitHub CHANGELOG.md does file that line under v2.1.154, but the official workflows docs (code.claude.com/docs/en/workflows) state 'Before v2.1.160 the literal trigger keyword was workflow' and separately require v2.1.154+ for the feature — the docs are this project's source of truth, so the rename stays v2.1.160 and #300 was not applied. PRs #300, #301, and #302 are superseded by this consolidated change.

Fixed

slash-commands: the command is /fewer-permission-prompts, not /less-permission-prompts (corrects v1.24.5)

v1.24.5 renamed the command the wrong way round. The official name — per the v2.1.105–v2.1.113 release notes and the live /fewer-permission-prompts skill — is /fewer-permission-prompts. Reverted across the slash-commands and skills modules, the reference cheatsheet, and the feature catalog (entry id and name), so search and every surface now show the correct command.

subagents: priority is managed > CLI flag > project > user > plugin (PR #302)

The subagent definition priority no longer lists 'built-in' as a priority level. Per the features-overview docs, built-in subagents are always available and are not part of the name-override priority system, which runs managed > CLI flag > project > user > plugin.

workflows: ultracode trigger rename stays v2.1.160 (rejected audit PR #300)

An audit proposed moving the rename from v2.1.160 to v2.1.154, citing the GitHub CHANGELOG.md. The official workflows docs (code.claude.com/docs/en/workflows) state 'Before v2.1.160 the literal trigger keyword was workflow' and separately note workflows require v2.1.154+ — so v2.1.160 is the documented rename version and the existing content was kept unchanged.

Arabic

Arabic parity for the command-name and priority fixes

The Arabic slash-commands, skills, and subagents modules, plus the Arabic feature catalog and reference cheatsheet, mirror the /fewer-permission-prompts revert and the subagent-priority correction.

v1.24.7 · Jun 23, 2026

Correct MCP tool search: it IS enabled by default — auto is only the 10% threshold mode (rejected audit PR #298)

An audit PR (#298) tried to rewrite the MCP module to claim tool search is off until you set ENABLE_TOOL_SEARCH=auto, and flipped quiz q6's answer to match. The official tool search reference (code.claude.com/docs/en/agent-sdk/tool-search) says the opposite: tool search is enabled by default — with ENABLE_TOOL_SEARCH unset, definitions are deferred and discovered on demand. It's only off by default on Vertex AI or a non-first-party ANTHROPIC_BASE_URL. The ENABLE_TOOL_SEARCH=auto value is a separate threshold mode that loads everything upfront unless definitions exceed 10% of the context window. PR #298 was a regression and is closed/superseded. This release keeps the correct default, adds the full ENABLE_TOOL_SEARCH value table (true/false/auto/auto:N) to the module, and reframes quiz q6 to ask specifically about auto mode so the 10% threshold is attributed correctly. EN + AR parity.

Improved

mcp: document the full ENABLE_TOOL_SEARCH value table

The MCP module now spells out the override values from the docs: true forces tool search always on, false loads every definition upfront on every turn, and auto (or auto:N) activates tool search only when tool definitions exceed 10% (or N%) of the context window.

Fixed

mcp: tool search is enabled by default — reject audit PR #298

An audit PR claimed tool search only works after setting ENABLE_TOOL_SEARCH=auto and that the default loads every MCP definition upfront. The official tool search reference states tool search is enabled by default (definitions deferred and discovered on demand), off by default only on Vertex AI or non-first-party ANTHROPIC_BASE_URL proxies. The original content was correct; PR #298 was a regression and is closed.

mcp quiz: q6 reframed to scope the 10% threshold to auto mode

Quiz q6 previously framed the 10% threshold as automatic default behavior. Per the docs, the 10% threshold is specifically the ENABLE_TOOL_SEARCH=auto mode — under the default (unset), tool search is already on regardless of size. The question now asks what auto does when definitions cross 10%, with explanations corrected to match.

Arabic

Arabic parity for the MCP tool search correction

The Arabic MCP module and quiz get the same correction: tool search on by default, the full ENABLE_TOOL_SEARCH value table, and q6 reframed around auto mode.

v1.24.6 · Jun 22, 2026

Add practical memory guidance (issue #293), fix the claude plugin tag version, and reject the subagents effort 'max' removal

Today's coverage pass consolidated three open PRs into one release. PR #294 (issue #293 — a reader asked for practical 'why does this matter' context) added an 'In practice' callout to the memory module explaining when to reach for project memory vs. user memory vs. CLAUDE.local.md. PR #295 fixed a version annotation in the plugins module: claude plugin tag was attributed to v2.1.121, but the official changelog shows v2.1.118 introduced claude plugin tag and v2.1.121 introduced the separate claude plugin prune command, so the tag annotation is now v2.1.118. PR #296 was rejected and closed: it removed max from the subagents effort values claiming the changelog dropped it in v2.1.72, but the official sub-agents reference lists effort options verbatim as low, medium, high, xhigh, max — so max stays. All changes applied in EN and AR; PRs #294, #295, and #296 are superseded by this consolidated change.

Improved

memory: practical guidance on which memory to use (issue #293)

A reader said the memory hierarchy was confusing without context on why it matters. The Memory Hierarchy section now has an 'In practice' callout: use project memory for what a teammate needs to understand the codebase (setup, testing, architecture), user memory for how you personally like to work, and CLAUDE.local.md for entries that only matter to you.

Fixed

plugins: claude plugin tag is v2.1.118, not v2.1.121

The plugins module attributed claude plugin tag to v2.1.121. The official changelog shows v2.1.118 added claude plugin tag (release git tags with version validation) and v2.1.121 added the separate claude plugin prune command, so the annotation now reads v2.1.118.

subagents: effort keeps max (rejected audit PR #296)

An audit PR removed max from the subagents effort values, claiming v2.1.72 dropped it. The official sub-agents reference lists the effort options verbatim as low, medium, high, xhigh, max, so the existing content is correct and max was kept.

Arabic

Arabic parity for all three changes

The Arabic memory module gets the same 'In practice' callout, the Arabic plugins module gets the v2.1.118 fix for claude plugin tag, and the Arabic subagents module keeps max in its effort values.

v1.24.5 · Jun 21, 2026

Finish the /less-permission-prompts rename across the catalog and cheatsheet; reject the repeat skills-budget PR

Today's coverage pass merged the slash-commands rename (PR #291: /fewer-permission-prompts → /less-permission-prompts, verified against the official changelog, which added /less-permission-prompts in v2.1.112) and then closed the parity gaps that PR left behind — the feature catalog and reference cheatsheet still listed the old /fewer-permission-prompts name in both English and Arabic, so search and the catalog now surface the correct command. Separately, the auto-generated PR #290 was closed: it re-proposed the already-rejected #288 change (skills budget 1% → 2%) and the official /en/skills docs state verbatim 'The budget scales at 1% of the model's context window', with 0.02 = 2% given there only as the example for raising the budget — so the 1% content stands. Applied in EN and AR.

Fixed

slash-commands: /less-permission-prompts rename completed everywhere

The command is now /less-permission-prompts across the slash-commands module (PR #291), the feature catalog, and the reference cheatsheet. The catalog and cheatsheet had been missed by PR #291 and still showed the old /fewer-permission-prompts name, so the command search index now matches the official spelling. Verified against the changelog (added in v2.1.112).

skills: budget stays at 1% (rejected audit PR #290)

PR #290 repeated the already-rejected #288 proposal to change the skill-description budget from 1% to 2%. The official /en/skills docs state 'The budget scales at 1% of the model's context window' and give 0.02 = 2% only as the example for raising it via skillListingBudgetFraction, so the existing 1% content is correct and was kept.

Arabic

Arabic parity for the command rename

The Arabic feature catalog and reference cheatsheet now use /less-permission-prompts, matching the English content and the slash-commands module.

v1.24.4 · Jun 19, 2026

Fact-check: keep skills budget at 1% and the v2.1.160 ultracode rename; document the v2.1.178 Agent Teams change where it belongs

Today's coverage pass triaged three auto-generated audit PRs against the official Claude Code docs and changelog. Two were rejected as inaccurate. PR #288 wanted to change the skills module and quiz from '1% of the context window' to '2%', citing a changelog line that does not exist — the official skills docs state verbatim 'The budget scales at 1% of the model's context window', and the `0.02 = 2%` figure the audit latched onto is the example for raising the budget via skillListingBudgetFraction, not the default, so the 1% content stands. PR #286 wanted to reframe the dynamic-workflow trigger as 'two separate changes in v2.1.178, not a rename'; the changelog explicitly says 'Renamed the dynamic-workflow trigger keyword from workflow to ultracode' under v2.1.160, so it is a rename and the existing v2.1.160 wording is correct and was kept. The one accurate finding shared by #286 and #287 — that v2.1.178 removed the TeamCreate and TeamDelete tools — was applied to the subagents module, which already documents Agent Teams and is the feature catalog's assigned home for it, instead of duplicating a new paragraph into advanced-features and commands as the audit PRs proposed. Applied in EN and AR; PRs #286, #287, and #288 are superseded by this consolidated change.

Fixed

subagents: Agent Teams reflects the v2.1.178 tool removal

The existing Agent Teams paragraph now notes that v2.1.178 removed the TeamCreate and TeamDelete tools — with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 set, every session already has one implicit team, so teammates are spawned directly through the Agent tool's name parameter with no setup step and cleanup happens automatically on session exit. Verified verbatim against the changelog.

skills: budget stays at 1% (rejected audit PR #288)

The skills module and quiz keep '1% of the context window' as the default skill-description budget. The official skills docs say 1% verbatim; the 0.02 = 2% value the audit cited is the example for raising the budget with skillListingBudgetFraction, not the default, and the claimed changelog line does not exist.

advanced-features: ultracode stays a v2.1.160 rename (rejected audit PR #286)

The dynamic-workflow paragraph keeps its accurate wording: the trigger keyword was renamed from workflow to ultracode in v2.1.160. The changelog says 'Renamed the dynamic-workflow trigger keyword from workflow to ultracode', so the audit's 'two separate changes in v2.1.178, not a rename' reframing was incorrect and was not applied.

Arabic

Arabic parity for the Agent Teams update

The Arabic subagents module mirrors the v2.1.178 Agent Teams change (TeamCreate/TeamDelete removed, implicit team per session, spawn via the Agent tool's name parameter, automatic cleanup on session exit).

v1.24.3 · Jun 18, 2026

Fact-check: hooks count is exactly 30, and Auto Mode's block thresholds (3 consecutive / 20 total) now appear in the module

Today's coverage pass consolidated two auto-generated audit PRs (#284 hooks, #283 advanced-features) into one release after verifying both against the official docs, and added the version bump + changelog entry that each PR was missing. The hooks docs list exactly 30 hook events, so the module's imprecise '30+ hook events' is now '30 hook events'. The permission-modes docs confirm verbatim that 'If the classifier blocks an action 3 times in a row or 20 times total, auto mode pauses and Claude Code resumes prompting. These thresholds are not configurable' — the advanced-features module described Auto Mode's classifier precedence but never stated these thresholds, which left the existing quiz q2 (asking for the exact numbers) unanswerable from the module alone. Both fixes are applied in EN and AR; the duplicate PRs #283 and #284 are superseded by this consolidated change.

Fixed

hooks: exact count of 30 hook events

The hooks module said Claude Code 'supports 30+ hook events'; the official hooks docs enumerate exactly 30, so the prose now states '30 hook events' for precision.

advanced-features: Auto Mode block thresholds documented

Added the Auto Mode fallback thresholds (3 consecutive blocks or 20 total blocks pause auto mode and resume prompting; not configurable) to the classifier-precedence paragraph, matching the permission-modes docs and making the existing quiz q2 answerable from the module.

Arabic

Arabic parity for both fact-checks

The Arabic hooks and advanced-features modules mirror both changes — '30 hook event' and the Auto Mode block-threshold sentence.

v1.24.2 · Jun 17, 2026

Fact-check: fix the getting-started quiz's Console answer — Console logs in via browser, not 'API key authentication'

Today's coverage pass triaged auto-generated audit PR #281, which correctly flagged that the getting-started quiz q3 answer (which plans include Claude Code) omitted Console, but rewrote the explanation to claim 'Console uses API key authentication rather than a subscription'. The official setup and quickstart docs contradict that wording: Console is one of the supported account types (Pro, Max, Team, Enterprise, Console), it's API access billed from pre-paid credits, and for all of these account types you sign in through the browser — an API key is a separate, optional credential path, not the defining trait of a Console login. Because q3 asks specifically about subscription plans, this release supersedes #281 by keeping the four subscription plans as the answer and reframing the explanation so the Console is named accurately as a non-subscription option (pre-paid API access, same browser sign-in) rather than mislabeled. Applied in EN and AR.

Fixed

getting-started quiz: accurate Console wording

Quiz q3 asks 'Which subscription plans include Claude Code access?', so the correct answer stays the four subscription plans (Pro, Max, Team, Enterprise) and the explanation now frames the Anthropic Console accurately as a non-subscription option — API access billed from pre-paid credits, with the same browser sign-in — instead of PR #281's inaccurate 'Console uses API key authentication rather than a subscription' framing. Cloud providers (Bedrock, Vertex AI) are noted too.

Arabic

Arabic parity for the Console answer fix

The Arabic getting-started quiz q3 mirrors the corrected wording: the four subscription plans remain the answer, and the Console is described as a non-subscription option (pre-paid API access, same browser sign-in).

v1.24.1 · Jun 16, 2026

Fact-check: xhigh and max effort levels still exist — reject audit PRs that would have deleted them

Today's coverage pass triaged eight auto-generated audit PRs against the official docs. Four were verified accurate and merged: #275 (MCP_TIMEOUT startup-timeout env var), #276 (managed settings have the highest precedence and cannot be overridden by command-line arguments), #273 (sandboxed Bash runs on macOS/Linux/WSL2 but not native Windows; `/effort ultracode` is a slash command — not a `--ultracode` flag — that sends xhigh), and #279 (CLAUDE_CODE_FORK_SUBAGENT=1 makes forked subagents inherit the full conversation and runs every spawn in the background, replacing a fabricated 'process isolation on Bedrock/Vertex' claim). Three were rejected and closed: #274 (hooks), #277 (skills), and #278 (slash-commands) all assumed the `xhigh` and `max` effort levels were removed, but the model-config docs confirm both still exist (Opus 4.8/4.7 and Fable 5 support low/medium/high/xhigh/max) — merging them would have deleted valid levels and made the site less accurate. Separately, this release corrects one genuine leftover inaccuracy the audit surfaced: the skills quiz and reference cheat sheet described `${CLAUDE_EFFORT}` / `CLAUDE_EFFORT` as resolving to an unverifiable 'ultra — the stored value for ultracode' level. That value is not in the docs, so it has been removed, leaving the verified list low/medium/high/xhigh/max. Applied in EN and AR.

Fixed

Skills quiz: removed an unverifiable ${CLAUDE_EFFORT} value

Quiz q6 described `${CLAUDE_EFFORT}` as resolving to 'low, medium, high, xhigh, max, or ultra — the stored value for ultracode'. The docs do not define an 'ultra' effort value for this variable, so the explanation now lists the verified levels low/medium/high/xhigh/max.

Reference cheat sheet: corrected the CLAUDE_EFFORT description

The `CLAUDE_EFFORT` environment-variable entry no longer claims it can resolve to 'ultra for ultracode', matching the feature catalog's accurate list of low/medium/high/xhigh/max.

Arabic

Arabic parity for the effort-level fix

The Arabic skills quiz q6 mirrors the corrected `${CLAUDE_EFFORT}` level list (low/medium/high/xhigh/max).

v1.24.0 · Jun 14, 2026

Full-surface coverage for /cd, --safe-mode, and the new model/footer/bundled-skills settings

Today's audit PRs (#268 advanced-features, #269 project-setup, #270 slash-commands quiz) added several v2.1.169+ features to the module prose, all verified against the official changelog and settings docs: the `/cd` command, `--safe-mode` / `CLAUDE_CODE_SAFE_MODE`, `CLAUDE_CODE_DISABLE_BUNDLED_SKILLS` / `disableBundledSkills`, `enforceAvailableModels` (v2.1.175), and `footerLinksRegexes` (v2.1.176), plus a settings-precedence correction (local overrides project) and a fix to the /simplify→/code-review rename direction in the slash-commands quiz. This release carries those new features across the rest of the surfaces so search and the reference tools catch them: the terminal simulator now knows `/cd` (and lists it in `/help`), the reference cheat sheet documents `/cd`, `--safe-mode`, the two bundled-skills toggles, and the model/footer settings, and the feature catalog adds `/cd` and `--safe-mode`. Applied in EN and AR.

Added

/cd in the terminal simulator, cheat sheet, and catalog

The terminal playground simulates `/cd <directory>` (moving the session without breaking the prompt cache) and lists it in `/help`; the reference cheat sheet and feature catalog both gained a `/cd` entry.

--safe-mode and CLAUDE_CODE_SAFE_MODE reference coverage

The cheat sheet documents the `--safe-mode` flag and `CLAUDE_CODE_SAFE_MODE` env var (start with all customizations disabled for troubleshooting), and the feature catalog adds a `--safe-mode` flag entry.

Bundled-skills and model/footer settings in the cheat sheet

Added `CLAUDE_CODE_DISABLE_BUNDLED_SKILLS` / `disableBundledSkills`, plus the `enforceAvailableModels` (v2.1.175) and `footerLinksRegexes` (v2.1.176) managed settings, to the reference cheat sheet's env-vars and config-options sections.

Arabic

Arabic parity for the new coverage

The Arabic terminal commands, cheat sheet (slash commands + CLI flags), and feature catalog mirror the `/cd` and `--safe-mode` additions.

v1.23.7 · Jun 13, 2026

Fact-check: MCP reconnection + channel version requirement, and remove a duplicate MCP quiz question

Verified MCP connection-resilience and channels details against the official MCP and channels docs, and fixed a structural duplicate in the MCP quiz. (1) The MCP module's reconnection paragraph now covers SSE servers alongside HTTP and adds the v2.1.121 behavior that initial connections at startup are retried up to three times on transient errors (5xx, connection refused, timeout) — matching the docs' Automatic reconnection section. (2) The Channels section now notes the v2.1.80 minimum version, confirmed by the channels doc's research-preview note. (3) The MCP quiz had two near-identical questions both testing `alwaysLoad` (old q6 and q8); the redundant one is removed and questions are renumbered to a clean q1–q9, which also brings the Arabic quiz to exact parity (it previously stopped at a stray q10). (4) The feature catalog's Channels entry incorrectly listed Slack as a channel — channels are Telegram, Discord, and iMessage; Slack is a separate integration. Note: an auto-generated audit PR proposed dropping the 'research preview' label from Auto Mode, but the official permission-modes doc still labels Auto Mode a research preview, so that change was rejected and the module left unchanged. Applied in EN and AR. Consolidates and supersedes auto-generated audit PRs #266 (which introduced a duplicate Arabic quiz question) and #265 (the unsupported Auto Mode change).

Fixed

MCP reconnection now covers SSE servers and startup retries

The MCP module states that HTTP or SSE servers reconnect mid-session with exponential backoff (up to five attempts), and that as of v2.1.121 the initial connection at startup is retried up to three times on transient errors such as a 5xx response, connection refused, or timeout.

Channels note the v2.1.80 minimum version

The Channels section now states that the Telegram, Discord, and iMessage channel plugins require Claude Code v2.1.80 or later, matching the official channels documentation.

Removed a duplicate MCP quiz question

The MCP quiz had two near-identical questions both testing the `alwaysLoad` config option; the redundant one is removed and the remaining questions renumbered to q1–q9.

Corrected the Channels feature-catalog entry

The catalog described channels as 'Telegram, Slack, and other platforms', and the `channelsEnabled` managed setting likewise listed 'Telegram, Slack'; both now correctly list the Telegram, Discord, and iMessage channel plugins, and the feature entry notes the research-preview / v2.1.80 requirement. Slack is a separate integration, not a channel.

Arabic

Arabic parity for the MCP fixes

The Arabic MCP module mirrors the SSE/startup-retry and v2.1.80 channel updates, the Arabic MCP quiz is renumbered to a matching q1–q9, and the Arabic feature catalog's Channels entry is corrected.

v1.23.6 · Jun 12, 2026

Fact-check: ExitWorktree isn't available to isolated subagents, and worktree.baseRef defaults to 'fresh'

Two factual corrections verified against the official tools reference and worktrees docs. (1) The Subagents module claimed an agent running with `isolation: worktree` can call the `ExitWorktree` tool to leave its worktree early. The tools reference says the opposite: `ExitWorktree` is explicitly not available to subagents that already run in their own working directory. The misleading sentence is replaced with accurate facts — Claude locks the worktree while the agent runs so cleanup can't remove it, and isolated worktrees branch from the repository's default branch unless `worktree.baseRef` is set to `head`. (2) The Advanced Features module listed `head` as the default for `worktree.baseRef`, but the docs make `fresh` (branch from `origin/HEAD` for a clean tree) the default; this also realigns the module with its own quiz and the reference cheatsheet, which already said `fresh`. Applied in EN and AR. Consolidates and supersedes auto-generated audit PR #263, which only reworded the inaccurate ExitWorktree claim instead of correcting it.

Fixed

Corrected the ExitWorktree availability claim for isolated subagents

The Subagents module no longer says `isolation: worktree` agents can use `ExitWorktree` to leave their worktree early — the tools reference states `ExitWorktree` is not available to subagents that run in their own working directory. The passage now covers worktree locking during the run and the `worktree.baseRef` base-branch behavior instead.

Fixed the worktree.baseRef default in Advanced Features

The module now lists `fresh` (branch from the remote default for a clean tree) as the default for `worktree.baseRef`, with `head` as the opt-in for branching from local HEAD — matching the official docs, the module quiz, and the reference cheatsheet.

Arabic

Arabic parity for both worktree fixes

The Arabic Subagents and Advanced Features pages mirror the ExitWorktree and baseRef corrections.

v1.23.5 · Jun 11, 2026

Fact-check: drop the non-existent deniedPlugins setting from the Plugins module

The Plugins module listed `deniedPlugins` as one of the managed-policy settings that control which plugins and marketplaces are allowed organization-wide. No such setting exists in the official docs — the real managed-policy controls are `enabledPlugins`, `extraKnownMarketplaces`, `strictKnownMarketplaces`, and `blockedMarketplaces`. Verified against the plugins reference and plugin-marketplaces pages. The plugins quiz had the same fiction in a distractor (and an explanation that asserted `deniedPlugins` was a real allowlist mechanism); both have been rewritten around the real `blockedMarketplaces` blocklist. Applied in EN and AR. Consolidates and supersedes an auto-generated audit PR that fixed only the module markdown.

Fixed

Removed fictional deniedPlugins managed-policy setting

The Plugins module now lists only the managed-policy settings that exist in the official docs — `enabledPlugins`, `extraKnownMarketplaces`, `strictKnownMarketplaces`, and `blockedMarketplaces` — instead of the non-existent `deniedPlugins`.

Plugins quiz distractor corrected

The team-disable quiz question no longer presents `deniedPlugins` as a real setting; the distractor and its explanation now turn on the real `blockedMarketplaces` managed-policy blocklist.

Arabic

Arabic parity for the deniedPlugins fix

The Arabic Plugins module and quiz mirror the English correction, dropping `deniedPlugins` for the real managed-policy settings.

v1.23.4 · Jun 10, 2026

Clarify settings precedence wording in the Project Setup module

Tightens the settings precedence explanation in the Project Setup module so the override direction is unambiguous: project settings are overridden by local settings, and only managed settings and command-line arguments override local. Verified against the official settings docs, whose precedence list (managed > command-line > local > project > user) matches the module. The Arabic page gets the same clarification plus a terminology fix — the managed layer is now consistently called 'الإعدادات المُدارة' instead of switching to 'سياسة المنظمة' mid-paragraph. Consolidates and supersedes an earlier auto-generated audit PR covering the same lines.

Fixed

Settings precedence wording made unambiguous

The Project Setup module now states plainly that project settings are overridden by local settings, and that only managed settings and command-line arguments override local — matching the official precedence order (managed > command-line > local > project > user).

Arabic

Arabic parity + managed-settings terminology consistency

The Arabic Project Setup page mirrors the precedence clarification and now uses 'الإعدادات المُدارة' consistently for the managed layer instead of switching to 'سياسة المنظمة'.

v1.23.3 · Jun 9, 2026

Fact-check: /ultrareview free runs are a one-time allotment (no fixed expiry date)

Two fact-check fixes verified against the official docs. The Workflows module described /ultrareview's 3 Pro/Max free runs as expiring on a specific date (May 5, 2026); the docs say only that the three runs are a one-time allotment per account that does not refresh — no fixed expiry date — so the date is removed in both EN and AR. The slash-commands quiz q7 explanation is also tightened: it keeps the doc-accurate framing that /code-review was renamed from /simplify in v2.1.147 (consistent with the rest of the site), and the closing note now explains that from v2.1.154 /simplify is a separate cleanup-only review that applies fixes without hunting for bugs — use /code-review --fix for bug-finding with fixes applied. This also supersedes two earlier auto-generated audit PRs covering the same lines.

Fixed

/ultrareview free runs: no fixed May 5, 2026 expiry

The Workflows module no longer claims the 3 Pro/Max free /ultrareview runs expire on May 5, 2026. Per the official ultrareview docs, the three runs are a one-time allotment per account that does not refresh — there is no published expiry date. Corrected in EN and AR.

slash-commands quiz: /code-review vs /simplify wording aligned with docs

Quiz q7 keeps the doc-accurate 'renamed from /simplify in v2.1.147' framing (matching the commands quiz, reference cheatsheet, and templates), and its closing note now matches the docs: from v2.1.154 /simplify is a separate cleanup-only review that applies fixes without hunting for bugs, and /code-review --fix is the bug-finding-with-fixes path.

Arabic

Arabic parity for both fixes

The Arabic Workflows module and slash-commands quiz mirror the /ultrareview free-runs correction and the /code-review wording, with natural phrasing in place of an earlier mixed-script glitch.

v1.23.2 · Jun 8, 2026

Fact-check: skill description budget is 1% of the context window by default

Corrects the Skills module and quiz against the official skills docs. The total budget for skill descriptions is 1% of the model's context window by default — not 2%, which is only an example raised value. Two ways to raise it are now documented: the `skillListingBudgetFraction` setting (e.g. `0.02` = 2%) and the `SLASH_COMMAND_TOOL_CHAR_BUDGET` environment variable for a fixed character count. The diagnostic command is corrected too: `/doctor` (not `/context`) reports whether the budget is overflowing and which skills are being dropped from the listing. The 1,536-character per-entry cap is unchanged. Mirrored across EN and AR module pages and quizzes, with an Arabic tanween spelling fix (مثلًا).

Fixed

Skill description budget is ~1% of the context window by default

Skills module and quiz corrected from ~2% to ~1%, the documented default. The 2% figure is only an example of a raised budget, not the default. Raise it with the skillListingBudgetFraction setting or the SLASH_COMMAND_TOOL_CHAR_BUDGET environment variable. Verified against the official skills docs.

Use /doctor (not /context) to check the skill budget

The Skills module and quiz now point to /doctor to see whether the skill-description budget is overflowing and which skills are dropped from the listing, matching the official docs.

Arabic

Arabic parity and tanween fix

The Arabic Skills module and quiz mirror the 1%/budget corrections, and a tanween spelling fix (مثلاً → مثلًا) is applied in the budget example.

v1.23.1 · Jun 7, 2026

Fact-check: corrected /terminal-setup behavior in Getting Started

An audit pass flagged the Getting Started module's `/terminal-setup` description, which is now corrected against the official terminal-config docs. The command does not 'auto-configure notification support for Kitty, Ghostty, and Alacritty' — Kitty and Ghostty already get desktop notifications without any setup, and the command is not about notifications at all. What `/terminal-setup` actually does is write the Shift+Enter (newline) keybinding for terminals where it isn't native: VS Code, Cursor, Devin Desktop, Alacritty, and Zed. In VS Code, Cursor, and Devin Desktop it additionally turns off the integrated terminal's GPU acceleration (to prevent garbled text) and adjusts scroll sensitivity — an accurate detail an earlier auto-fix had removed and that is now restored and made precise. Notification guidance is corrected too: desktop notifications work by default only in Ghostty, Kitty, and iTerm2; elsewhere set `preferredNotifChannel` to `"terminal_bell"` or add a Notification hook. The feature-catalog entry for `/terminal-setup` was updated to match. Three lower-quality auto-generated audit PRs that only injected self-referential 'confirmed by docs' notes into the learning content were closed without merging, since the underlying claims were already accurate.

Fixed

/terminal-setup no longer described as a notification configurator

Getting Started now explains that `/terminal-setup` writes the Shift+Enter keybinding for VS Code, Cursor, Devin Desktop, Alacritty, and Zed — not notification support for Kitty/Ghostty/Alacritty. Desktop notifications work by default in Ghostty, Kitty, and iTerm2; other terminals use `preferredNotifChannel: "terminal_bell"` or a Notification hook. Verified against the terminal-config docs page.

Restored the GPU-acceleration and scroll-sensitivity detail for VS Code forks

In VS Code, Cursor, and Devin Desktop, `/terminal-setup` turns off the integrated terminal's GPU acceleration (to prevent garbled text) and adjusts its scroll sensitivity for smoother fullscreen scrolling. This accurate detail was preserved and made precise rather than dropped. The feature-catalog description was sharpened to match.

Arabic

Arabic parity for the /terminal-setup correction

The Arabic Getting Started module and feature catalog mirror the English corrections with consistent phrasing for the Shift+Enter keybinding scope, the notification defaults, and the GPU-acceleration/scroll-sensitivity behavior.

v1.23.0 · Jun 6, 2026

Site-wide search with ⌘K command palette

Added a site-wide search experience: press ⌘K (or Ctrl+K) anywhere to open a command palette that searches across modules, slash commands, settings, and reference content, so you can jump straight to any topic without navigating the sidebar. This changelog entry backfills the v1.23.0 release, which shipped the search feature without a recorded entry.

Added

⌘K command palette for site-wide search

A new search island lets you open a command palette with ⌘K / Ctrl+K and find modules, commands, and reference material from any page, with keyboard navigation through results.

v1.22.8 · Jun 6, 2026

Fact-check sweep: /code-review effort levels, /simplify split, ultracode trigger, MAX_THINKING_TOKENS scope

Four audit findings verified against the official Claude Code docs and reflected across English and Arabic content. The /code-review effort range now includes `ultra` (which runs a deeper multi-agent review in the cloud), matching the documented `[low|medium|high|xhigh|max|ultra]` signature. /simplify is no longer described as a simple alias for /code-review — from v2.1.154 it runs a separate cleanup-only review that applies fixes without hunting for bugs. The dynamic workflow trigger keyword is now `ultracode` (renamed from `workflow` in v2.1.160; natural-language requests still work) across the workflows module, quiz, reference cheatsheet, and terminal simulation. The advanced-features module clarifies that `MAX_THINKING_TOKENS=0` only disables thinking on Opus 4.6 and Sonnet 4.6 — on Opus 4.7 and later, adaptive reasoning is always used and the variable does not apply. The `/install-github-app` blurb in workflows drops the unverified 'sandboxed environment' claim. The proposed `DISABLE_UPDATES` removal was investigated and rejected — the setup docs do document `DISABLE_UPDATES` as the way to block all update paths including manual updates, so the original module text stands.

Fixed

/code-review documents the ultra effort level

Commands module, slash-commands module, quizzes, reference cheatsheet, and terminal simulation now list the full documented effort range (low/medium/high/xhigh/max/ultra). `/code-review ultra` runs a deeper multi-agent review in the cloud — the same one previously surfaced as `/ultrareview`.

/simplify is no longer described as an alias for /code-review

From v2.1.154 /simplify runs a separate cleanup-only review that applies fixes without hunting for bugs. The commands module, slash-commands module, both quizzes, reference cheatsheet, templates, terminal-steps, and terminal simulation all drop the 'still works as an alias' framing and now explain the v2.1.154 split, with /code-review as the bug-finding tool.

Dynamic workflow trigger keyword renamed to ultracode

The workflows module, workflows quiz (Q9), reference cheatsheet /workflows entry, and terminal simulation now describe the trigger as `ultracode` instead of `workflow`. The rename landed in v2.1.160; asking for a workflow in your own words still works. Verified against the workflows docs page.

MAX_THINKING_TOKENS=0 scoped to Opus 4.6 and Sonnet 4.6

Advanced-features module clarifies that `MAX_THINKING_TOKENS=0` only disables thinking on Opus 4.6 and Sonnet 4.6. On Opus 4.7 and later, adaptive reasoning is always used and the variable has no effect. Verified against the model-config docs page.

/install-github-app: drop unverified sandboxed-environment claim

The workflows module no longer states that `@claude` mentions run in a sandboxed environment — the github-actions docs say `runs-on: ubuntu-latest` and 'Your code stays on GitHub's runners' but do not use the 'sandboxed environment' framing.

Arabic

Arabic parity for all five changes

Arabic versions of the commands, slash-commands, workflows, and advanced-features modules, plus the Arabic quizzes, reference cheatsheet, and terminal simulation all mirror the EN updates with consistent phrasing for the effort-range extension, the /simplify split, the ultracode trigger rename, and the MAX_THINKING_TOKENS scoping.

v1.22.7 · Jun 5, 2026

v2.1.162 fact-check: claude agents --json field names and waitingFor

Two doc-coverage updates verified against the official Claude Code docs. The `claude agents --json` field list in the subagents module, terminal simulation, templates, quiz, reference cheatsheet, and feature catalog is corrected to match the documented schema — `pid`, `cwd`, `kind`, `startedAt`, plus `sessionId`, `name`, and `status` when set — replacing the older `id`/`state`/`project`/`last_activity` names that no longer match the docs. The new `waitingFor` field (added in v2.1.162) is documented as the way to tell a session blocked on a permission prompt apart from one waiting for typed input, with a jq example that routes only permission-prompt sessions to `claude respawn`. The advanced-features environment-variable section also adds `OTEL_RESOURCE_ATTRIBUTES`, the supported way to attach team, department, or cost-center labels to every metric datapoint and event for multi-team OTEL backends, with the `OTEL_METRICS_INCLUDE_RESOURCE_ATTRIBUTES=false` cardinality escape hatch.

Added

waitingFor field disambiguates what a waiting session needs

When `status` is `waiting`, the new `waitingFor` field (v2.1.162) says exactly what the session is blocked on — `permission prompt` or `input needed`. The subagents module, templates, terminal simulation, and reference cheatsheet now include a jq example that wakes only permission-prompt sessions with `claude respawn`, so a boot script can route those two cases to different handlers.

OTEL_RESOURCE_ATTRIBUTES env var documented

Advanced-features module now documents `OTEL_RESOURCE_ATTRIBUTES` as the supported way to attach team, department, or cost-center labels to every metric datapoint and event. Formatting rules (comma-separated, no spaces, percent-encode special characters) and the `OTEL_METRICS_INCLUDE_RESOURCE_ATTRIBUTES=false` cardinality escape hatch are called out. Built-in attributes like `user.id` and `session.id` always win on key collision.

Fixed

claude agents --json field names match the docs

Subagents module, terminal simulation, templates, quiz Q9 explanation, reference cheatsheet, and feature catalog now list the documented `pid`, `cwd`, `kind`, `startedAt`, `sessionId`, `name`, and `status` fields — replacing the older `id`/`state`/`project`/`last_activity` names. All jq examples are updated from `.state` to `.status` and from `.id` to `.sessionId` so they actually parse the live output.

Arabic

Arabic parity for all three changes

Arabic subagents module, advanced-features module, terminal simulation, templates, quiz, reference cheatsheet, and feature catalog all mirror the field-name correction, the `waitingFor` addition, and the `OTEL_RESOURCE_ATTRIBUTES` env var, with consistent Arabic phrasing for the OTLP resource block and the cardinality escape hatch.

v1.22.6 · Jun 4, 2026

v2.1.162 fact-check: Windsurf renamed to Devin Desktop

One coverage update verified against the official Claude Code v2.1.162 changelog and the VS Code extension docs page. Windsurf has been renamed to Devin Desktop across `/ide`, `/terminal-setup`, and `/scroll-speed` since v2.1.162, and the IDE integrations doc page now lists VS Code forks as 'Devin Desktop or Kiro' instead of Windsurf. The getting-started module and its quiz are updated to match — keeping the historical Windsurf name as a 'formerly known as' reference so older content searches still resolve, and adding Kiro as the second confirmed VS Code fork.

Added

Kiro listed as a supported VS Code fork

The official VS Code extension docs page now states the extension installs in 'other VS Code forks like Devin Desktop or Kiro'. The getting-started module and Q5 quiz explanation in the getting-started quiz both add Kiro alongside Cursor and Devin Desktop so learners see the full set of VS Code forks where the Claude Code extension is supported.

Fixed

Windsurf is now Devin Desktop in the Claude Code UI

Getting-started module no longer presents Windsurf as a current VS Code fork name — it now describes Cursor, Devin Desktop (renamed from Windsurf in v2.1.162), and Kiro as the VS Code forks that support the Claude Code VS Code extension and the integrated terminal. The paragraph also notes that `/ide` and `/scroll-speed` use the new Devin Desktop label, on top of the existing `/terminal-setup` auto-configuration.

Arabic

Arabic parity for the Devin Desktop rename and Kiro addition

The Arabic getting-started module and Arabic getting-started quiz mirror the rename — Cursor وDevin Desktop (الاسم الجديد لـ Windsurf من v2.1.162) وKiro — with consistent phrasing for the `/ide`, `/terminal-setup`, and `/scroll-speed` label change.

v1.22.5 · Jun 3, 2026

Auto Mode on Bedrock/Vertex/Foundry + workflows availability fix

Two doc-coverage updates verified against the official Claude Code docs. Auto Mode availability is now documented for Amazon Bedrock, Google Cloud Vertex AI, and Microsoft Foundry — gated behind `CLAUDE_CODE_ENABLE_AUTO_MODE=1` since v2.1.158, with only Opus 4.7 and Opus 4.8 supported on those providers, and `permissions.disableAutoMode: "disable"` as the admin override. The workflows module's `/ultrareview` paragraph is corrected to state plainly that dynamic workflows are available on Bedrock, Vertex AI, and Foundry on v2.1.154+, dropping the previous 'may be restricted' hedge that no longer matches the docs.

Added

Auto Mode availability on Bedrock, Vertex AI, and Foundry

Advanced-features module now documents Auto Mode platform availability: on the Anthropic API it's on by default once your account meets the model and admin requirements; on Bedrock, Vertex AI, and Foundry (v2.1.158+) it's gated behind `CLAUDE_CODE_ENABLE_AUTO_MODE=1` and only Opus 4.7 and Opus 4.8 are supported, while Sonnet 4.5, Opus 4.5, Haiku, and Claude 3 are not. The `permissions.disableAutoMode: "disable"` admin override is called out as the way to lock the mode off in managed settings.

Fixed

Workflows module: drop the unsupported `/ultrareview` restriction hedge

The /ultrareview paragraph used to caveat that workflows generally work on Bedrock, Vertex AI, and Foundry while `/ultrareview` specifically might be restricted. The official workflows page now states plainly that dynamic workflows are available on all paid plans on Bedrock, Vertex AI, and Foundry with Claude Code v2.1.154+, so the hedge is removed in favor of the confirmed availability.

Arabic

Arabic parity for both Auto Mode and workflows updates

Both changes are mirrored in the Arabic advanced-features and workflows modules with consistent phrasing for platform availability, the `CLAUDE_CODE_ENABLE_AUTO_MODE` opt-in, and the model restriction to Opus 4.7/4.8 on third-party providers.

v1.22.4 · Jun 2, 2026

v2.1.160 fact-check: ultracode rename and OPUS_4_6 override removal

Three audit findings against the v2.1.160 changelog, applied across module docs, quizzes, templates, and the feature catalog. The dynamic-workflow trigger keyword was renamed from `workflow` to `ultracode` — `/effort ultracode` now activates dynamic workflows, and asking for one in natural language still works. CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE was removed and is a no-op — all references in module prose, templates, the feature catalog, and the commands module's fast-mode section were cleaned up. /ultrareview's version attribution is corrected to v2.1.111 introduction (updated in v1.24.31 from the earlier v2.1.86 attribution, per the official CHANGELOG).

Fixed

Dynamic-workflow trigger renamed to `ultracode`

Advanced-features and commands modules now document the v2.1.160 rename of the trigger keyword from `workflow` to `ultracode`. The literal `workflow` keyword no longer triggers a run, but a natural-language request still works, and `/effort ultracode` activates dynamic workflows.

CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE removed (no-op)

Removed all instructions to set this env var: from the commands module fast-mode section, the advanced-features environment-variable section and templates, and the feature catalog. Quiz Q23 in advanced-features now teaches that the variable was removed in v2.1.160 with no replacement.

/ultrareview introduced in v2.1.111

Workflows module now reflects the official CHANGELOG — /ultrareview has been available since Claude Code v2.1.111, instead of being marked only as new in v2.1.112. (This entry originally read v2.1.86; corrected in v1.24.31.)

Arabic

Arabic parity across all three audit fixes

Every change is mirrored in the Arabic modules (advanced-features, commands, workflows), Arabic templates, Arabic feature catalog, and Arabic quizzes, with Arabic phrasing for the `workflow`/`ultracode` distinction clarified after CodeRabbit review.

v1.22.3 · Jun 1, 2026

Fast mode now covers Opus 4.8; project-setup quiz hierarchy fix

Updates the Fast Mode section in the commands module to match the current docs — fast mode supports Opus 4.8 (default since v2.1.154), 4.7, and 4.6, with Opus 4.6 fast mode deprecated and being removed about 30 days after the Opus 4.8 launch. Also adds Claude Platform on AWS and the VS Code extension to the list of places fast mode is not available, and notes the rate-limit pool is shared across all three Opus versions. Q4 of the project-setup quiz now states the settings precedence correctly: project settings override user settings, but local settings, managed policy, and command-line arguments override project.

Fixed

Fast mode covers Opus 4.8, 4.7, and 4.6

Commands module no longer pins fast mode to Opus 4.6 alone. Opus 4.8 is the fast mode default in v2.1.154+, and the CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE=1 env var is documented for pinning back to 4.6 while it remains supported. The Opus 4.6 fast mode deprecation timeline is called out.

Fast mode platform exclusions are complete

Commands module now lists all platforms where fast mode is unavailable — Bedrock, Vertex AI, Foundry, Claude Platform on AWS — and notes it is not supported in the VS Code extension. The rate-limit pool is shared across Opus 4.8, 4.7, and 4.6.

Project-setup quiz Q4 precedence explanation

Project-setup quiz Q4 option B explanation was inverted: settings.local.json (not project settings) overrides project. The corrected explanation now reads: project settings override user settings, but they are overridden by local settings, managed policy, and command-line arguments — matching the official settings hierarchy.

Arabic

Arabic parity for fast mode and project-setup quiz

Every change is mirrored in the Arabic commands module and the Arabic project-setup quiz, with consistent terminology for deprecation and platform exclusions.

v1.22.2 · May 31, 2026

Plugin manifests: monitors and themes nest under experimental

Updates plugin manifest guidance to match the current Claude Code schema — monitors and themes should now be declared under the experimental key in plugin.json. Top-level placement still works but claude plugin validate warns, and a future release will require the nested form. Three other audit findings (effort levels, hook env var name) were verified against the official docs and skipped — the original module text was correct.

Fixed

Plugin monitors nest under experimental

Plugins module now shows monitors declared under experimental.monitors in plugin.json, with a note that top-level still works but claude plugin validate warns. Feature catalog entry updated to match.

Project setup mentions monitors/themes are experimental

Project-setup module now tells learners that monitors and themes are experimental plugin manifest keys and should be nested under experimental: {}.

Arabic

Arabic parity for plugin manifest guidance

Mirrored in the Arabic plugins and project-setup modules plus the AR feature catalog, with cleaner Arabic phrasing for the new project-setup paragraph.

v1.22.1 · May 30, 2026

Audit fact-check pass: docs and quizzes across seven modules

Applies seven targeted audit findings against the official Claude Code docs and changelog — covering getting-started, memory, project-setup, skills, slash-commands, subagents, and workflows. Each fix is mirrored in the matching module page and quiz across EN and AR, and the cross-module link to subagent configuration from the memory module is now a real link.

Fixed

IDE extensions: Cursor and Windsurf are VS Code forks

Getting-started module now describes Cursor and Windsurf as VS Code forks that reuse the VS Code extension and integrated terminal, with /terminal-setup auto-configuring GPU acceleration and scroll sensitivity. Quiz updated to match.

Subagents have their own auto memory

Memory module now notes that subagents can maintain their own auto memory, with a link back to the subagents module for configuration details.

DISABLE_UPDATES vs DISABLE_AUTOUPDATER

Project-setup module now distinguishes DISABLE_UPDATES=1 (blocks all update paths, including manual claude update) from DISABLE_AUTOUPDATER (suppresses package-manager update notifications only).

Skill description budget is ~2% of the context window

Skills module and quiz updated from the older ~1% figure to the current ~2% budget, with SLASH_COMMAND_TOOL_CHAR_BUDGET callable to raise the cap. All q3 option explanations now agree.

/simplify and /code-review behavior

Slash-commands module clarifies that /code-review is a bundled skill that reports findings, /code-review --fix applies them to the working tree, and /simplify now invokes /code-review (report only) — the old cleanup-and-fix /simplify behavior was removed, but /simplify still works as an alias.

CLAUDE_CODE_FORK_SUBAGENT scope

Subagents module and quiz now state that forked subagents work in interactive sessions, non-interactive mode, the Agent SDK, and on external builds — dropping the inaccurate 'interactive mode only' framing.

/ultrareview platform availability

Workflows module no longer claims /ultrareview is unavailable on Bedrock, Vertex AI, or Foundry. Learners are pointed to the official docs to confirm, since the workflows feature itself works on those platforms.

Arabic

Arabic parity for all fixes

Every fix is mirrored in the Arabic module pages and quizzes, including the cross-module link in memory.md and the consistent 2% phrasing across all skills q3 explanations.

v1.22.0 · May 29, 2026

Dynamic workflows and the full bundled-skills set

Adds the workflows module's Dynamic Workflows section (/workflows orchestration, the /deep-research bundled workflow, and /effort ultracode), and expands the skills module to list every bundled skill. New quiz questions, terminal-simulation commands, feature-catalog entries, and reference-cheatsheet rows back the content. Full EN/AR parity.

Fixed

Clarified the channels research-preview wording

MCP module now says the Telegram, Discord, and iMessage channel plugins are 'included in' the research preview, matching the official docs phrasing.

Content

Added dynamic workflows

Workflows module now covers dynamic workflows (v2.1.154+) — orchestrating dozens to hundreds of subagents from a script Claude writes, the bundled /deep-research workflow, /effort ultracode, saving a run as a /command, and disabling via /config or CLAUDE_CODE_DISABLE_WORKFLOWS=1. Mirrored in the feature catalog, reference cheatsheet, and terminal simulation (/workflows, /deep-research).

Expanded the built-in skills list

Skills module now lists the full set of bundled skills available in every session — /code-review, /batch, /debug, /loop, and /claude-api — alongside the /run, /verify, and /run-skill-generator trio (v2.1.145+). Added /claude-api to the terminal simulation.

New quiz coverage

Added a workflows quiz question on how to start a dynamic workflow (the 'workflow' keyword or /effort ultracode, not /workflows) and a skills quiz question on bundled skills. Corrected the skills effort-variable answer to include the ultra value.

Arabic

Arabic parity for all changes

Translated the dynamic workflows section, bundled-skills table, new quiz questions, feature-catalog entries, and cheatsheet rows into Arabic.

v1.21.1 · May 28, 2026

Effort level corrections, cloud code review, and PowerShell clarification

Corrects the reasoning effort levels to include xhigh across modules, documents the deep cloud code review (/code-review ultra, alias /ultrareview), clarifies the PowerShell tool shell setting on Linux/macOS, and fixes the Arabic permission-mode cycle order. Full EN/AR parity.

Fixed

Corrected reasoning effort levels

Hooks and subagents modules now list the full effort set — low, medium, high, xhigh, max, auto — matching official docs. xhigh was added for Opus 4.7, sitting between high and max.

Clarified the PowerShell tool shell setting

Skills module now notes that enabling the PowerShell tool with CLAUDE_CODE_USE_POWERSHELL_TOOL=1 on Linux and macOS also requires pwsh on your PATH.

Fixed Arabic permission-mode cycle order

Commands module (Arabic) now shows Shift+Tab cycling default → acceptEdits → plan, matching the English module and official docs.

Content

Documented the cloud code review

Slash commands module, feature catalog, reference cheatsheet, and terminal simulation now cover /code-review ultra (alias /ultrareview) — a deep, multi-agent code review run in a cloud sandbox.

Arabic

Localized feature catalog categories

Arabic feature catalog now uses Arabic category labels for the new entries, and fenced code blocks carry language tags.

v1.21.0 · May 27, 2026

Session recap, command history search, push notifications, and auto mode hard deny

Adds coverage for session recap (/recap), Ctrl+R reverse command history search, mobile push notifications via Remote Control, auto mode hard_deny rules and four-tier precedence, and new slash commands (/fewer-permission-prompts, /tui, /focus, /undo). Also adds continueOnBlock and terminalSequence to hooks documentation.

Content

Added session recap and command history

Commands module now covers automatic session recaps when returning to the terminal, /recap on-demand summaries, and Ctrl+R reverse history search with Ctrl+S scope cycling.

Added mobile push notifications

Workflows module now documents push notifications via Remote Control — Claude sends phone alerts when tasks finish or need input.

Expanded auto mode configuration

Advanced features module now documents hard_deny rules (unconditional blocks), four-tier precedence, and claude auto-mode defaults/config/critique CLI subcommands.

Added new slash commands

Slash commands module now includes /recap, /fewer-permission-prompts, /tui, /focus, and /undo (alias for /rewind).

Added hook configuration options

Hooks module now documents continueOnBlock (feed rejection back to Claude instead of ending the turn) and terminalSequence (emit notifications without a terminal).

Arabic

Full EN/AR parity for all changes

All new content mirrored in Arabic modules, quizzes, feature catalog, and reference cheatsheet.

v1.20.0 · May 26, 2026

Output styles, channels, computer use, and expanded routines

Adds coverage for output styles (Default, Proactive, Explanatory, Learning, custom), MCP channels (Telegram, Discord, iMessage push into sessions), computer use (GUI control on macOS), and expands routines documentation with API triggers, GitHub triggers, and cloud management.

Content

Added output styles section

Commands module now covers built-in output styles (Default, Proactive, Explanatory, Learning) and custom output style creation with Markdown files and keep-coding-instructions frontmatter.

Added channels section

MCP module now documents channels — MCP servers that push events (Telegram, Discord, iMessage) into running sessions. Covers --channels flag, pairing, allowlists, and enterprise controls.

Added computer use section

Advanced features module now covers the computer-use MCP server for GUI control on macOS. Includes enabling, permissions, per-app approval, and safety features.

Expanded routines documentation

Workflows module now fully documents routines: API triggers, GitHub triggers, web UI at claude.ai/code/routines, connectors, one-off scheduled runs, and /schedule list/update/run CLI management.

Arabic

Full EN/AR parity for all changes

All new content mirrored in Arabic modules, quizzes, feature catalog, and reference cheatsheet.

v1.19.0 · May 25, 2026

Bundled skills, auto-update accuracy, and installation coverage

Adds /run, /verify, /run-skill-generator bundled skills and skillOverrides to the skills module. Fixes inaccurate auto-update guidance and npm deprecation claims by cross-referencing official docs. Adds Linux package managers (apt/dnf/apk), claude doctor, and release channel details across getting-started and project-setup.

Fixed

Fixed auto-update documentation accuracy

Project-setup module now correctly documents that Homebrew/WinGet can opt in to auto-updates via CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE=1, adds autoUpdatesChannel setting, and DISABLE_AUTOUPDATER env var. Previous PR #195 incorrectly claimed the env var was unsupported.

Removed incorrect npm deprecation claim

Getting-started module, quiz, and installation tabs no longer describe npm as deprecated — the official docs list it as a supported alternative installation method.

Content

Added /run, /verify, /run-skill-generator bundled skills

Documents the three bundled skills for launching, verifying, and recording app build recipes. Added to both English and Arabic skills module.

Added skillOverrides setting

Documents the skillOverrides setting for controlling skill visibility from settings.json without editing SKILL.md frontmatter. Includes the /skills interactive menu workflow.

Added string substitution variables

Documents ${CLAUDE_SESSION_ID}, ${CLAUDE_EFFORT}, ${CLAUDE_SKILL_DIR}, and named arguments frontmatter in the skills module.

Added Linux package managers and claude doctor

Getting-started module now documents apt, dnf, and apk installation methods and the claude doctor verification command.

Arabic

Full EN/AR parity for all changes

All module text, quiz corrections, and tab content mirrored in Arabic.

v1.18.1 · May 24, 2026

Coverage gaps, audit fixes, and EN/AR alignment

Closes verified content gaps (updatedToolOutput, args exec form, --add-dir, --mcp-config), incorporates two audit findings (CLAUDE_CODE_FORK_SUBAGENT availability, /less-permission-prompts version), and aligns all changes across English and Arabic.

Fixed

Fixed CLAUDE_CODE_FORK_SUBAGENT availability and Arabic description

English corrected from 'interactive mode only' to 'interactive sessions, non-interactive mode, and the Agent SDK'. Arabic completely rewritten to match (was incorrectly described as external-builds-only).

#192

Corrected /less-permission-prompts version

Version corrected from v2.1.112 to v2.1.111 (confirmed via CHANGELOG) in both English and Arabic skills module.

#191

Content

Added PostToolUse updatedToolOutput documentation

PostToolUse hooks can replace tool output entirely via hookSpecificOutput.updatedToolOutput (works for all tools since v2.1.121). Quiz q8 tested it, but the module content was missing.

#106

Added --add-dir and --mcp-config CLI flags

--add-dir grants Read/Edit access to additional directories; --mcp-config loads MCP servers from external JSON for the current session. Both documented in subagents module and terminal simulator.

#171

Arabic

Added missing args exec form to Arabic hooks

The English hooks module documented the exec form (args array for shell-free process spawning) but Arabic was missing it entirely.

v1.18.0 · May 22, 2026

v2.1.146 coverage — /code-review bundled skill

Documents the new /code-review bundled slash command (formerly /simplify, which still works as an alias) — verified against the official Claude Code commands reference. Mirrored across English and Arabic module content, quizzes, the terminal simulator, templates, the feature catalog, and the reference cheatsheet.

Content

Added /code-review bundled slash command

Reviews the current diff for correctness bugs and reports findings without editing files. Accepts effort levels (low/medium/high/xhigh/max) and --comment to post inline GitHub PR comments. Renames /simplify, which still works as an alias.

#184

Arabic

Full Arabic parity for /code-review

Mirrored across Arabic module content, quizzes, terminal steps, terminal-commands.json, templates, the feature catalog, and the reference cheatsheet.

#184

v1.17.0 · May 20, 2026

v2.1.144 / v2.1.145 coverage — 5 verified features

Documents 5 features verified against the official Claude Code docs and CHANGELOG, mirrored across all content, quizzes, terminal steps, templates, the feature catalog, and the reference cheatsheet in both English and Arabic.

Content

Added claude agents --json for scripting

claude agents --json prints the session roster as a JSON array — id, state, name, project, last activity — for tmux-resurrect-style boot scripts, status bars, and session pickers.

#179

Added Stop/SubagentStop background_tasks and session_crons fields

Stop and SubagentStop hook inputs now include background_tasks (running background bash/subagents) and session_crons (queued scheduled tasks). A completion-gate hook can block until both arrays drain.

#179

Added /plugin Discover/Browse component preview

The /plugin Discover and Browse screens now show a plugin's commands, agents, skills, hooks, and MCP/LSP servers inline before installation.

#179

Added Read tool partial-view truncation

When a whole-file read exceeds the token limit, Read now returns a truncated first page with a PARTIAL view notice instead of a hard error. Claude paginates with offset/limit or narrows with grep.

#179

Renamed /extra-usage to /usage-credits

v2.1.144 renamed 'extra usage' to 'usage credits' across the CLI; /extra-usage still works as an alias. Catalog, cheatsheet, slash-commands module, fast-mode copy, and terminal sim updated.

#174

Arabic

Full Arabic parity for v2.1.144 + v2.1.145

All five features mirrored across Arabic module content, quizzes, terminal steps, templates, terminal-commands.json, feature catalog, and reference cheatsheet.

#174, #179

v1.16.0 · May 16, 2026

v2.1.143 coverage — plugin enable/disable and audit fixes

Documents 5 features from v2.1.143 verified against the official Claude Code docs. Also includes audit corrections for memory, project-setup, hooks, and plugins modules that landed alongside coverage work.

Fixed

Audit corrections across 4 modules

Fact-check fixes in memory, project-setup, hooks, and plugins modules from automated audit pipeline.

#176, #177, #178, #180, #181

Content

Added claude plugin enable/disable commands

Toggle installed plugins on or off without uninstalling. Accepts --scope (user/project/local) to control where the setting is stored.

#171

Added /plugin marketplace projected context cost

Plugin Discover/Browse screens now show projected token cost per session for each plugin.

#171

Added plugin details and plugin tag commands

claude plugin details <name> shows component inventory and token cost; claude plugin tag creates release git tags with version validation.

#171

v1.15.0 · May 16, 2026

Curated YAML changelog

Replaces the GitHub-driven changelog with a hand-curated YAML format. Each release now has a title, summary, and categorized entries with related issue links.

Improved

Migrated changelog to curated YAML format

Changelog data moved from GitHub API scraping to a structured YAML file (changelog.yaml) with per-release entries, categories, and issue references.

#170

v1.14.0 · May 15, 2026

v2.1.142 coverage — agents, permissions, identity, and plugins

Documents 4 features verified against the official Claude Code docs, mirrored across all content, quizzes, terminal steps, templates, and the feature catalog.

Content

Added agents --cwd directory-filtered Agent view

claude agents --cwd <path> filters the Agent view to only show agents running in that directory.

#168

Added --permission-mode flag with full accepted-modes list

Documents --permission-mode <mode> flag with the complete list of accepted permission modes.

#168

Added ANTHROPIC_WORKSPACE_ID workload identity federation

Documents ANTHROPIC_WORKSPACE_ID for Workload Identity Federation on cloud platforms.

#168

Added CLAUDE_CODE_PLUGIN_PREFER_HTTPS for CI plugin cloning

CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1 ensures plugins are cloned over HTTPS in CI environments.

#168

v1.13.0 · May 14, 2026

v2.1.138/140 env vars and sidebar visibility fix

Adds newly documented environment variables and fixes a longstanding sidebar visibility issue.

Improved

Brightened sidebar collapse toggle

Higher-contrast text in expanded state with full text-primary color and thicker chevron stroke when collapsed.

#162

Fixed

Fixed backwards CLAUDE_CODE_NATIVE_CURSOR description

Corrected the pre-existing backwards description for CLAUDE_CODE_NATIVE_CURSOR.

#164

Content

Added 3 publicly documented env vars from v2.1.138/140

CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE, CLAUDE_CODE_RESUME_PROMPT, and CLAUDE_CODE_ENABLE_FEEDBACK_SURVEY_FOR_OTEL across modules, feature catalog, quizzes, and templates.

#164

v1.12.1 · May 12, 2026

6 new features and full Arabic quiz parity

Adds module content for 6 verified features, 12 quiz questions, complete Arabic parity across all 7 modules, and a security note for plugin URLs.

Fixed

Added --plugin-url trust warning

Added a security note for --plugin-url in both English and Arabic plugins documentation.

#160

Content

Added 6 verified features across 5 modules

Gateway model discovery, alternate screen toggle, image pasting hint, --plugin-url flag, package manager auto-update, and SESSION_ID env var.

#160

Added 12 quiz questions across 6 modules

New quiz questions covering the 6 verified features added this release, with correct numbering throughout.

#160

Arabic

Complete Arabic quiz parity across all 7 modules

15 missing Arabic quiz questions added (getting-started q7-q8, hooks q9-q10, project-setup q6, advanced-features q13-q21), plus 4 terminal steps and 4 templates.

#160

v1.12.0 · May 10, 2026

v2.1.138/139 coverage — 7 verified features

Closes coverage gaps for 7 features verified against the official Claude Code documentation.

Content

Added 7 features from v2.1.138/139

Module content, quizzes, templates, and feature catalog entries for 7 newly verified Claude Code features.

#159

v1.11.0 · May 7, 2026

v2.1.128–133 coverage and #122 content

Closes coverage gaps across multiple module areas, informed by user feedback and audit findings.

Content

Added 5+ features from v2.1.128–133

Module content, quizzes, and templates for 5+ newly verified Claude Code features.

#142

v1.10.2 · May 6, 2026

Shift+Tab permission mode cycling fix

Corrects the cycling order for Shift+Tab in permission mode, which was broken in a prior release.

Fixed

Corrected Shift+Tab permission mode cycling order

Shift+Tab now correctly cycles through permission modes in the right order instead of skipping states.

#135

v1.10.1 · May 5, 2026

ultrareview --timeout template and catalog entry

Adds a new workflow template and feature catalog entry for running ultrareview with a timeout flag.

Added

New ultrareview --timeout template

Added a CI code review workflow template that runs ultrareview with --timeout for environments where long reviews are disruptive.

#121

v1.10.0 · May 5, 2026

v2.1.119–126 coverage — 7 verified features

Closes 7 coverage gaps for features verified against the official Claude Code documentation.

Content

Added 7 features from v2.1.119–126

Module content, quizzes, and templates for 7 newly verified Claude Code features.

#119

v1.9.0 · May 1, 2026

v2.1.118–123 coverage — 10 verified features

Closes 10 coverage gaps across commands, plugins, MCP, and advanced-features modules with content, quizzes, and templates.

Content

Added 10 features from v2.1.118–123

Full content, quiz questions, and templates for 10 verified features across commands, plugins, MCP, and advanced-features.

#114, #96

v1.8.0 · Apr 30, 2026

Beginner-friendly Getting Started module

Adds a beginner-friendly introduction and glossary to the Getting Started module in both English and Arabic.

Content

New beginner introduction and glossary

The Getting Started module now includes a step-by-step beginner guide and a glossary of terms for those new to Claude Code.

#95

v1.7.0 · Apr 29, 2026

Advisor Tool full coverage

Adds complete Advisor Tool coverage including a quiz question and terminal step in both English and Arabic.

Content

Added Advisor Tool quiz and terminal step

Full quiz question and terminal step coverage for the Advisor Tool in both English and Arabic.

#94

v1.6.0 · Apr 28, 2026

Module 0 — Getting Started complete

Completes the Getting Started module (Module 0) with install, auth, terminal, and IDE setup in both English and Arabic.

Content

Complete Getting Started module

Full Module 0 coverage for install, authentication, terminal, and IDE setup in English and Arabic.

#86

v1.5.0 · Apr 25, 2026

Advisor Tool description correction

Corrects the Advisor Tool description and removes references to undocumented environment variables.

Fixed

Corrected Advisor Tool description

Advisor Tool description is now accurate. Undocumented env vars have been removed from the feature catalog.

#84

v1.4.5 · Apr 21, 2026

Slash-commands audit and quiz consistency

Corrected a command that was documented but not built-in, fixed mismatched Arabic quiz questions, and replaced quiz auto-advance with a manual button.

Improved

Quiz no longer auto-advances after correct answer

Learners can read explanations before deciding to continue. A 'Next Question' button replaces the automatic advance.

#20

Fixed

Removed /allowed-tools from Configuration commands

/allowed-tools was listed as a built-in command but does not exist in Claude Code. Removed it from the slash-commands module.

#33

Fixed 5 mismatched Arabic quiz questions

Arabic quiz questions in memory, skills, and slash-commands modules now match their English counterparts.

#21

v1.4.4 · Apr 21, 2026

Effort max is session-only, not Opus-only

Corrects documentation that incorrectly stated the effort maximum was an Opus-only feature.

Fixed

Corrected effort max scoping

The effort maximum is session-wide, not Opus-only. Documentation corrected across 4 modules.

#74

v1.4.3 · Apr 20, 2026

sandbox.network.deniedDomains coverage

Adds quiz and template coverage for the sandbox.network.deniedDomains configuration option.

Content

Added sandbox.network.deniedDomains coverage

Documents sandbox.network.deniedDomains in advanced-features with quiz questions and templates.

#71

v1.4.2 · Apr 16, 2026

v2.1.105 coverage gaps

Closes coverage gaps for v2.1.105 features across commands, hooks, plugins, skills, and subagents modules.

Content

Added v2.1.105 coverage across 5 modules

Module content updates for commands, hooks, plugins, skills, and subagents covering newly verified Claude Code features.

#58

v1.4.1 · Apr 8, 2026

Skills module accuracy

Corrects the Arabic context budget and adds documentation for missing skill frontmatter fields.

Fixed

Corrected Arabic context budget figure

Skill description budget corrected from 2% / 16,000 to 1% / 8,000 characters.

#28

Content

Documented model and shell frontmatter fields

Added documentation for model and shell frontmatter fields in the skills module.

#28

v1.4.0 · Apr 4, 2026

Terminal, card download, and template fixes

Three UI-level fixes for the terminal simulator, card download experience, and code template display.

Fixed

/clear command clears the terminal

The /clear command in the terminal simulator now clears visible history instead of printing text.

#25

Card download shows error on failure

When html2canvas fails, a localized error message appears below the button instead of silently failing.

#25

Template copy button no longer overlaps text

Code template blocks push content below the copy button to prevent text rendering underneath it.

#25

v1.3.1 · Apr 3, 2026

New audit skills for content integrity

Launches audit-quiz and audit-terminal skills for automated content integrity checking across all modules.

Added

New audit-quiz skill

Automated skill for checking quiz data integrity, structural validity, and EN/AR consistency.

#23

New audit-terminal skill

Automated skill for cross-referencing module content against terminal-commands.json and terminal-steps.yaml files.

#23

New /allowed-tools command

Terminal simulator now supports /allowed-tools for managing permitted tools with add/remove and wildcard support.

#22

v1.3.2 · Apr 2, 2026

Arabic layout, keyboard navigation, and scoring fixes

Migrates to CSS logical properties, adds RTL-aware keyboard navigation, and corrects the self-assessment scoring range.

Fixed

Migrated to CSS logical properties

Replaced physical CSS properties with logical equivalents across 8 components for proper RTL support.

#18

RTL-aware keyboard navigation

Added RTL-aware arrow-key navigation to BuildTabs, QuizBlock, and InteractiveDiagram.

#18

Arabic self-assessment scoring corrected

Self-assessment scores now correctly cap at 20. Expert users are no longer misclassified as Beginner.

#18

Arabic

Feedback form mixed-script input support

Free-text fields use dir='auto' for mixed Arabic/English input. Email fields use dir='ltr'.

#18

v1.3.0 · Apr 2, 2026

GLM audit workflow and module accuracy

Adds an automated audit fact-checking workflow and corrects documentation in slash-commands and subagents modules.

Fixed

Corrected slash-commands and subagents documentation

Fixed command discovery, model aliases, effort options, diagnostics, and Agent Teams documentation.

#15

Content

GLM audit workflow for learning modules

Automated audit workflow with OpenCode agents, runner scripts, report templates, and tracker sync.

#15

v1.1.2 · Mar 31, 2026

Self-assessment scoring ranges fixed

Self-assessment now scores correctly up to 20 points with proportional level ranges.

Fixed

Self-assessment scores correctly up to 20 points

Score ranges are Beginner 0–6, Intermediate 7–14, Advanced 15–20. Expert users are no longer classified as Beginner.

#11

v1.1.0 · Mar 28, 2026

Public feedback system and navigation launch

Launches the public feedback tracker, changelog page, per-module Report an issue links, and navigation reorganization.

Added

Public feedback tracker

New /feedback page showing active feedback organized by status with item counts and a submission form.

#7

Changelog page for shipped items

New /changelog page showing what has been shipped and fixed, linked from the footer.

#7

Report an issue link on every learn page

Each module page has a link that opens the feedback form with the module name pre-filled.

#7

Improved

Navigation renamed for clarity

Build → Config Builder, Quick Reference → Cheat Sheet, Feature Catalog → Feature Index. Footer and sidebar reorganized.

#7