This Claude Code command is amazing.

It’s somehow like the multi-agent teams feature — but much simpler and more straightforward.

It’s perfect for those large-scale changes that can easily be broken down into smaller tasks — like mass refactoring and codebase migration.

It spins up multiple AI agents to work simultaneously across the codebase — giving you an immense boost in productivity.

Let’s look at the key features that make it so invaluable when working with Claude Code — from autonomous testing and pull requests, to how it combines brilliantly with other Claude Code commands to build a comprehensive engineering workflow.

1. Multi-agent task decomposition

The foundation of /batch is its ability to break large requests into smaller, independent units of work.

When you invoke /batch, Claude Code:

• Analyzes the repository.
• Understands the requested objective.
• Identifies logical boundaries within the codebase.
• Decomposes the work into 5–30 independent work units.

Rather than editing files sequentially, Claude distributes work across multiple agents that can operate in parallel.

For example, a framework migration might be divided into:

• Shared UI components
• Authentication modules
• Routing logic
• API integrations
• Testing infrastructure

By separating work into distinct scopes, /batch can scale far beyond the limitations of a traditional single-agent workflow.

2. The /batch and /simplify power combo

One of the more interesting aspects of /batch is how it complements Claude Code’s /simplify command.

While /simplify focuses on reducing complexity and unnecessary abstractions, /batch can coordinate improvements across an entire codebase.

The combination gives us several advantages:

• Identifies overly complex patterns at scale.
• Reduces unnecessary abstractions and indirection.
• Improves code readability and maintainability.
• Creates greater consistency across modules.
• Eliminates repetitive manual refactoring work.

Instead of simplifying files one by one, you can use /batch to coordinate the effort across dozens of components simultaneously. This makes large-scale codebase cleanup and standardization significantly faster and more manageable.

3. Git worktree isolation

A key feature of /batch is its use of Git worktrees.

Every subagent receives its own isolated worktree instead of sharing a single working directory.

This enables:

• Concurrent development
• Independent validation
• Isolated dependency management
• Reduced merge conflicts

Because each worker operates in its own environment, changes made by one agent do not interfere with another.

A component migration can run in one worktree while another agent updates tests or refactors utilities elsewhere in the repository.

This isolation is what makes large-scale parallel execution practical and reliable.

4. Autonomous testing and pull requests

/batch is more than a code-editing tool.

Each subagent behaves like an autonomous developer responsible for its assigned scope.

Subagents can:

• Implement code changes
• Run test suites
• Detect failures
• Fix localized issues
• Validate completed work
• Create commits or pull requests

Instead of producing one massive repository-wide change, /batch generates smaller, self-contained outputs that are easier to review and merge.

The result is less manual coordination and a cleaner development workflow.

5. Plan-first execution

Before making any changes, /batch generates a structured execution plan.

The plan outlines:

• How the task was divided
• Which files or directories belong to each work unit
• The responsibilities assigned to each subagent
• The proposed transformation for each area of the codebase

Developers review and approve the plan before execution begins.

This approval stage:

• Provides visibility into the process
• Prevents unexpected repository-wide changes
• Keeps humans in control of major modifications

Rather than blindly applying edits, /batch follows a plan-first approach designed for large-scale engineering work.

Final thoughts

Claude Code’s /batch command represents the broader shift single-agent coding assistance to coordinated multi-agent software engineering.

With key features like:

• Intelligent task decomposition
• Parallel AI execution
• Git worktree isolation
• Autonomous testing
• Pull request generation
• Human approval checkpoints

It enables repository-wide transformations at a scale that would traditionally require significant manual effort.

Software is no longer being built by a single AI agent, but now by a coordinated systems of specialized agents working together toward a common objective.

This is HUGE.

Google’s new Gemini 3.7 Flash is absolutely insane.

It even dominated Claude Sonnet 5 and GPT-5.6 Terra — it’s the best & fastest mid-tier coding model in the world right now.

It literally jumped 11 good places in the AI Arena Leaderboard — now even beating models like Opus 4.8 and Grok 4.5 — despite being several times cheaper and faster.

It’s so amazing at software engineering, web design, and UI generation.

Gemini 3.7 Flash achieved 65.3% on DeepSWE v1.1—up dramatically from Gemini 3.6 Flash’s 48.6% and ahead of Claude Sonnet 5’s 49.7% and GPT-5.6 Terra’s roughly 52–54% results on the same benchmark, establishing a new high-water mark for autonomous software engineering.

Gemini 3.7 Flash has by far the best Time per Intelligence of any model of this intelligence level:

Google’s Gemini 3.7 Flash delivers a breakthrough intelligence-to-speed ratio, hitting a peak output speed of roughly 340 tokens per second while scoring 56 on the Artificial Analysis Intelligence Index—outperforming several pricier flagship peers while finishing multi-step workflows up to 40% faster

It costs so much less than all these other models on the same level of intelligence — you won’t believe how cheap it is right now.

Gemini 3.7 Flash has by far the best Cost per Intelligence of any model of this intelligence level:

Smarter agentic planning — “diligent” thinking

