Recently, Cloud Code released some great

features. Let's see what they are and

why they're useful. The first feature is

the ability to run sub agents and

commands in the background. That means

your main conversation stays clean and

you can keep working while tasks run

quietly in parallel. This is one of the

features I'm most excited about. But

strangely, there's no official

documentation yet. So, instead of

guessing, I asked Cloud Code directly.

So, how does it work? In all devs.com, I

have a sub agent called end-to-end test

architect. Its role is to design and

maintain our end-to-end tests. I want

this sub agent to review everything that

changed over the last two weeks and

decide whether existing tests need

updates or if new ones should be added.

To run it in the background, I simply

ask Claude code directly. Let's execute.

Now you can see cloud code has one

background task. When you click on it,

you can see the sub aent is still

running. If we had more than one, you

could see all of them here. When it

completes, you can click on the sub aent

task and review its job. But don't

worry, the main chat will get an update

that the task is completed. Another way

to open this panel is to run the task

command or you can just exclude code in

the main chat for the current status of

the sub aents work. Next, let's look at

how this works with commands. Imagine we

want to run the current test and make

sure nothing breaks in this project. I

already have an npm script for that. The

key benefit here is running it in the

background because test runs take time

and I don't want them blocking my

workflow. Just like with sub agents, I

can ask load code directly to run the

command in the background or while it's

executing, I can presstrl +b to move it

there. To retrieve the results, you can

either ask load code directly or use the

task command. Don't worry, I'll put a

clear summary of all this in the video

description. But when should you

actually use this? There are two main

scenarios. First, when you're dealing

with longunning commands or sub aent

executions, test suites, builds,

migrations, big refactors. If it takes

time, push it to the background and keep

moving. Second, even when execution time

isn't a big deal, use the background

when the task doesn't need your

supervision. For example, scanning

recent changes, generating docs,

updating test, running a quick audit, or

summarizing logs. The next update is

also related to sub agents. You can now

open a chat session directly with a sub

agent, which lets you talk to it in its

own dedicated conversation. There's been

a lot of hype around the next update. By

the way, I forgot to introduce myself. I

help developers turn AI into real

workflows. So sub and like it really

helps me provide more value for you.

Anthropic released the native browser

integration for cloud code. That means

you no longer need an external MCP to

use it. Just install the new Chrome

extension and you're good to go. To

install it, we'll use the Chrome

command. After that, click install

Chrome extension. Now it will open the

Cloud website and lead you to install

the plug-in from the store. Next, you

need to configure the websites you allow

it to use. If you want me to cover it in

depth, drop a comment. If you're a heavy

clawed code user like me, you've

probably waited way too long for

conversations to compact. Whether it's

autoco compacting at the context limit

or running the compact command yourself,

it now happens much faster. Another

update is the new stats command. It

shows you how many tokens you used, what

is your longest session, and more. It is

useful because the context window is

calculated for 5 hours. So, if you are

like me and use less, make sure to

trigger sub agents in the background.

These new Cloud Code updates help keep

it at the top in an extremely

competitive AI coding space. But at the

end of the day, what matters most is the

workflows you use. In this video, I'll

show you how to turn Cloud Code into a

great designer. So don't miss it. Until

we meet again, build workflows, not

chaos.