Anthropic will extend support for watermarking AI generations for older models as well.

A Anthropic anunciou nos últimos dias duas novidades bem interessantes para o Claude Code, sua plataforma agêntica de codificação com inteligência artificial (IA) generativa: as conversas entre diferentes sessões e o modo automático como padrão para alguns de seus planos.

Começando pela primeira novidade supracitada, ela permite que o Claude envie informações de uma sessão para outra num mesmo computador ou responda a sessões em outras máquinas — algo que pode ser bastante útil quando mais de uma sessão está trabalhando num mesmo projeto.

O recurso pode ser usado, por exemplo, quando há uma mudança que quebra o sistema como um todo e cuja resolução depende de algo executado em outra sessão — ou simplesmente quando alguma delas precisa saber de uma decisão de design ou de um resultado de testes.

Por ora, no entanto, apenas texto simples é suportado, de modo que nenhum arquivo ou o histórico da conversa é transferido entre as diferentes sessões. Uma sessão também não pode aprovar comandos originados de outras sozinha — sempre é requerida a autorização do usuário para tal.

New in Claude Code: your sessions can now message each other.

Instead of having to re-explain yourself in another session, you can now tell Claude to do it. It sends a summary (not your history or files), and the other session picks it up mid-task. pic.twitter.com/PtNsfXeQXP

— ClaudeDevs (@ClaudeDevs) August 7, 2026

O Claude pode decidir enviar uma mensagem por conta própria se julgar necessário, ou o usuário pode solicitar explicitamente que ele informe algo a outra sessão — inclusive, é possível definir se elas devem ser aceitas ou recusadas automaticamente ou se devem requerer aprovação.

Modo automático como padrão

Um dos recursos mais interessantes do Claude Code é o modo automático, que permite à plataforma usar uma espécie de “classificador de segurança” para decidir se prossegue ou não com determinada tarefa, sem precisar a todo instante solicitar a permissão do usuário.

Com o modo automático, que antes era opcional, o Claude pode trabalhar sozinho por períodos muito mais longos e sem qualquer interferência humana — o que permite que seus modelos realizem tarefas complexas durante horas e entreguem um trabalho mais completo ao fim da sessão.

Pesquisas feitas pela Anthropic indicaram que o modo automático também tende a deixar o desenvolvimento mais seguro, já que desenvolvedores costumam aprovar 97% dos pedidos de permissão por reflexo (sem revisão), e bloqueiam bem menos prompts perigosos que a ferramenta (acima).

Com isso, esse modo agora passará a ser o modo padrão do Claude Code nos planos Pro, Max e Team — a partir de 14 de agosto. Como consequência dessa mudança, a Anthropic também deixará de cobrar dos usuários desses planos pelo custo computacional desse classificador.

The App Store is evolving at a breakneck pace not seen since its earliest days. We saw the first glimmers of what was to come early in 2025, but it wasn’t until late last year that the tsunami of apps developed with the help of AI agents really took hold.

Since then, veteran developers are releasing new apps and updating existing ones faster than ever, and new developers are releasing their first apps in droves. Today, supply is dramatically up, demand is flat, and quality is seemingly simultaneously up and down, depending on where you look.

How these forces play out long-term is anyone’s guess, but it’s worth examining because, just as Federico’s link to Bryan Irace’s post about agentic coding tools foreshadowed the rise of tools like Codex and Claude Code, today’s trends are sparks that have the potential to become tomorrow’s App Store wildfires or simply fizzle out.

Utility apps are on the front lines of this change. The TechCrunch story I linked in April picked up on this trend:

Another interesting tidbit from Appfigures is that the Utilities app category moved up the top five chart.

If anything, the trend has accelerated in the months since.

It’s not surprising at all that utility apps have taken off. They’ve been a staple of new developers since long before agents came along. That’s because many are UI wrappers around command line tools. That isn’t a knock against the developers of those apps; most users don’t want to open Terminal to convert a video or audio file to another format using ffmpeg, for example. By building a great UI around command line tools, developers have made them far easier to use.

However, the relative simplicity and narrow scope of many utility apps have made them a natural fit for AI agents, too. That’s why the App Store (and my inbox) is deluged with Mac menu bar and single-screen iPhone and iPad utility apps.

On the one hand, the abundance of utilities has been great for users. More choice means you’re more likely to find the app that perfectly fits your needs.