The reasoning and planning have gotten so much more sophisticated.

Instead of immediately generating a response, the model spends more time planning, reasoning, and coordinating tools before taking action.

It thinks more diligently, putting in more effort into multi-step planning and tool calls. A more disciplined execution means less manual oversight and fewer retries across engineering workflows.
— Google

This gives you:

• Better upfront planning for complex tasks
• Self-correction when code or tool calls fail
• Recovery from dead ends without getting stuck in retry loops
• Stronger tool orchestration across multi-step workflows
• Intent clarification when instructions are ambiguous

It doesn’t make risky assumptions of things it’s not sure about — it pauses and ask the right question before continuing.

Which makes a much more reliable coding partner.

Massive software engineering gains

Nobody can look down on Gemini when it comes to coding anymore.

Gemini 3.7 Flash achieved 65.3% on DeepSWE v1.1—up dramatically from Gemini 3.6 Flash’s 48.6% and ahead of Claude Sonnet 5’s 49.7% and GPT-5.6 Terra’s roughly 52–54% results on the same benchmark, establishing a new high-water mark for autonomous software engineering.

3.7 Flash outperforms other frontier models like Sonnet 5 and GPT-5.6 Terra is key software engineering abilities — despite being multiple times cheaper.

It’s been such a massive upgrade:

Benchmark Performance:

65.3% on DeepSWE v1.1

• Up from 48.6% in Gemini 3.6 Flash
• Measures complex, long-horizon software engineering tasks

43.6% on FrontierCode 1.1

• Evaluates first-pass coding accuracy
• Tests real-world engineering capabilities

These gains translate into real meaningful improvements for you as a developer:

• Better understanding of large codebases
• Stronger debugging abilities
• More accurate feature implementation
• Improved multi-file reasoning
• Higher-quality code on the first attempt

Exceptional web dev & frontend design ability

Frontend generation is becoming one of the most competitive areas in AI — and Gemini 3.7 Flash is now among the strongest performers.

Gemini 3.7 Flash generating a world class landing page with posh visual effects from scratch:

Frontend Benchmarks:

• 1588 Elo on WebDev Arena
• 1588 Elo on Code Arena

These scores place Gemini 3.7 Flash ahead of competing models like Claude Sonnet 5 and GPT-5.6 Terra in frontend and full-stack application generation.

And these benchmarks evaluate more than visual appearance. High-performing models must create:

• Responsive layouts
• Multi-component interfaces
• Consistent design systems
• Functional application logic
• Production-quality user experiences

As someone building real-world products, this means fewer revisions and better results for you from the very first prompt.

Incredible UI generation ability

You can give it:

• Wireframes
• Screenshots
• Design systems
• Existing interfaces
• Product mockups

The model can then generate functional applications that closely match the provided designs.

Instead of hallucinating generic layouts, it is far better at preserving structure, styling, and user experience patterns.

The result:

• Fewer prompts
• Less back-and-forth
• Faster prototyping
• Quicker path to production-ready applications

Industry-leading Pricing

This is hands-down one of the biggest selling points.

Introductory Pricing (through December 31, 2026)

• $0.75 per million input tokens
• $3.75 per million output tokens

Standard Pricing (starting January 1, 2027)

• $1.50 per million input tokens
• $7.50 per million output tokens

Even at standard pricing, Gemini 3.7 Flash remains highly competitive.

At launch pricing, it is:

• More than 60% cheaper than Claude Sonnet 5
• More than 60% cheaper than GPT-5.6 Terra
• Competitive or superior across several coding and web development benchmarks

This combination of performance and affordability makes it one of the strongest value propositions in the AI market today.

Far more than just a routine upgrade

It gives us major advances in:

• Agentic planning
• Self-correction
• Software engineering
• Web development
• Frontend design

Combined with aggressive pricing, Gemini 3.7 Flash sets a new benchmark for cost-efficient AI.

For developers and startups building AI-powered products, it’s one of the most compelling models available today.

Claude Code Dynamic Workflows will change the way developers code with AI forever.

It fixes all the problems we’ve had to deal with when trying to use the same agent to do everything — or when trying to make multiple agents work together.

It combines hard-coded code and dynamic LLMs in a way we’ve never seen before — to get the absolute best of both worlds.

Dynamic Workflows allows Claude write its own JavaScript orchestration scripts on the fly and spin up tens to hundreds of parallel subagents to tackle giant tasks end-to-end.

It doesn’t just spawn sub-agents randomly — it deploys them in incredible structured and sophisticated ways.

And the sub-agents are not just doing simple divide-and-conquer code generation like we’ve been seeing.

They are intelligently combining themselves in a way that’s perfectly customized to whatever massive task we give them.

Some of them might aggressively review the code another agent generated — some might be there to pick the best code generated among a set of other agents.

Let’s dive deeper into Dynamic Workflows and see all the ways it can level up the workflows of so many developers.

1. Fixes all the biggest failures of single-context LLMs

Traditional AI agents operate inside a single conversation, which creates three major failure modes.

Defeating agentic laziness

