Skip to content
Datfx Labs Claude Guide

March 2026

Five changes shipped in March that are worth adopting now. This isn’t a full changelog — it’s the short list of things that will actually change how you work day-to-day.

Auto Mode

What it is: Shift+Tab cycles through permission modes. Auto mode adds a background safety classifier that reasons about each action before executing it — instead of just asking you to approve.

Workflow impact: If you’ve been staying in Default mode for safety, Auto mode is now the safer choice. Default mode asks you to approve actions, which means your approval becomes a rubber stamp over time. Auto mode actively classifies each action’s risk level and blocks unsafe ones even when you’re not watching. For long-running tasks, it’s more reliable than manual approval fatigue.

Try it:

Cycle to Auto mode with Shift+Tab twice (past accept-edits mode), or set it as default in your settings:

{
  "permissions": {
    "defaultMode": "auto"
  }
}

--worktree Flag

What it is: claude --worktree feature-name creates an isolated git worktree and branch in a single command, then opens Claude in that context.

Workflow impact: Parallel Claude sessions used to require three manual steps — git worktree add, cd into the worktree, then claude. Now it’s one command. If you’ve been avoiding parallel sessions because setup was tedious, this removes that friction entirely.

Try it:

Terminal window
claude --worktree feature-auth    # creates worktree + branch named feature-auth
claude --worktree                 # auto-names from timestamp

Each worktree is fully isolated — file changes in one session don’t affect another. See Advanced Techniques for parallel session patterns.

Computer Use (macOS)

What it is: Claude can open applications, click UI elements, and type — full macOS desktop control from the CLI.

Workflow impact: Automate anything that requires a mouse: UI testing, browser-based workflows, filling forms in apps with no API, or walking through a multi-step GUI process. Particularly useful for QA workflows where the test subject is a UI, not an API.

Try it:

Terminal window
claude --computer-use

macOS only. Requires granting accessibility permissions when prompted.

Caveat: Desktop-destructive actions are possible — closing apps, deleting files via GUI, submitting forms. Review carefully before enabling in unattended automation pipelines. Treat it like bypassPermissions for desktop actions.

Interactive Lessons (/powerup)

What it is: /powerup launches animated, interactive demos of Claude Code features directly inside the CLI.

Workflow impact: Better onboarding for new team members than pointing them at documentation. The demos are hands-on and self-paced, making feature discovery faster for people who joined after the features shipped.

Try it:

Open Claude Code and type:

/powerup

No installation or setup required. Works in any Claude Code session.

PowerShell Tool (Windows)

What it is: Claude Code now executes PowerShell natively on Windows instead of routing through bash-via-WSL.

Workflow impact: Windows users no longer need WSL installed to run automation scripts. PowerShell scripts work directly — file paths, environment variables, and Windows-specific commands all behave as expected. If you’ve been maintaining parallel bash and PowerShell versions of scripts just for Claude compatibility, you can drop the bash version.

Try it:

No setup required. When Claude Code detects Windows with PowerShell available, it uses PowerShell automatically for shell commands. Existing PowerShell scripts work without modification.