Jonathon's AI Wiki

What's New in Claude Code (Dixon / Anthropic, Code with Claude 2026)

17 min read

Source: What’s new in Claude Code (Anthropic / Dixon Dick — Member of Technical Staff, Claude Code team, Code with Claude 2026, May 7 2026 conference talk, YouTube IMZa42k6L6M; transcript captured locally via Whisper since YouTube has no captions)

Dixon (MTS, Claude Code team — works specifically on plugins and Claude Code on the web) steps back from the public changelog and tells the story of what shipped in the recent weeks. The frame: two themes. Developer experience — making Claude Code nicer to live in as users spend more of their day inside it. Autonomy — enabling Claude to do more while you’re away from the keyboard. The talk is Dixon’s “as a daily user of Claude Code, here is what we love” tour: remote control, flicker-free rendering, the redesigned Desktop GUI, auto mode, worktrees, auto memory, multi-agent code review, routines + /loop, and the new tool-search indirection layer. Closes by acknowledging that the team also shipped a wall of enterprise features (better Windows, cloud-provider setup, native installation, admin settings, plugin company-wide harness improvements) — too many to cover.

Key Takeaways

Theme 1 — Developer Experience

  • Remote control — start on your machine, pick up on your phone.

    • Type remote control in a session → Claude Code prints a link to a Claude Code on the web mirror of that exact session. Open it in a mobile browser; the same dev setup keeps running on your machine. Type on your phone, see it in your terminal; type in your terminal, see it in your phone.
    • Dixon’s favorite pattern: enable remote control on a long-running session that has accumulated context over multiple PRs. While running errands, ask that session to spin up a sub-agent and implement an idea — context already loaded, no fresh-session ramp-up.
    • Distinct from the keynote’s “iOS and Android Claude apps” announcement — same surface, different entry point. The CLI feature is what plugs the terminal into the web mirror.

  • Flicker-free rendering — full-screen mode virtualizes the terminal.

    • “Show of hands — how many of you have hit flickering?” The previous renderer appended to the terminal scrollback; one misalignment triggered a full repaint. The new full-screen mode virtualizes scrollback inside Claude Code’s TUI. Guarantees no flickering. Keeps memory flat even on very long sessions.
    • Toggle with /tui full-screen (tui = terminal UI). The Claude Code team has switched to this for the most part.
    • Bonus: full-screen mode makes terminal elements clickable — folded tool calls expand on a single click; “jump to bottom” handles long output without scroll-jacking; new-message indicator surfaces while you’re scrolled up reviewing.
    • Voice mode pairs with this naturally: /voice toggles it on/off, then hold the spacebar to dictate. Demoed live: “write me a file containing 10 jokes and another file containing 10 fun facts.”

  • Claude Code Desktop GUI — revamp.

    • Two design goals: (1) manage multiple sessions at once, (2) surface relevant context so you can work efficiently. “If you haven’t seen Claude Code Desktop in a while, a lot has changed.”
    • Sidebar: pin section + advanced filtering and grouping (e.g. group by project). Drag-and-drop session into split view.
    • Top-right session views: open the plan for the session, open a diff view with per-line comments, open the file tree view of the working directory with quick edits. All optional — “they’re not your default experience, just something you grab when you need them.”
    • Highlight + comment on any part of a transcript or diff; comments aggregate and Claude can resolve them later as a batch.
    • Experimental — “pin as chapter”: hover an assistant message, click the pin → the message becomes a renamed chapter title above the transcript. Pin two and you get a top-left table of contents for jumping around the session. Dixon: “If you want this to ship faster, just let Anthony Morris (Claude Code Desktop lead) know on X — he’ll probably ship it for you tomorrow.”

Theme 2 — Autonomy

