Sunday, August 23, 2026
HomeRuby On RailsParallel AI coding with Сlaude Code: multitask with out shedding your...

Parallel AI coding with Сlaude Code: multitask with out shedding your thoughts


The nightmare of neighbours, household, and pals interrupting your course of each jiffy (“you’re simply typing one thing, it means you aren’t THAT busy to assist me!”) has come true. Solely now, it isn’t people who interrupt us essentially the most. AI beats all data of productiveness in that process.

And whereas some persons are bragging about dozens of pull requests in a single day (though we don’t truly know what number of of these duties get actually closed, and what number of bugs get created alongside the best way), others refuse to modify context in any respect.

As at all times, the reality is someplace within the center. Loading your self with too many duties directly can drain you and create a false sense of productiveness, whilst you’re truly making errors and shedding focus. However absolutely avoiding multitasking simply means watching TikTok whereas AI generates the reply. Tempting as that’s, I’m sorry to say your time can be utilized extra effectively. 

Observe: And if you’d like extra on methods to use AI coding instruments, learn my earlier article on the 4 pillars of utilizing AI in engineering.

TL;DR

  • Parallel AI coding pays off if you match the device to the duty and handle your individual context-switching fatigue, not if you simply pile on extra periods and hope for the very best.
  • Simply beginning out → Brokers View (a number of periods in a single place, worktrees automated).
  • Need guide management → worktrees immediately.
  • Lengthy-running, weeks-to-months process → a separate cloned folder (easy, onerous to interrupt).
  • Duties contain a number of roles (frontend dev/ backend dev/ qa/ product supervisor → Claude Code Groups (quick, however token-hungry).
  • Ought to run with out your laptop computer → Claude Code Internet + Routines (cloud + scheduled).

What are the primary instruments for managing parallel AI coding workflows in Claude Code?

1. Claude Code brokers view

It is a place the place you’ll be able to run a number of periods and assessment them multi function spot. Each session runs in its personal worktree, except you explicitly say in any other case. As a neat addition, it retains your periods alive even when the terminal was closed.

The place to make use of Claude Code brokers view: actual parallel work throughout a number of duties. For instance, you might repair a small bug in a single session, work in your principal process in one other, and examine manufacturing points within the third. You will note all periods in progress, periods which require your consideration, and the checklist of accomplished ones

Drawbacks: 

  • Classes can typically freeze, leaving you with out seen progress for some time.
  • The function’s controls aren’t very intuitive.

repair: not a lot to do in regards to the first one. Hopefully it’ll be mounted quickly. For the second, a keyboard cheat sheet does the trick.

2. Claude Code worktrees

The Claude Code brokers we simply mentioned use Claude Code worktrees internally, however if you’d like extra guide management than the Brokers View gives, it is a good possibility.

A fast overview: with Claude Code worktrees, every process runs in its personal git worktree, so file adjustments by no means battle. It additionally can be utilized for actual parallel work throughout a number of duties.

Observe part: What’s Claude Code worktree: a separate working listing linked to the identical repository however remoted from different duties. That means each AI agent can edit information independently with out overwriting another person’s adjustments or inflicting merge conflicts. 

Drawbacks:

  • All gitignored information received’t exist in a git worktree (true for Brokers View as properly).
  • Managing all of the terminal home windows can get troublesome.
  • Reviewing and testing adjustments isn’t handy, because it requires guide steps, like switching to a worktree, beginning a server, and many others.

repair: use instruments constructed for organizing terminal home windows that allow you to level to which information must be copied. For instance, a tmux plugin like workmux. An alternative choice: add a worktree be aware to your CLAUDE.md that symlinks these information robotically when a worktree is created.

3. New folder linked to the identical repo

It would sound like an old style approach to do issues, however it may be genuinely useful: as an alternative of a worktree, you simply clone the repo once more into a totally separate folder on disk.

The benefit is that it’s lifeless easy and onerous to mess up. There’s no threat of shedding information, in contrast to deleting a worktree, which wipes out any uncommitted adjustments together with it.

The place to make use of: you probably have some long-standing process, you’ll be able to drive it in a separate folder. For instance, now we have the talent to rewrite the legacy JQuery code right into a shiny (okay, possibly a bit worn, 18th model) React JS.

We do it in small items so every change will be correctly reviewed, and because it’s a long-standing process, it might take months to complete. The talent’s directions are easy: go into the pre-created folder, pull the most recent adjustments, decide the smallest piece of code, rewrite it in React, open a PR, and watch CI.

Drawbacks: 

  • You find yourself managing a number of folders for one repo: add an env variable to your .env file in a single, and also you’ll want to recollect to replace it within the different too.
  • Testing adjustments is inconvenient, since it is advisable run the server from inside that separate folder.

repair: 

  • Symlink your principal gitignored information into this folder
  • Create an alias to run the server on a special port inside this actual folder

4. Claude Code Groups

It’s nonetheless experimental. As an alternative of 1 agent working alone, it assembles an entire group of brokers, every with its personal session.

The place to make use of Claude Code Groups: mainly any process that must be carried out, then examined, then reviewed. You don’t must do these steps one after one other your self. The testing and reviewing occur on the identical time, dealt with by totally different brokers, robotically (which is nice).

Drawbacks: it might burn your tokens out fairly rapidly. 

repair: it is a frequent tax on parallel work. If your organization permits it, use a subscription plan as an alternative of pay-as-you-go API billing, and double-check that “Further utilization” is switched off in settings so that you don’t blow previous your limits.

5. Claude Code internet and routines

Claude Code Internet helps you to run duties within the cloud, in order that they don’t rely in your laptop computer being open and even turned on. Routines take {that a} step additional and run duties on a schedule.

The place to make use of Claude Code Internet: any long-running process. For instance of a Routine, you might set one as much as assessment the previous week’s code adjustments and replace the documentation robotically. One other use-case is updating expertise based mostly on the PR opinions.

Drawbacks: some organizations limit these instruments over safety issues. I’ll go away you right here as a result of, you already know, humble your self earlier than safety and endure with persistence.

keep away from burnout whereas multitasking with AI?

Certainly there are some points with the instruments. Nevertheless, not solely. There may be additionally the emotional burden we talked about in the beginning. So, as an engineer with greater than 15 years of expertise, I’ll take the freedom of sharing a few issues that assist me with that.

1. Experiment with the context

Some duties take extra of your vitality than others. Perhaps it’s high-quality so that you can work in parallel on one huge function and one small one. Perhaps you’ll be able to reply messages, examine your mailbox, or look by means of logs whereas AI works on the function. I’ve heard of individuals watching movies about new engineering device options whereas AI works within the background. I’m a bit envious of that. For me, it’s an excessive amount of. New data calls for my full consideration, not even an oz much less.

2. Experiment with the instruments

Attempt among the instruments advised above. Some might be extra handy than others for you. All of us are distinctive snowflakes, so there’s no silver bullet, simply you and your means.

3. Attempt it out for a month or two

Sure, I do know multitasking feels disagreeable. However possibly, simply possibly, it’s since you’re not used to it but. Our brains resist change, and since we stay in fast-moving occasions, we have to adapt and undergo somewhat for it. I can say that after a few months, I caught the rhythm of transferring quick. Now the primary factor is to not get carried away too far.

4. Write notes in your means

I exploit an excellent previous paper pocket book for that. It helps me to not overlook issues and to not be burdened by all of the duties tapping on my window. Additionally, a Q letter close to some duties can assist you to underline what duties will be accomplished rapidly and due to this fact are preferrred to work in parallel with AI. 

If you don’t like handwriting, you should use one other device you like: even easy textual content or md file. Important is writing down what must be achieved, not the place you write this.

5. Swap off notifications in your telephone and work chats when it’s doable 

Don’t add extra multitasking than you have already got. The emotional burden of multitasking didn’t disappear wherever, and it’s extra essential now than ever to maintain your borders up. And to not be distracted by “whats up” after which ready for the message with the matter for one more 5 minutes. 

6. Take breaks

Typically, you want them. Take it straightforward. You aren’t a robotic (but), so your mind feels much less drained after engaged on a single process, and it’s regular. Let’s not be harsh on ourselves. There are folks round who already do it properly sufficient; no must contribute to this. And if you really feel drained, please simply work on one process at a time.

FAQ: Parallel AI coding with Claude Code

What’s the distinction between Claude Code Brokers View and worktrees?

Brokers View is the interface, a single place to run and monitor a number of periods, with worktrees created robotically beneath. Worktrees are the underlying mechanism, a separate checkout of the repo per process. Use Brokers View for comfort; use worktrees immediately if you’d like extra guide management.

Does Claude Code Groups price greater than operating a single agent?

Sure. As a result of a group splits one process throughout a number of brokers working in parallel: implementing, testing, reviewing. It consumes extra tokens than a single agent working sequentially. A subscription plan, quite than pay-as-you-go API billing, typically absorbs this higher.

Can Claude Code run duties with out my laptop computer being on?

Sure, however solely with Claude Code Internet or Routines you’ll be able to run duties within the cloud unbiased of your native machine. Routines can set off duties like code assessment or documentation updates on a schedule.

Is multitasking with AI coding instruments truly extra productive?

It depends upon the way it’s achieved. Operating too many parallel periods directly creates a false sense of productiveness whereas growing errors. The sustainable strategy is selecting one device that matches your process, operating a manageable variety of periods, and utilizing the freed-up time intentionally quite than splitting consideration throughout every thing directly.

Which Claude Code device ought to I begin with for parallel work?

Brokers View is the best entry level because it requires no guide worktree administration. Transfer to worktrees immediately if you’d like extra management. Claude Code Groups is on by default with a subscription. Claude makes use of it robotically, splitting a process into implement/take a look at/assessment roles when the work is well-defined sufficient to profit, and skipping the group for less complicated duties.

I hope all of this helps you change into more practical than earlier than, with out burning out. 

Want you cheerful coding and never that terrible form of multitasking!

Anastasiia Vlasova
Article by Anastasiia Vlasova

Anastasiia is a full-stack developer rooted in Ruby on Rails, with React on the frontend and 13+ years of transport actual merchandise. From greenfield builds to untangling legacy code, she’s snug throughout the stack, together with search, databases, and third-party integrations. Right here, she shares sensible insights on constructing functions that work and hold working. Linkedin
RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments