We break down Claude Code v2.1.157’s local .claude/skills workflow, where executable scripts can be loaded straight from a developer’s machine for instant tool creation and hot reloading. The conversation also digs into the security risks of committing custom plugins to source control, including the possibility of arbitrary code execution.

We dig into Claude Code’s new /code-review --fix workflow, which can edit files directly instead of just leaving comments, and the revamped /simplify pass for trimming dead code and redundant structure. The episode also covers safer usage tips, from keeping a clean git tree to reviewing diffs, plus the new skipLfs option for speeding up large repos.

We break down a critical credential leak in custom API gateways, where Claude Code mistakenly sent primary Anthropic OAuth credentials to the wrong place. The episode also covers faster git and GitHub plugin loading with skipLfs, plus new safeguards for subagent MCP configs to prevent privilege escalation.

This episode digs into the v2.1.132 Claude Code update, including a stdio MCP memory leak that could balloon long sessions past 10GB, plus the practical differences between stdio and HTTP transport. It also covers new session-aware Bash env vars, a terminal escape hatch for alternate screen mode, and a permission-mode bug that could quietly override your intent when resuming plan-mode sessions.

This episode breaks down how Claude Code v2.1.129 changes plugin loading with URL-based zip installs, moving plugins from local setup to a true distribution model. It also explores the new experimental themes and monitors fields, and the security tradeoffs that come with treating plugins like packaged software.

This episode breaks down a subtle Git behavior in Claude Code v2.1.128 where new worktrees now branch from local HEAD instead of origin/default-branch, preventing unpushed commits from being skipped. It also covers related reliability improvements, including OTEL isolation for subprocesses and better handling of parallel tool calls.

This episode explores how Claude Code’s `ultrareview` command uses exit codes, streamed output, and PR targeting to make AI review behave like a real CI check. It also digs into the multi-agent verification model, cost tradeoffs, and the network constraints teams need to consider before wiring it into GitHub Actions.

We break down Anthropic’s new xhigh effort level for Claude Code on Opus 4.7, why it now defaults for Max subscribers, and how the new slider and config flow make it easier to use.The discussion also covers when deeper reasoning is worth the extra latency and cost, plus how to spot the tasks where xhigh really pays off.

Claude Code now asks your configured ANTHROPIC_BASE_URL for /v1/models, so the model picker reflects the IDs your gateway actually exposes instead of a hardcoded Anthropic-only list. The episode breaks down why that matters for LiteLLM, Bedrock, and other proxies, plus the catch: the backend still has to return truthful model names or the client will pass them through verbatim.

We break down the new claude project purge command, which wipes stale transcripts, tasks, file history, and project config so broken project state can be reset cleanly. The episode also covers the expanded behavior of --dangerously-skip-permissions, the new direct OAuth code paste flow for login failures, and a subtle policy bug fix affecting Claude Code memory.