Claude Code Update is INSANE
Claude Code has launched a web and mobile interface at claude.ai/code, allowing developers to kick off and monitor coding tasks remotely without a terminal. The update introduces cloud-based VM execution, persistent sessions, parallel task running, and an auto-fix feature for pull requests. This transforms Claude Code from a terminal-only tool into an async coding collaborator.
Summary
The video covers Anthropic's major update to Claude Code, which previously required users to be present at a terminal. The new experience is accessible via claude.ai/code and allows developers to connect their GitHub account, write a plain-English prompt, and launch full coding tasks directly from a browser. Anthropic runs these tasks on isolated cloud virtual machines pre-installed with Python, Node.js, Ruby, Go, Rust, Java, PostgreSQL, Redis, Docker, and Git. Claude clones the target repository, performs the work, and presents a reviewable diff in the browser.
A key capability highlighted is session persistence — even if the user closes their browser tab, Claude continues working in the cloud. Users can monitor and steer sessions from the Claude mobile app, answering Claude's questions or approving actions without being at a laptop. The presenter outlines several workflows: launching tasks directly from the browser, using a `--remote` flag in the CLI to offload work to the cloud while continuing local development, and a plan-then-execute workflow where Claude proposes a plan locally before running autonomously in the cloud.
The auto-fix feature for pull requests is described as particularly underrated. Once a PR is created, Claude monitors it on GitHub, automatically investigating and pushing fixes when CI checks fail, and addressing reviewer comments — with transparent disclosure in the thread that responses came from Claude Code.
On the infrastructure side, each session runs on fresh Anthropic-managed VMs with environment caching, so setup scripts only run once and future sessions boot from a snapshot. Security is handled via a proxy with scoped credentials, ensuring Git keys never exist inside the sandbox. Users can run multiple parallel cloud sessions simultaneously and use a 'teleport' command to pull a finished cloud session back into the local terminal with full conversation history intact.
Practical tips include maintaining a claude.md file in the repo for persistent context, using inline diff comments for cleaner review feedback, and monitoring context window usage with built-in commands. The video closes with availability information — Claude Code on the web is in research preview for Pro, Max, Team, and Enterprise users — and promotional mentions of the presenter's AI community and resource hub.
Key Insights
- The presenter explains that Claude Code on the web runs in Anthropic-managed isolated virtual machines pre-installed with a full development stack including Python, Node.js, Ruby, Go, Rust, Java, PostgreSQL, Redis, Docker, and Git — meaning users need nothing installed locally.
- The presenter highlights that cloud sessions persist even after closing the browser tab, allowing Claude to continue working autonomously and enabling users to check in and steer progress from the Claude mobile app.
- The presenter describes a plan-then-execute workflow using permission mode plan, where Claude explores the codebase and proposes a plan without touching code, which the user reviews before sending execution to the cloud — comparing it to a contractor reviewing blueprints before breaking ground.
- The presenter calls auto-fix for pull requests 'the most underrated feature,' explaining that Claude monitors a PR on GitHub, pushes fixes when CI checks fail, and addresses reviewer comments — while transparently labeling its own responses as coming from Claude Code so team members can distinguish agent output from human output.
- The presenter notes that users can run multiple remote sessions simultaneously — for example, fixing a bug on one branch, writing test coverage on another, and refactoring a module on a third all at once — and use a 'teleport' command to pull any finished cloud session back into the local terminal with full conversation history.
Topics
Full transcript available for MurmurCast members
Sign Up to Access