Give one agent a task like reviewing 50 files for a security issue and it eventually becomes difficult to track progress.

Tasks get summarized, details are missed, and the model may prematurely declare success.

Dynamic Workflows solve this through decomposition. Instead of one agent handling 50 files, Claude launches 50 focused subagents. Each agent sees only one file and one objective, while the orchestration layer manages the larger task.

Crushing self-preferential bias

In traditional workflows the same model often generates and reviews its own work.

Dynamic Workflows separate these responsibilities. One agent builds, another reviews, and a third may challenge both. Because reviewers operate in independent contexts, they evaluate outputs against the requirements rather than defending previous reasoning.

Preventing goal drift

Long conversations cause important constraints to disappear over time.

Requirements like maintaining backwards compatibility or preserving performance gradually get compressed out of context.

Dynamic Workflows keep agent conversations short and purpose-built, ensuring every worker remains tightly aligned with the original objective.

2. JavaScript-powered deterministic decomposition

This is one of the biggest breakthroughs with Dynamic Workflows.

Claude doesn’t just spawn agents on the fly — it first writes a custom orchestration program.

LLM’s are great but they can be unpredictable — and there is no guarantee on how they tackle a huge goal.

With this JavaScript orchestration layer, the workflow’s structural control flow is 100% deterministic and predictable.

The file calls multiple JavaScript functions, like agent():

• agent(prompt, options): Spawns an isolated subagent. Can enforce structured JSON data using a schema

We know exactly what is going to happen at the high-level — while letting the individual sub-agents decide how they go about the lower-level tasks distributed among them.

Instead of thinking and generating everything on the fly, Claude generates a JavaScript workflow that determines:

• How work is divided
• Which agents are created
• How outputs are verified
• How failures are handled
• How results are synthesized

Because these workflows are standard artifacts, developers can save, modify, version-control, and rerun them. Over time, teams can build libraries of reusable workflow harnesses and custom agent networks tailored to their engineering processes.

3. Advanced multi-agent design patterns

Dynamic Workflows can combine sophisticated agent architectures on demand.

Tournaments

Multiple agents attempt the same problem using different approaches. A separate judging agent evaluates the candidates and selects the strongest solution.

Adversarial verification

A dedicated reviewer is created with one goal: reject the output.

This agent actively searches for security vulnerabilities, logic flaws, hidden assumptions, and edge cases, creating a far more rigorous review process than self-evaluation.

Fan-out-and-synthesize

For large-scale tasks, Claude distributes work across dozens or hundreds of parallel agents operating independently. Once completed, the workflow pauses and synthesizes all outputs into a unified result.

This pattern is ideal for migrations, audits, documentation generation, and repository-wide code changes.

4. Powering massive engineering projects

The scale enabled by Dynamic Workflows is difficult to overstate.

It’s really hard to overstate the sort of massive scale you could get from using Dynamic Workflows.

A prominent example is the Bun runtime migration from Zig to Rust. Using workflow-driven orchestration, approximately 750,000 lines of Rust code were generated while maintaining roughly 99.8% compatibility with the existing test suite.

Projects that would traditionally span multiple quarters can increasingly become automated jobs running in the background for hours or days.

5. Built-in resumability and safety

Long-running workflows require operational reliability.

The runtime continuously tracks workflow state and subagent progress. If a crash or disconnection occurs, execution resumes from the last checkpoint rather than restarting from scratch.

To prevent runaway costs, the system also provides visibility into workflow execution, token consumption, and resource usage, while enforcing limits that stop recursive workflows from spiraling out of control.

Dynamic Workflows represent a shift from prompt engineering to orchestration engineering.

Rather than asking a single AI agent to solve increasingly complex problems, Claude generates a custom execution harness, launches specialized workers, verifies their outputs, tracks state, and synthesizes results.

The future of AI development is not single super-agent.

It’s dynamically generated teams of specialized agents coordinated by software the AI writes for itself.

This new AI design tool from Anthropic is sending shockwaves across the entire web design industry.

Claude Design is well and truly here — with so many features that completely eliminate the need and cost of hiring a web designer in the vast majority of cases.

And it’s far more advanced that those one-time design generators — this is a full-blown collaborative design environment that helps you discover, refine, compare, and implement ideas faster than ever before.

Generating a UI with dynamically generated controls using Claude Design:

And it works hand-in-hand with Claude Code — you can go from idea to design to full working code in no time at all.

Sophisticated dynamic tweaks panels

This is hands-down one of the most incredible features.

When Claude creates a design, it can automatically create visual controls tailored to that specific interface.

These controls can include:

• Sliders
• Toggles
• Color palettes
• Spacing controls
• Typography adjustments
• Density settings
• Layout controls

The generated design has its own custom tweaks that let you adjust the theme and typography:

Instead of typing:

“Reduce the padding by 20%.”

or

“Make the design feel more compact.”

You can adjust settings directly on the canvas and see changes instantly.

This instantly gives you:

• Faster iteration
• Fewer prompt cycles
• Less token usage
• More precise visual control

The experience feels closer to using professional design software than just chatting with an AI.

Guided design questionnaires

A major challenge with AI design tools is knowing what prompt to write.

Claude Design addresses this with guided questionnaires and visual discovery exercises.

Rather than presenting a blank canvas, it asks users questions like:

• What are you building?
• Who is the audience?
• What style do you prefer?
• Which layouts appeal to you?
• What is the primary goal of the experience?

The platform can also present visual options and taste tests to help users identify preferences before design generation begins.

This approach offers several advantages:

• Reduces prompt anxiety
• Helps users clarify their vision
• Produces more relevant designs
• Makes design accessible to non-designers

Instead of guessing what to ask for, users are guided toward a solution.

Multi-option brainstorming

Traditional design workflows often focus on a single concept at a time.

Claude Design encourages broader exploration.

Rather than generating one design, it can produce multiple radically different approaches simultaneously.

For example, a landing page request might generate:

• A minimalist concept
• A bold marketing-focused layout
• A highly visual creative direction
• A data-heavy enterprise design

All options appear side-by-side on the same canvas.

This makes it easier to:

• Compare ideas
• Identify strengths and weaknesses
• Gather stakeholder feedback
• Combine the best elements into a final concept

Instead of asking for version after version, teams can evaluate several directions immediately.

Direct design-system syncing

Many AI-generated interfaces look impressive but are disconnected from real products.

Claude Design attempts to solve this through /design-sync.

/design-sync lets Claude connect to:

• GitHub repositories
• Storybook libraries
• Existing applications
• Internal design systems

Once connected, Claude can use:

• Real React components
• Company color palettes
• Existing typography systems
• Approved design patterns
• Spacing and layout rules

This means prototypes are built using actual product assets rather than generic SaaS templates.

So you end up getting:

• Better brand consistency
• More realistic prototypes
• Less redesign work
• Faster implementation

Interactive canvas controls

Claude Design is not limited to text chat.

You can interact directly with designs through the canvas itself.

Capabilities include:

• Pin-comments on individual elements
• Drag-and-drop adjustments
• Visual alignment changes
• Layout refinements
• Direct element manipulation

This hybrid workflow combines AI generation with traditional design interactions.

Not every design change should require a prompt.

Sometimes it is faster to simply move an element.

Claude Design supports both approaches.

Seamless handoff to Claude Code

The final stage of the workflow is where Claude Design becomes especially powerful.

Once a prototype is approved, Claude can package the project into a structured handoff bundle.

That bundle can flow directly into Claude Code or other AI-assisted development workflows.

This gives you a continuous pipeline:

Idea → Prototype → Refinement → Design-System Validation → Claude Code → Production Software

You end up getting:

• Reduced designer-developer handoff friction
• Less documentation overhead
• Faster implementation
• Better alignment between design and code

Instead of rebuilding requirements from screenshots or mockups, development can begin with the design context already intact.

Why it matters

Claude Design represents a shift from AI-generated mockups to AI-assisted product creation.

Its key differentiators include:

• Dynamic Tweaks panels
• Guided design interviews
• Multi-option brainstorming
• Design-system synchronization
• Interactive canvas controls
• Direct integration with Claude Code

Together these features help you and your team move from idea to implementation faster while maintaining consistency with existing products and design standards.

Rather than simply generating screens, Claude Design focuses on improving the entire journey from concept to production-ready software.

This is absolutely incredible.

Meta’s just released a revolutionary new AI coding agent.

The new Muse Code is so unbelievably cheap and intelligent — once again we see the clear trend of AI getting cheaper and cheaper.

And it comes with a revolutionary new approach to multi-agent collaboration, that could transform the workflow of so many developers.

Powered by their most powerful model ever — this is going to make major impact on the entire AI coding ecosystem.

Demo stage #1: A drone fly through video to be given to Muse Code to integrate into a landing page:

Muse Code is a terminal-based agent designed from the group up to handle complete software engineering tasks across large repositories — putting it directly against tools like Claude Code and Codex.

But it’s not just yet another coding assistant in your terminal.

Meta is building it around a bigger idea: coding agents should work for hours, coordinate multiple workers, survive failures, and keep making progress autonomously.

Let’s check out all the most amazing features it comes with — including how incredibly inexpensive it is.

Demo stage #2: Asking Muse Code to integrate the video into the website with various marketing copies at different points in the video — directly from the terminal:

1. Persistent background agents — less repeated work

Most coding agents create a subagent, give it a task, collect the result, and destroy it.

Muse Code instead keeps asynchronous background agents alive throughout the session.

They can:

• investigate different parts of the codebase
• retain context they’ve already gathered
• work while the main agent continues
• report useful discoveries back later

For us developers, this means less repeated exploration of large repositories.

Instead of one agent repeatedly searching hundreds of files, you get specialized workers that gradually build knowledge of the project while the main agent keeps coding.

Demo stage #3: Muse Code intelligently integrates the video into the website, with all the marketing copies and the final call to action:

2. Incredible low cost — run coding agents for a fraction of the price

Meta is also being extremely aggressive on price.

