Okay so Anthropic dropped Claude Code Web today and I’ve been playing with it all night because this is genuinely different from what we’ve had before.

Everyone’s talking about “coding in the browser” but that’s like… the least interesting part? The real thing is you can now run multiple Claude agents at the same time in the cloud. And I know that sounds boring but stay with me.

Why I actually care about this

So like, the CLI version of Claude Code is great but you can only do one thing at a time. Which means if you want to fix bugs AND write tests AND update docs, you’re literally just… waiting. Sitting there. Watching Claude type.

There are a couple of workarounds - multiple terminal windows, git worktrees, Docker containers, tmux splits - basically anything to run multiple Claudes at once. But sometimes spinning up 5 terminal windows and managing 5 different contexts can become confusing, And this problem becomes insane as you keep spinning up 5+ new terminal windows for every new claude instance.

Now? You just open the website, kick off 5 different tasks, and they all run in parallel in the cloud. No setup. No configuration hell. Good structure to break down tasks. Just works.

Stuff I’ve been trying (and actually works)

The “oh shit” Monday morning scenario

You know that feeling when you come back Monday and there’s 30 GitHub issues labeled “bug”? Used to ruin my whole week.

Now I’m just… selecting 5 of them, letting Claude Code spin up 5 agents, and each one tackles a bug while I drink coffee and read through the PRs as they come in.

Like I’m not even exaggerating - I did this with our actual backlog. 5 bugs, 5 parallel agents, 1 hour later I had 5 PRs. Some needed tweaks obviously, but the tedious part was just… done.

Testing “what if” without the commitment

Here’s a thing I always wanted to do but never had time for: when you’re deciding between different approaches, actually BUILD all of them to compare.

Like last week we were debating three ways to handle caching. Normally you either:

• Pick one and hope it works

• Spend days prototyping all three

• Have a very long meeting where everyone argues

Now? I literally can spin up 3 agents, each with different instructions:

• “Make it stupid fast”

• “Make it maintainable by junior devs”

• “Use zero external dependencies”

Got three working versions. COMPARED THEM WITH ACTUAL CODE. Made a decision based on reality instead of vibes.

This is the shit I wished I could do when I was a senior engineer but never had time for.

Coding from my phone like a psychopath

Okay this one sounds fake but I swear it works.

Lazing on my couch, got an idea, pulled out my phone, opened the Claude app, connected to my repo, and just voice-typed: “Add rate limiting to the auth endpoint with Redis, 100 requests per hour per user”

The agent just… did it. In the cloud. While I was literally browsing Reddit.

Got a notification 15 minutes later, reviewed the PR on my laptop, merged it.

I don’t know if this is the future or if I’ve just lost my mind but it felt like magic.

Real talk - what actually makes this different

The cloud thing is huge - Your laptop isn’t doing the work. Which means:

• Your battery doesn’t die

• You can close your laptop mid-task

• Multiple agents don’t make your computer sound like a jet engine

• Works on literally any device with a browser

The parallel thing is huger - Before this, doing multiple things meant:

• Multiple terminal windows (chaos)

• Multiple checkouts (disk space nightmare)

• Containerization (why do I need a PhD for this)

• Or just… waiting (boring)

Now it’s just tabs. Open task. Open another task. They run together. That’s it.

The mobile thing is bonkers - I still can’t believe this works on an iPhone. Like I tested it on an iPad and it’s legitimately usable. Who asked for this? Me, apparently, when I have shower thoughts.

What I’ve learned will probably fail

Not everything is sunshine and rainbows. Here’s what didn’t work:

Trying to do architecture from my phone - Yeah no. Complex system design still needs a real computer and a whiteboard. The mobile thing works for quick fixes and simple tasks but don’t try to rebuild your auth system from the beach.

Spinning up 20 agents at once - Hit rate limits immediately. Also my brain couldn’t keep track of 20 different PRs. 5-10 is the sweet spot for me.

Vague prompts at scale - If you give one agent a vague prompt, you get a vague result. Give 10 agents vague prompts? Ten different interpretations. Be specific or suffer.

Zero-context tasks - Agents still need context. Saying “fix the bug” to 10 agents without explaining which bugs or providing error messages = 10 confused agents asking you questions.

Random cool things people are building and talking about

I asked around, browsed on X and Reddit and here’s some wild stuff:

Someone is using this to translate their entire Python codebase to three different languages at once (Go, Rust, Node) just to see which one is actually better. Not to migrate - just to make an informed decision. That’s powerful.

A PM friend is using it to auto-generate documentation by spawning agents per microservice. Each agent reads the code, writes the docs, creates diagrams. She said it’s the first time their docs are actually up to date.

Saw someone analyzing their meeting transcripts for conflict avoidance patterns. Not coding related but like… damn, that’s therapeutic.

A team is doing bulk security updates - spawning agents to add logging to 200 different files simultaneously. What used to take a sprint now takes an afternoon.

How to actually try this without losing your mind

If you’re Pro or Max, just go to [claude.com/code] and click around. It’s pretty intuitive.

Start small:

• Pick 3 easy bugs from your backlog

• Make them each a separate task

• Watch them run

• Review the PRs

• Decide if this is useful

Don’t start with:

• “Rebuild my entire app”

• 50 parallel agents

• Critical production code

• Anything you can’t easily review

Work your way up. I started with “rename variables across codebase” type stuff and now I’m having it refactor entire modules.

My actual take after 3 hours

This feels like when GitHub Actions first clicked for me. Suddenly you realize you can automate away entire categories of boring work, and you wonder why you were doing it manually.

Is it perfect? No. Does it solve every problem? Definitely not. Will it write your startup for you? Stop asking this question.

But if you’re drowning in grunt work - bug fixes, test writing, documentation, routine refactors - this thing is genuinely useful.

The fact that I can kick off multiple tasks from my phone while I’m making dinner and review the results later… I don’t know man, we’re in a weird timeline.

Questions I can’t answer yet

• How does this scale to huge codebases? (Testing this week)

• Can you chain agents together for complex workflows? (Probably?)

• Will this replace junior devs? (No, but it changes what “junior work” means)

• Is coding from my phone while on the toilet the future? (God I hope not)

If you’re trying this, what’s working for you? What’s breaking? I’m collecting real experiences because the hype is real but I want to know the truth.

P.S. - Yes the CLI is still better for actual development work where you’re iterating. This is for when you have 20 discrete tasks and 2 hours. Different tool, different job.

P.P.S. - Rate limits are shared between web and CLI so don’t go crazy or you’ll burn through your quota.

Like a Codex from ChatGPT. Testing it now!

You can now delegate coding tasks to Claude without opening your terminal. 

With Claude Code on the web, assign multiple tasks that run in parallel while you monitor and steer from your browser or iOS app.

It's ideal for tackling bug backlogs, routine fixes, and parallel development work. Each session runs in its own isolated environment on Anthropic-managed infrastructure to keep your code and credentials safe.

Claude Code on the web is available now in beta as a research preview for Pro and Max users.

Learn more: https://www.anthropic.com/news/claude-code-on-the-web

Technical deep dive: https://www.anthropic.com/engineering/claude-code-sandboxing