OneRange

What's New in Claude Code for Developers

A short refresher on the latest Claude Code for Developers updates

What this course covers

The course runs across 7 topics, each one a short adaptive session rather than a recorded lecture. The tutor explains the idea, works an example, checks understanding, and adjusts the next step to the answer given.

  • Sessions now start in auto mode — What's different: New terminal and VS Code sessions now start in auto mode, where a safety check reviews each action, unless you have set a different default mode. Why it matters for your work: Claude asks you to approve far fewer steps, so work moves faster, while risky actions are still stopped or flagged. Try it (about 2 minutes): Start a new session and look at the mode shown by the prompt, then press Shift+Tab to cycle through the modes and back to auto. No access? Here's what you'd see: New terminal and VS Code sessions show auto mode in the prompt, and pressing Shift+Tab cycles through the modes.
  • Fast mode on the older Opus model is being retired — What's different: Fast mode for the previous Opus model was deprecated on October 30 and will stop working on November 30, with no automatic fallback; users must switch to the newest Opus model to keep the speedup. Why it matters for your work: Anyone who pinned the older Opus model with fast mode will start getting errors after the cutoff date. Try it (about 2 minutes): Run /model to see which model your session uses, and if it is the older Opus, switch to the newest Opus before turning fast mode on with /fast. No access? Here's what you'd see: After November 30, fast mode on the older Opus model will fail with errors, requiring a switch to the newest Opus model.
  • Block file edits outside your project folder — What's different: A new permission setting stops Claude from writing or editing any file outside the folders you are working in, in every mode. Why it matters for your work: It gives teams a simple guardrail so Claude cannot change files elsewhere on your computer, even in hands-off modes. Try it (about 2 minutes): Run /permissions to review your current rules, then ask your admin or check the permissions docs about turning on the setting that blocks writes outside working folders.
  • Guided setup teaches auto mode about your project — What's different: A new /auto-mode-setup command reads your project and recent sessions to teach the hands-off safety check what is normal in your environment. Why it matters for your work: The safety check blocks fewer harmless actions once it understands your tools and workflow. Try it (about 2 minutes): In a project folder, run /auto-mode-setup and read the rules it suggests before accepting them.
  • Long idle chats get summarized automatically — What's different: When a very long conversation sits idle, Claude Code now summarizes it in the background so your next message picks up from a short summary instead of reprocessing everything; this started in the terminal and came to VS Code and the desktop app's Code tab on October 30. Why it matters for your work: Coming back to a long session after a break is faster and uses less of your plan. Try it (about 2 minutes): Open the settings menu with /config, find the idle compaction row, and check whether it is on or off for you. No access? Here's what you'd see: In the settings menu opened with /config, learners see an idle compaction row indicating whether it is on or off.
  • Also new — - A new Opus model is now the default: A new Opus model is now the default for Pro and Team Standard plans. - Mods, plus a built-in "You should know" helper: Plugins called mods can now alter Claude Code, including a built-in helper to flag mistakes. - A new, faster Sonnet model: A new, faster, and lower-cost Sonnet model has been released. - Claude Code reads AGENTS.md files: Claude Code now reads AGENTS.md files for instructions when CLAUDE.md is missing. - Review edits one change at a time in VS Code: The VS Code proposed-change view now lets you accept or reject individual changes. - Your claude.ai skills and plugins sync to the terminal: Skills and plugins from your claude.ai account now sync to your terminal sessions. - Concise style for shorter replies: A new Concise output style makes Claude skip step-by-step narration in replies. - /diff now opens a live changes panel: The diff command now opens a live panel showing uncommitted changes as Claude edits. - Ask helper agents to work at a set effort level: You can now specify the effort level for Claude's helper sub-agents. - Get back a prompt you cleared by mistake: Pressing the Up arrow now restores a draft prompt cleared by Ctrl+C. - and 8 more: Open a terminal session in the desktop app; A new top-tier Fable model; Ultraplan was removed; The ultrathink keyword now means extra-high effort; Rewind no longer undoes sed edits; Connector permission rules now match exactly; Colored code blocks in VS Code replies; Code Review now has Quick, Standard and Deep levels
  • Try one on your own work — Pick the one main change from this course that is most useful to your job. Try it in your own Claude Code on a real task, then paste or describe what you got. The coach gives short, specific feedback. No access to the app or plan it needs? Describe how you would use it on a real task this week. That counts too. There is no score and no pass or fail: finishing this completes the course.

Skills you build

Results are measured against named skills in the OneRange taxonomy of more than 10,000 skills, so a manager sees proficiency per skill rather than a completion tick.

Who it is for

The material is pitched at intermediate level, and takes roughly 20 minutes at a typical pace. Because every session adapts, someone who already knows a topic moves through it quickly instead of sitting through an explanation they do not need.

It sits in the Tool: Claude track of the Vero AI Catalog, and can be assigned to one person, a team, or the whole company.

How it is delivered and assessed

Delivery is conversational and interactive. There is no video to sit through and no slide deck to click past.

Understanding is checked with a lab assessment, with a pass mark of 70%.

Administrators can copy this course into their own library and adapt it — edit the outline, change the duration, swap the assessment format, or ground it in internal documentation so answers cite the company's own source material.

Also in this track

Related

Frequently asked questions

How long does this course take?

It runs roughly 20 minutes at a typical pace. Because every session adapts, someone who already knows a topic moves through it quickly instead of sitting through an explanation they do not need.

How is it assigned to a team?

An administrator assigns it from the Vero dashboard to one person, a team, a department or the whole company, and sees progress and results per person and per skill.

Can we customise it with our own documents and terminology?

Yes. Administrators can copy this course into their own library and adapt it — edit the outline, change the duration, swap the assessment format, or ground it in internal documentation so answers cite the company's own source material.

Course code what-s-new-in-claude-code-for-developers-465b052a.