DEV Community

RAXXO Studios
RAXXO Studios

Posted on • Originally published at raxxo.shop

Claude Code Auto Mode and MCP Tools on Mobile: What Just Shipped

  • Claude Code Auto Mode intelligently approves file writes and terminal commands based on safety criteria, eliminating repetitive manual approval prompts during coding sessions.

  • Auto Mode safeguards still block destructive operations like force pushes and production config changes unless explicitly approved by the user.

  • MCP work tools (Figma, Canva, Amplitude) now function on Claude mobile app without additional setup, using existing desktop configurations and permissions.

  • Mobile MCP integration eliminates context switching by allowing designers and analysts to access tools and data directly from their phones.

Two updates from Anthropic this week that are worth paying attention to. One changes how you interact with Claude Code. The other brings your work tools to your phone.

Claude Code Auto Mode

If you've used Claude Code for any real project, you know the permission flow. Every file write, every bash command, you either approve each one individually or set permissions to allow everything upfront. The first is slow. The second is risky.

Auto mode is the middle ground. Instead of you approving every action or blindly trusting all commands, Claude makes permission decisions on your behalf. Safeguards check each action before it runs.

What does this mean in practice? When Claude needs to create a file, edit code, or run a terminal command, auto mode evaluates the action against safety criteria before executing. No more clicking "allow" forty times during a feature build. No more worrying about a runaway script because you set everything to permissive.

When to Use It

Auto mode is ideal for focused coding sessions where you're actively building. You describe the feature, Claude writes the code, creates files, runs tests, and iterates. The safety checks still prevent destructive operations (force pushes, deleting branches, modifying production configs) unless you explicitly approve them.

It's not a replacement for understanding what Claude is doing. You should still review the output. But it removes the friction of constant permission prompts that break your flow during a build session.

How to Enable It

Auto mode is available now in Claude Code. You can toggle it per session. Start with it on a non-critical project to get comfortable with the behavior. The safeguards are conservative by default, meaning it will still ask for confirmation on anything that could be destructive or irreversible.

MCP Work Tools on Mobile

The second update: MCP (Model Context Protocol) integrations now work on the Claude mobile app. This means the same tools you use on desktop, Figma, Canva, Amplitude, and whatever else you've connected, are now available on your phone.

Why this matters: context switching kills productivity. If you're reviewing a design on your commute, you no longer need to wait until you're at your desk to pull up the Figma file in Claude. If a dashboard alert comes in, you can ask Claude to check the Amplitude data right from your phone.

What Works

Any MCP server you've already configured will show up on mobile. The same connections, the same permissions, the same capabilities. No additional setup required. Claude can:

  • Explore Figma designs and get design context

  • Create and edit Canva presentations

  • Pull dashboard data from Amplitude

  • Access any other MCP-connected tool in your workspace

The mobile interface handles tool outputs the same way as desktop. Screenshots, data tables, and generated content all render properly on smaller screens.

The Pattern

Both updates follow the same principle: reduce friction between intent and execution. Auto mode removes the approval bottleneck in code workflows. Mobile MCP removes the device bottleneck for tool access.

These aren't flashy releases. No new model, no benchmark numbers. But they're the kind of infrastructure improvements that change daily workflows. The best tools are the ones you stop noticing because they just work.

If you haven't tried Claude Code yet, the download is free. If you're already using it, auto mode is worth testing on your next feature build.

For the full setup, including CLAUDE.md configuration, custom commands, and workflow automation, check out the Claude Blueprint. It's the environment configuration that makes all of this actually productive.

Top comments (0)