Dixon’s framing: each autonomy feature came from the same place — “I had Claude do something long-running, and one small thing — a permission prompt, a branch conflict, a forgotten build command — would lead me to wonder Claude why’d you do that? when I came back to my laptop.” The next features make Claude do what you want when you step away.

  • Auto mode — a classifier replaces permission prompts.

    • “Show of hands, how many of you became tired of 1 1 1 1?” Audience laughs and waves.
    • Auto mode is a permission mode where Claude makes permission decisions on your behalf using a classifier. For each tool call that would otherwise hit a permission prompt, the classifier evaluates two things: is the action destructive? and does it look like prompt injection? If safe, the tool call runs. If not, Claude is blocked and the agent has to figure out what to do next.
    • Saves the team time at Anthropic and eliminates “I thought I started a long-running task — a permission prompt.” See W13 release digest for the launch and [[claude-ai/hooks|the PermissionDenied hook]] for the retry-on-block extension surface.

  • Worktrees — multiple Claudes that don’t step on each other.

    • “Worktrees are my favorite feature.”
    • Git worktrees pre-date Claude Code (a worktree creates a new branch and a copy of the repo files), but they have sharp edges. The Claude Code team smoothed them: a settings field declares files shared across worktrees (e.g. node_modules), so new worktrees inherit them rather than re-installing.
    • claude --worktree (or claude -w) starts a new session with a fresh worktree attached.
    • Claude can also create worktrees autonomously. Claude Code ships enter_worktree / exit_worktree tools — Claude decides whether to start implementing a feature in an isolated environment. “I’m being explicit in this demo, but you can put this prompt in your CLAUDE.md, you don’t have to be explicit. Claude will know what your intent is.” When Claude leaves the worktree, the harness cleans it up automatically.
    • Demo: three worktrees in parallel — color, border-radius slider, star shape — three independent feature branches running side-by-side off the same Excalidraw repo. Rendered the color worktree feature on localhost:3003; original Excalidraw still ran on the main checkout.

  • Auto memory — Claude accumulates knowledge across sessions.

    • “How many of you spend a lot of tokens on the same things over and over because you think Claude Code’s working on a blank slate?”
    • Auto memory lets Claude accumulate knowledge across your sessions automatically — key build commands, debugging insights, project preferences. Claude decides what’s worth remembering based on whether the information could be useful for a future conversation.
    • Mechanism: for every project, Claude manages a directory. Inside is a MEMORY.md index file that gets included in every conversation (just like CLAUDE.md) but is exclusively managed by Claude. The index links to other files in the same directory with more detail — same progressive disclosure pattern as skills.
    • Works for sub-agents too: in a custom sub-agent, say memory user or memory project to establish a memory directory.
    • Model dependency: “this feature wouldn’t be possible without recent breakthroughs in model development. Compared to Opus 4, Opus 4.7 and other recent models are more capable of managing memory as a set of files in a directory.” Connects directly to the Memory and Dreaming talk’s file-system memory model — and to the public Claude-plays-Pokemon improvement Anthropic has been showcasing. See also Rick Mulready’s operator framing of Memory 2.0 (auto-memory + auto-dream).

  • Code review — multi-phase, multi-agent, runs before you look at the PR.

    • Anthropic discovered a more effective code-review pattern: spin up a team of reviewers to look at independent aspects of a change, then verify the findings are actually worth reporting. Catches issues that would have taken hours, or been missed altogether.
    • Two delivery modes: (1) GitHub app for all your PRs automatically, (2) /ultrareview slash command for ad-hoc local runs. See Ultrareview deep-dive for pricing, sandbox model, and the “verified-findings-only” filter.
    • Stacks: between auto mode + worktrees + auto memory + code review, you have “fewer actions to approve, more agents safely working in parallel, sessions accumulating knowledge over time, and teams of Claude reviewing changes — all before you yourself look at each PR.”

  • Routines — automate the idea generation itself.

    • Routines (research preview) create Claude Code sessions that fire without your intervention. “We’ve talked about features that help agents work autonomously from idea to PR. Now we’re automating idea generation itself.”
    • Shape: configure once (prompt + repo + relevant connectors). Pick a trigger: cron schedule (hourly/daily), GitHub webhook event, or API endpoint you can hit. Claude runs without you.
    • Examples: triage GitHub issues daily, send digest to Slack via the Slack connector. Or run on every e-commerce sale — “you can have Claude be happy with you.”
    • Dixon’s own routine, running for a week: “scan the latest open public GitHub issues with the most reactions created since the day before, look only at issues with labels area-plugins and area-hooks, respond with a list of the top 10 issues sorted by reactions.” Daily report. “I don’t have to think about prompting Claude to launch these. And we can imagine other automation that ingests these reports and launches sub-agents to fix them.” See Routines deep-dive.

  • /loop and the cron-create tool — in-session scheduling.

    • /loop <interval> <prompt> — sets up automation inside a single Claude Code session. Demo: /loop 1m tell me a joke produces a stream of programmer jokes (“why programmers prefer dark mode — light attracts bugs”). Then stop the loop and Claude maps the natural language to the proper tool call to delete the cron.
    • Under the hood: Claude Code ships a cron-create tool (similar in shape to the enter_worktree / exit_worktree tool pair) — Claude can self-schedule at its discretion. Disable in settings if you don’t like it. See Claude Code scheduled tasks for the full /loop + Cron* tool surface.
    • Routines vs /loop: routines run remotely on Anthropic servers (your laptop can be closed); /loop runs locally inside the open session. Pick remote unless you need local resources.

  • Tool search tool — indirection layer for tool discovery.

    • “We have a tool search tool now. What it does is add a layer of indirection between you and the actual tool definition. So we can offer more tools at once without directly impacting your context.”
    • Same architectural move as MCP filter-out / /context pruning — pay token cost only for tools the model actually loads. Connects directly to the Expanding Toolkit talk’s “scaffolding moves into the model” thesis: tool routing was previously the user’s problem, now it’s Claude’s.