Its Contributor tier can bring pricing down to as little as $0.20 per million output tokens — less than one-tenth of typical frontier-model rates.

One thing you need to know though — if you’re using this discounted tier, you have to agree to let Meta use your interactions, including generated code, to help improve its models.

If you’re comfortable with that, this could be huge for your cost savings.

Long-running agents can burn through enormous numbers of tokens. Making those tokens dramatically cheaper makes Muse Code’s hours-long autonomous coding loops and parallel agents much more practical to run regularly.

3. Muse Spark 1.2 — Meta now has a serious coding model

Muse Code is powered by Muse Spark 1.2, Meta’s new coding-focused model.

And interestingly Meta says the model and coding harness were co-trained — not something you see everyday from most other models.

Rather than wrapping an agent around a generic model afterward, Meta trained Spark using the environment and workflows it would eventually operate inside.

Some key benchmark results from Muse Spark 1.2:

• Terminal-Bench 2.1: 82.9%
• DeepSWE 1.1: 59.3%
• Meta Internal Coding Bench: 70.6%

Meta hasn’t taken the coding crown (yet??) — but it’s clearly become a serious competitor.

4. Parallel worktrees — build multiple things at once

Muse Code can also fan large tasks out across multiple subagents running simultaneously in isolated Git worktrees.

Each agent gets its own workspace, allowing several agents to modify the same repository without constantly overwriting each other’s work.

Meta demonstrated this by having Muse Code build six game features simultaneously without collisions.

The practical benefit is speed.

Instead of:

feature A → feature B → feature C → feature D

you potentially get:

feature A + feature B + feature C + feature D

all being developed simultaneously.

AI coding starts looking less like one extremely fast developer and more like a small engineering team working in parallel.

5. Crash recovery — long-running agents don’t lose everything

Long-running agents create another problem: failure becomes increasingly expensive.

Imagine an agent researching, coding, testing, and debugging for three hours — then the process crashes.

Muse Code addresses this with a local append-only event log.

Model calls, tool executions, approvals, edits, and other actions are recorded as events. The runtime can replay them to reconstruct its previous state.

That makes executions restart-safe.

For five-minute coding prompts, this isn’t particularly important.

For autonomous tasks lasting several hours, it’s essential.

6. 24-hour coding runs — AI coding becomes a background process

Meta is clearly designing Muse Code for much longer tasks than normal prompt-and-response coding.

In one experiment, Muse Code optimized GPU kernels for NVIDIA Hopper hardware.

The agent repeatedly:

wrote code → compiled → profiled → analyzed → improved

It made more than 1,000 tool calls across runs lasting up to 24 hours.

That’s a very different model of AI-assisted development.

For optimization, migrations, debugging, test improvement, and other measurable engineering problems, you could define the goal, leave the agent running, and return later to the results.

What all this tells us

The most interesting part of Muse Code isn’t another benchmark score.

It’s everything surrounding the model:

Persistent agents. Parallel worktrees. Crash recovery. Thousands of tool calls. 24-hour autonomous runs.

The AI coding race is moving beyond “which model writes the best code?”

It’s increasingly about which system can reliably keep working until the engineering task is actually finished.

Muse Code is Meta’s answer.

This new viral Skill is an absolute game changer for Claude Code.

The I Have ADHD Skill massively upgrades the quality and clarity of Claude’s responses by encouraging it to communicate in a much more direct, structured, and action-oriented way.

It removes all the fluff and goes straight to the point — saving you so much token costs and improving your mental model of the task at hand.

The crucial problem it’s here to solve

AI coding assistants often answer simple questions with long explanations before getting to the solution.

That style can be useful for learning — but when you’re debugging, shipping features, or reviewing code, it creates unnecessary friction.

The “I Have ADHD” skill solves that by encouraging Claude to prioritize the next action instead of lengthy context.

How the Skill works

The skill dramatically changes how Claude structures its responses.

Instead of long introductions, it’s encouraged to:

• Start with the immediate next step.
• Break work into numbered tasks.
• Remove unnecessary filler.
• Show progress throughout a task.
• Finish with one clear next action.

You end up getting an AI that isn’t just intelligent, but also extremely easy to work with.

Why so many developers love it

The project quickly gained over 10,000 stars on GitHub within days of launch.

Because it addresses a frustration many developers have long had with AI assistants: too much explanation and not enough execution.

Whether you’re debugging, refactoring, or navigating a new codebase, concise responses reduce cognitive load and help you stay focused.

How to get started with the I Have ADHD skill

Install it easily with these commands:

Then type /i-have-adhd in a Claude Code session to activate it — all the responses will be structured according to the rules of the skill for the rest of the session:

How to use it to transform your workflow (5 practical use cases)

1. Debugging production issues

Without the skill

With the skill

Why it matters: When production is down, you need the next action — not a lesson.

2. Refactoring legacy code

Without the skill

With the skill

Why it matters: Breaking work into milestones makes large refactors feel manageable.

3. Building large features

Without the skill

With the skill

Why it matters: You stay focused on one phase instead of being overwhelmed by the entire implementation.