On the other hand, though, I don’t think what’s happening in the category is sustainable and expect to see it dramatically shift again in the coming months. As we’ve seen from reporting by The New York Times, app supply is outstripping demand by orders of magnitude, which will drive down prices. That alone is likely to cause the utility app market to shrink. But there’s more to it than that.

Remember, the demand shifts that The New York Times reported, based on Sensor Tower numbers, are for the entire App Store, where download numbers have grown 2-3% this year and last. I expect utility downloads to actually shrink in the coming months – again, because of agents. Utilities, especially simple ones, are exactly the sorts of apps that are becoming trivially easy for power users – the very users these utilities are made for – to create themselves. From frontier labs‘ model improvements to a growing number of app-building tools from those same labs and third parties, it’s never been easier to build a web or native app yourself.

And although I agree with people, like Nilay Patel, who say the notion that everyone will build their own software is overblown, the utility market is different. Your average person is not downloading apps to adjust the frame rate and file format of a video or downloading YouTube videos to watch later. But those are exactly the sort of things that people who are using agents are doing with them, whether they’re having an agent do those things directly via a command line tool in an app like Codex or Claude Code or building an app to do the same thing. That’s going to put even more pressure on the category.

That said, I think there will always be a cohort of users who would rather pay for an app than build it themselves, so I’m not predicting the demise of utilities in general – just the end of today’s frothy market. I also think there remains a place for simple utilities that solve hard problems with clever solutions. Not every utility is a UI wrapper for a terminal command. Plenty of apps feature original solutions or thoughtful and unconventional remixes of disparate tools.

Utilities aren’t going away, but just like other App Store deluges, the trend will recede. It’s just that this time, it’s likely to flip faster than usual.

Claude Code’s Mac desktop app has added Apple simulator support, and although it’s billed as “iOS Simulator Support,” it actually works with any iOS, iPadOS, visionOS, or watchOS simulator you have installed.

The process of setting up a simulator is simple. A new button with an iPhone icon appears when you open an existing project. Click it and a new iPhone simulator pane opens to the right by default. However, clicking on the name of the simulator reveals a list of every available simulator. You can also run multiple simulators at once, but that immediately made my aging M1 Max Mac Studio start to chug a little.

Once you have the simulators that you want open, simply ask Claude Code to run and test your app, and it gets to work, building the app, installing it in the simulator, opening it, and poking around. I loaded up a simple word game I’ve been playing with, and after a few minutes, Claude Code found a UI bug while controlling the simulator. I asked it to fix the issue, which it did, then tested and committed. My testing has been limited, but so far it looks like a simple, effective loop.

It’s also worth noting that Claude Code is running the simulator directly inside the Claude app. This is not computer use, meaning windows aren’t going to be opening and getting in your way as you work on something else. All in all, the addition of the simulator, like the inclusion of an in-app sandboxed browser a couple of weeks ago, is a great update to Claude Code.

A Anthropic implementou no Claude Code a possibilidade de testar aplicativos para iPhone em um painel interativo do iOS Simulator.

Aos interessados, será possível construir aplicativos para iPhones diretamente do Claude Code Desktop a partir da versão 1.24012.0 do app. A integração possibilita ainda a utilização de toques, gestos e atalhos da solução nativa da Apple para simular o iPhone.

Claude Code on desktop now works with the iOS simulator.

Build and run your iOS app, and the simulator opens in a panel right next to your conversation. Available today in public beta. pic.twitter.com/su4IguzPVb

— ClaudeDevs (@ClaudeDevs) July 21, 2026

O recurso é exclusivo da versão para macOS do Claude Code (levando em conta, claro, a disponibilidade do Simulator da Apple), e é necessário ainda ter o Xcode com a plataforma iOS instalada.

Para executar um determinado app, basta abrir o projeto na aba “Code” do Claude Code Desktop, pedir à inteligência artificial (IA) para testar o aplicativo e… pronto. É possível que no primeiro acesso o app solicite uma permissão para seguir com a instalação. O painel dispensa o uso do Computer Use (com exceção da versão em CLI), controlando diretamente o uso do iOS Simulator.

Ainda em beta pública, a ferramenta exige sessões locais, pois sessões em nuvem não são capazes de acessar simuladores instalados no Mac. A novidade está disponível para usuários dos planos Pro, Max e Team.