”Everything else” wall

Dixon flashes a slide of the changelog and says “take a picture, or just get a sense of the overwhelming number of features.” Specifically called out for enterprise:

  • Much better Windows support than months prior
  • Native cloud provider setup
  • Native installation (no bundled JS — see W16 release digest for the migration)
  • Admin settings management
  • Plugin features for company-wide harness improvements

How to keep up: follow Claude devs on X, read the weekly what’s-new digests in the Anthropic docs (W13 / W14 / W15 / W16 / W17 / W19 all in this wiki), or subscribe to the developer newsletter.

Recent Signals

[Reddit signal — r/ClaudeAI 2026-05-09]: r/ClaudeAI post 1t89g1j surfaces path-frontmatter rule files as an undocumented complement to auto memory’s directory pattern. Per the canonical Anthropic doc at memory#organize-rules-with-claude/rules/, CLAUDE.md can be split into multiple surgical rule files that load on demand when Claude touches a path matching the rule’s frontmatter — same priority as the main CLAUDE.md but progressively disclosed (sample implementation: milis92/nestjs-boilerplate). Pairs with the auto-memory section’s progressive-disclosure framing: rule files + MEMORY.md index together build a two-axis context system — path-conditional (rules) + conversation-conditional (memory).

Where it fits in the wiki

  • Sister talk to Lucas’ Expanding Toolkit and Mahes’ Memory and Dreaming — three Code with Claude 2026 deep-dives by Anthropic platform/research staff. Lucas covers the four agentic capabilities (tool use, context management, code execution, computer use); Mahes covers the Managed Agents memory + dreaming primitives; Dixon covers the Claude Code surface itself — the daily-driver experience plus the autonomy primitives layered on top. They compose into the keynote’s three-layer story (model → managed-agents → Claude Code).
  • Closes the GUI gap. The wiki has been deep on terminal Claude Code, CLI reference, hooks, channels, scheduled tasks — but the Claude Code Desktop redesign has only been mentioned in passing in W17. This talk is the canonical narrative for what the new Desktop GUI does (sidebar, split view, plan/diff/file-tree per-session views, comment + resolve, pin-as-chapter). The talk is now the reference doc for that surface.
  • Concrete operational examples. Dixon’s “long-running session + remote control + sub-agent dispatch” pattern, his “I run a daily routine for label-filtered GitHub issues” pattern, and his “three parallel worktrees for three feature branches” demo are all transferable templates. Add them to operator playbooks. Pairs with Karpathy techniques for Claude Code as the Anthropic-side companion.
  • Ratifies the Angela & Caitlin platform team interview’s claims. Dixon’s “memory works because Opus 4.7 can manage files in a directory” is a concrete instance of Caitlin’s “memory eval saw drastic per-harness performance differences.” The harness-and-model-are-pairing thesis from that interview shows up in the actual product surface here.
  • Reframes /loop and Routines. Both have wiki articles already ([[claude-ai/scheduled-tasks|/loop]], Routines) — this talk is the first end-to-end narrative of how the team uses them in daily practice (/loop for in-session automation, routines for fully unattended cloud runs, and the explicit “prefer remote — your laptop can be closed” recommendation).

Implementation

  • Tool/Service: Claude Code (CLI + Desktop + Web), all 2026 features.
  • Setup:
    • Remote control: type remote control inside a session, or run claude remote-control standalone — see CLI reference.
    • Full-screen / flicker-free: /tui full-screen (toggle) + /voice (voice mode toggle, hold spacebar to dictate). The classic renderer is still available — toggle back with /tui (default mode).
    • Worktrees: claude --worktree or claude -w for an explicit one; otherwise put intent in CLAUDE.md and Claude self-creates via enter_worktree / exit_worktree. Configure files-shared-across-worktrees in Claude Code settings (e.g. node_modules).
    • Auto memory: on by default for projects (Claude manages the memory directory + MEMORY.md). For sub-agents say memory user or memory project. Requires Opus 4.7+.
    • Code review: install the GitHub app for every-PR coverage, or run /ultrareview ad-hoc. See Ultrareview for pricing.
    • Routines: create from the Claude Code Desktop sidebar or claude.ai/code (kicks off remote on Anthropic servers; can also run locally on your desktop, but laptop must stay open). Configure prompt + repo + connectors + trigger (cron / GitHub event / API endpoint).
    • /loop: /loop <interval> <prompt> inside any session. Claude can also self-schedule via the cron-create tool — disable in settings if unwanted.
  • Cost: Auto memory is free in normal Claude Code billing (no separate quota called out). Routines run on Anthropic servers — same Claude tokens. Code review GitHub app + /ultrareview have their own pricing — see Ultrareview (Pro/Max: 3 free runs one-time, then 20 as extra usage). Worktrees / full-screen mode / remote control / voice mode / tool search are free harness features.
  • Integration notes: Auto mode uses a classifier — [[claude-ai/hooks|PermissionDenied hook returns retry: true]] to give Claude an explicit retry path when the classifier blocks. The cron-create tool, like the enter_worktree / exit_worktree pair, can be disabled per-tool in settings. Tool search adds a discovery layer between Claude and individual tools — large MCP-server portfolios benefit most. Remote control sessions inherit the running dev environment; phone input typed mid-task interleaves with terminal input on the same session.

Open Questions

  • Auto memory cost / size guardrails. The talk shows Claude managing files in a directory across sessions, but doesn’t quote a max-size guardrail or cost model. Does the entire memory directory get loaded into every conversation (à la CLAUDE.md), or is it lazy-loaded via Claude’s discretion? Progressive-disclosure framing suggests the latter, but the load-bearing limits aren’t spec’d here.
  • Worktree isolation depth. Is the --worktree setting purely a git-worktree wrapper, or does it also isolate environment variables, ports, language servers, etc.? The “files shared across worktrees” config implies file-level only — needs verification against the CLI reference’s worktree.baseRef and shared-files settings.
  • Auto-mode classifier specifics. Two-axis classifier (destructive + prompt-injection). What model backs it? Does it run on every tool call or only on tool calls that would otherwise prompt? How is “destructive” defined (filesystem write? net call? tool-by-tool list?)? See settings.autoMode.hard_deny from W19 for the unconditional-block escape hatch.
  • Pin-as-chapter persistence. Experimental feature. Are pinned chapters saved per-session and survive a session reload, or are they session-state only? Are they shareable when remote-controlling?
  • Tool search tool semantics. Talk introduces it but does not name the tool’s API surface. Is mcp_filter (W17 hook tooling) the same primitive, or is this a separate API the model invokes?
  • Routines vs Managed Agents boundary. Both run autonomously on Anthropic servers. The talk frames routines as “automating idea generation”; Managed Agents is “the general hosted-agent primitive.” When does a routine graduate to a managed agent? Is there a migration path?

Try It

  1. Watch the talk (YouTube IMZa42k6L6M) — Dixon’s three-worktree Excalidraw demo and the “pin as chapter → table of contents” sequence are the visceral hooks.
  2. Type remote control in your most context-rich session right now. Open the link on your phone. Bookmark it. Next time you’re away from your desk, ask the session to spin up a sub-agent — pre-loaded context, no fresh-session ramp.
  3. Toggle /tui full-screen and use Claude Code for a session. If you ever hit flicker before, it stops here. Click on a folded tool call to expand it (terminal + click, finally).
  4. Add a “files shared across worktrees” entry to your project’s Claude Code settings (e.g. node_modules, .venv), then run claude -w and ask Claude to implement a feature that needs those files. Verify the second worktree didn’t have to reinstall.
  5. Let Claude create a worktree on its own. Add to CLAUDE.md: “For any new feature, create a worktree to isolate the work.” Next session, ask for two unrelated features in one message — watch Claude split them via enter_worktree.
  6. Set a routine for a daily issue triage. Pattern after Dixon’s: “scan public GitHub issues with most reactions in the last 24 hours, filter by labels I own, return top 10.” Connect Slack to send the digest. Run for a week, then evaluate whether the digest beat your manual scan.
  7. Use /loop 5m /your-favorite-recurring-prompt for an in-session recurring task. Stop it with stop the loop and verify Claude maps the natural-language stop to the right CronDelete tool call.
  8. Use /ultrareview on a non-trivial PR before you read it yourself. Note which findings the multi-phase verification step kept and which it filtered. Contrast with /review.
  9. Open Claude Code Desktop. Group the sidebar by project, drag two sessions into split view, open the diff view on one and the file tree on the other. The new GUI rewards multi-session work — design your daily flow around it.
  10. Pin two assistant messages as chapters in a long session. Watch the table of contents appear top-left. Decide whether you want this — and if so, tell Anthony Morris on X (Dixon’s exact ask).

Graph View

Backlinks