4. Learning an unfamiliar codebase

Without the skill

With the skill

Read these first:

Why it matters: You can understand the project faster by focusing only on the files that matter.

5. Reviewing pull requests

Without the skill

With the skill

Why it matters: Prioritized feedback makes reviews quicker to understand and easier to act on.

Final thoughts

You don’t just need a smarter assistant — you need an assistant that helps you get things done faster.

Sometimes the biggest productivity improvement isn’t giving an AI more knowledge. It’s simply teaching it to get to the point.

You think Claude Code makes you code faster — but you don’t realize you’re barely scratching the surface.

Just sending prompt after prompt to Claude Code will get you nowhere.

When you ignore features like Loops, you end staying far behind what your potential could be — in speed and accuracy and everything that moves you closer to your goals as a developer.

Loops are like the holy grail of AI automation.

You’re no longer just manually prompting and hoping to get exactly what you want.

Now Claude will actually do the prompting for you — over and over until it gets the exact prompt that meets your exact requirements.

It’s an absolute game changer.

You are going from regular prompt engineering — to full-blow loop engineering.

No more step-by-step instructions — now you define precise goals, verification criteria, and stopping conditions.

And it doesn’t stop at prompting.

What are Claude loops exactly?

Claude Code loops are the iterative execution cycles in which Claude repeatedly:

• Reads the current project context
• Uses tools such as terminal commands or file editing
• Evaluates the results
• Repeats the process until a predefined stop condition is met

Instead of acting like a one-shot chatbot, Claude functions as an autonomous background agent capable of completing tasks with minimal human intervention.

The four types of loops

Claude Code gives you four primary loop patterns.

1. Turn-based loops — Complete everyday tasks reliably

Every prompt already runs inside a turn-based loop by default.

Claude gathers context, performs edits, executes tools, verifies its work, and returns a response.

Example:

Scenario: Fixing a bug in a login form.

Prompt:

Fix the bug preventing users from logging in with Google OAuth.

What Claude does:

• Reads the authentication code
• Identifies the issue
• Updates the implementation
• Runs relevant tests
• Returns the completed fix

The loop ends once Claude has finished your task and gives you a response.

These loops are ideal for everyday tasks such as debugging, refactoring, and implementing small features.

2. Goal-based loops — Make sure Claude explicitly finishes the job

Goal-based loops continue working until a measurable objective has been achieved.

Example:

Scenario: Eliminate all failing tests.

Prompt:

Keep working until every unit test passes.

Do not stop if tests fail—fix the issues and rerun the test suite until all tests are green.

What Claude does:

• Runs the test suite
• Finds failing tests
• Makes code changes
• Reruns the tests
• Repeats until every test passes

Instead of stopping after one attempt, Claude keeps iterating until the success criteria are met.

Rather than generating a single answer, Claude keeps iterating until the defined outcome is reached.

3. Time-based loops — Easily automate recurring development tasks

Time-based loops execute on a schedule, similar to cron jobs.

For example:

Scenario: Monitor a pull request throughout the day.

Command:

/loop 15m check my open PR, address any new review comments, rerun CI, and commit fixes if needed.

What Claude does every 15 minutes:

• Checks for new reviewer comments
• Updates the code
• Runs tests
• Verifies the build
• Waits until the next scheduled run

This is similar to a cron job, except the scheduled task is powered by an AI agent rather than a static script.

Claude periodically revisits the task without requiring another prompt.

4. Proactive loops — Let Claude continuously maintain your projects by itself

Proactive loops are the most autonomous.

Instead of waiting for your instructions, they continuously handle repetitive engineering work.

For example:

Scenario: Automatically maintain a repository.

Workflow:

Every once in a while, Claude:

• Scans the repository for outdated dependencies
• Opens upgrade pull requests
• Fixes simple merge conflicts
• Runs the test suite
• Closes duplicate issues
• Updates documentation if APIs have changed

No developer prompt is required. The workflow runs continuously based on a schedule or repository events, keeping the project healthy with minimal manual intervention.

This shifts AI from reactive assistance to proactive software engineering.

Evaluator-driven verification — Reduce bugs by making Claude prove its work

One of the biggest challenges with language models is premature satisfaction—assuming a task is complete before proving it works.

Claude Code addresses this with external verification.

Instead of relying on Claude’s confidence, an evaluator checks the outcome using objective signals like:

• Unit tests
• Linters
• Browser automation
• Performance checks

If verification fails, Claude automatically returns to work until the required checks pass.

Cron-like AI workflows — Turn Claude into a scheduled engineering assistant

Time-based loops effectively turn Claude into a scheduled AI engineer.

A recurring loop can:

• Review open pull requests
• Respond to new review comments
• Apply fixes
• Re-run tests

You can step away while Claude continuously manages routine engineering work in the background.

Deterministic API control — Build reliable autonomous agents that stop at the right time

Claude Code loops are controlled by structured API signals rather than natural-language responses.

States such as stop_reason: "tool_use" and stop_reason: "end_turn" determine whether Claude should continue working or exit the loop. This deterministic control flow reduces premature exits and prevents runaway execution.

Tiered cost optimization — Scale long-running AI workflows while keeping costs low

Long-running loops can become expensive if every iteration relies on a frontier reasoning model.

To reduce costs, routine tasks—such as gathering context or running shell commands—can be delegated to smaller, faster models. More capable models are reserved for complex reasoning and code changes, making autonomous workflows more efficient.

Loops are the future — Spend less time prompting and more time shipping software

With loops, instead of waiting for prompts, Claude can monitor repositories, manage pull requests, triage issues, and perform continuous maintenance with minimal supervision.

By combining iterative execution, automated verification, deterministic control flow, and scheduled automation, loop engineering enables AI agents that work toward measurable outcomes—not just generated responses.

The result is an AI that behaves less like a chatbot and more like a persistent engineering teammate.

Small features can change workflows massively — and the new /btw is definitely one of such.

❌ Before:

This is what many of us are used to right now — every question you ask an AI coding assistant becomes part of the same growing conversation thread:

No /btw feature used to ask questions here 👇:

Which unfortunately leads to questions, clarifications, and quick reminders slowly cluttering the context — making sessions more expensive than ever.

✅ Now:

Now Claude Code’s new /btw command is here to change all that — by creating a lightweight lane for disposable, context-aware questions.

Making changes just before using /btw:

Asking questions on our changes with /btw:

When we press Enter, the btw message disappears and we’re back to our normal conversation:

It’s a simple but powerful feature that makes those long coding sessions cleaner and much more efficient.

What /btw actually is

/btw is a lightweight side-question feature inside Claude Code. It can see the current session context, meaning it understands the code, decisions, and task state already in play.

But unlike the main thread, it’s intentionally constrained.

1. Context-aware

/btw understands the active session.

That means you can ask questions tied to the current work, such as:

Making changes to our codebase:

• “What does this regex do?”
• “What is this helper function responsible for again?”
• “Why did we choose this configuration pattern earlier?”

Using /btw to ask context-aware questions:

You’re not asking a model with zero memory. You’re asking from inside the active coding session, where the relevant context already exists.

That’s what makes /btw more useful than opening a separate AI chat.

2. Disposable history

The core idea behind /btw is that the interaction is temporary.

Your question and its answer do not become part of the main conversation history.

Making changes to our codebase:

Why this matters:

Many developer questions are momentary:

• reminders
• clarifications
• quick explanations

Using /btw to ask questions:

Claude Code doesn’t remember the previous /btw message:

You need the answer right now, but the agent doesn’t need to keep re-reading that exchange for the rest of the session.

Think of /btw as:

• a sticky note, not a commit message
• a side whisper, not a meeting transcript

3. Read-only

Another important constraint:

/btw cannot perform actions.

Making changes to our codebase:

It cannot:

• edit files
• run bash commands
• use MCP tools
• inspect new files

It can only talk.

Trying to make changes with /btw — it doesn’t work — it only shows a message containing the code at best:

This means /btw isn’t meant for implementation work. Instead, it’s meant for:

• explanations
• reminders
• quick clarifications
• contextual understanding

You use /btw to stay oriented while real work continues elsewhere.

4. Single-turn only

/btw also enforces a strict interaction model:

One question. One answer.

There’s no extended back-and-forth and no mini-thread forming inside the /btw window.

That constraint prevents it from turning into a secondary conversation.

It stays exactly what it’s meant to be: a quick aside.

How it helps us as developers

The real value of /btw isn’t the command itself.

It’s how it improves workflow during long, context-heavy coding sessions.

1. Massive token savings

Claude Code stays effective by remaining aware of the full conversation history.

But that also means every new turn in the main thread carries the cost of everything that came before it.

As sessions grow, small interruptions become expensive.

For example:

• A 40-message thread means Claude rereads a large context every turn.
• Adding clarification questions increases that cost quickly.

This is where /btw helps.

Instead of putting these into the main thread:

• “What does this regex do?”
• “What was this utility function for again?”
• “What does this flag change?”

You route them through /btw.

The result:

• fewer tokens in the main thread
• less history to reread
• significantly cheaper long sessions

Over time, this can cut total session costs dramatically.

2. It prevents context rot

Long AI conversations naturally degrade.

As threads grow, the context becomes noisy:

• temporary explanations
• side questions
• dead-end ideas
• minor clarifications

Eventually the model starts losing track of what matters.

Developers often see this as:

• missed constraints
• forgotten earlier decisions
• weaker reasoning

This is essentially context rot.

/btw helps prevent this by enforcing separation:

Main thread

• implementation
• architecture decisions
• debugging
• planning
• file edits

/btw

• explanations
• quick reminders
• clarifications
• trivia

Keeping those categories separate helps the main thread remain clean and focused, which maintains higher reasoning quality for longer.

3. Seamless multitasking

This is the most underrated benefit.

During long-running Claude tasks—like refactors or multi-file updates—you’ll often have small questions.

For example:

• “What syntax does this function expect again?”
• “What does that pattern mean?”
• “Did we say this utility handles validation?”

Without /btw, you have two options:

1. Interrupt the main thread and risk derailing the workflow.
2. Hold the question in your head and slow yourself down.

/btw gives you a third option.

You can quickly ask the question without altering the agent’s working context.

This makes Claude feel less like a fragile chat log and more like a collaborator that can handle quick side questions while staying focused on the main task.

The real takeaway

The best way to think about /btw is this:

It’s a pressure-release valve for long Claude Code sessions.

It allows developers to:

• ask context-aware questions
• avoid polluting the main thread
• reduce token usage
• preserve reasoning quality
• multitask more smoothly

For developer workflows, that’s not a flashy feature.

It’s just good interface design.

Most AI tools treat every interaction as permanent. /btw recognizes that real development doesn’t work that way.

Some questions matter long-term — others are just momentary.

Treating those differently is exactly why /btw matters.

If you’re still AI coding with one agent at a time, you’re seriously wasting the incredible potential Claude Code gives you.

Learning how to develop with multiple agents at a time will massively boost your speed and productivity.

You can work on different features, bug fixes, and cleanups on your codebase all at the same — saving unprecedented amounts of time.

One critical challenge though — how do we keep all the agent sessions from interfering with each other?

How do we make them work simultaneously without tearing into each other’s changes?

Claude Code solves this brilliantly with the native Git worktree feature.

Instead of cloning your repository multiple times, it creates lightweight, isolated workspaces that share the same Git history while giving each session its own branch and working directory.

As a developer, this lets you easily:

• Build multiple features simultaneously
• Eliminate branch-switching headaches
• Experiment safely without affecting ongoing work
• Scale AI-assisted development with minimal overhead

Instant session isolation: Build multiple features without workspace conflicts

Launching Claude with the -w (or –worktree) flag instantly creates a dedicated worktree and Git branch.

claude -w [branch]

Each Claude session gets its own isolated environment, meaning edits in one terminal never affect another.

Isolated worktree environment in .claude/worktrees/[branch]

For example, you could have separate sessions working on:

• Authentication
• Dashboard UI
• Payment bugs
• Documentation
• Test coverage

As a developer, this means:

• No constant branch switching
• No stashing unfinished work
• No accidental file conflicts
• True parallel development

Every task gets its own workspace, making it much easier to stay focused.

Automated worktree creation: Let AI agents manage their own workspaces

Worktree isolation isn’t limited to top-level Claude sessions.

When Claude Code delegates work to subagents, it can automatically create a dedicated Git worktree for each one.

Rather than sharing the parent’s workspace, every agent receives its own isolated environment where it can edit files, run commands, and validate changes independently.

Every time that agent runs, Claude automatically creates an isolated workspace — under .claude/worktrees/.

Instead of manually preparing worktrees before delegating work, the agent handles everything automatically.

This gives you:

• Less setup
• Less manual Git management
• Safer parallel execution
• Easier large-scale refactoring

This is especially useful when multiple agents are generating tests, updating documentation, or performing code migrations simultaneously.

Native context switching: Experiment without losing your session

Sometimes you want to try something risky without abandoning your current conversation.

Claude Code includes a built-in EnterWorktree capability that lets you switch into a new worktree mid-session.

Simply ask Claude:

• “Create a worktree for this experiment.”
• “Switch to the auth worktree.”

Claude creates — or enters — the requested workspace while preserving the existing conversation and context.

For developers, this encourages experimentation.

You can:

• Prototype new ideas
• Try alternative implementations
• Test risky refactors

—all without restarting Claude or losing the context you’ve already built.

Zero repository duplication: Scale parallel development efficiently

Traditional parallel development often means cloning the same repository several times.

That duplicates:

• Git history
• Object databases
• Repository metadata
• Disk usage

Git worktrees avoid all of that.

Every worktree shares the same underlying Git database while maintaining its own:

• Working directory
• Checked-out branch
• Staging area

Because the repository isn’t duplicated, creating a new Claude worktree is almost instantaneous—even for very large projects.

For developers, this means more AI sessions without paying the cost of multiple repository clones.

Intelligent lifecycle management: Stay organized without Manual cleanup

Temporary workspaces are useful — but only if they don’t pile up.

Claude Code helps manage their lifecycle automatically.

When a worktree finishes:

• No changes? Claude removes it automatically.
• Changes made? Claude asks whether you’d like to keep or delete it.

Background cleanup also helps remove stale temporary workspaces while preserving active branches.

For us developers, this means:

• Less maintenance
• Fewer abandoned directories
• Cleaner repositories
• More time spent building instead of cleaning up

Final thoughts

Git worktrees have existed for years, but Claude Code transforms them into a seamless workflow for AI-assisted development.

Instead of treating AI as a single coding assistant, you can coordinate multiple isolated agents working on different parts of the same project.

The benefits are clear:

• Faster feature development
• Safe parallel workflows
• Lightweight isolated environments
• Less Git overhead
• Cleaner development workflows

As AI becomes a larger part of software engineering, worktrees provide the foundation for running multiple coding agents efficiently — without the chaos of shared workspaces.