❌

Reading view

Visual Studio Code 1.136 introduces agent merges for pull requests

Microsoft has released Visual Studio Code 1.136, an update to the popular programming editor that previews an Agent Merge feature and introduces two experimental features for agentic coding.

VS Code 1.136 was released September 2 and can be downloaded from code.visualstudio.com.

Agent Merge, a preview feature, helps take a pull request across the finish line, Microsoft said. Agent Merge asks an agent to address review feedback, fix failed checks and merge conflicts, and rerun workflows until the pull request is ready to merge. To use Agent Merge, turn on the setting chat.agentMerge.enabled. Then you can enable Agent Merge for a session by running “Enable Agent Merge for Active Session” from the Agents window or selecting the “Agent Merge” button in the title bar.

VS Code 1.136 also introduces multi-root workspaces, an experimental feature that allows developers to work with GitHub Copilot and Claude agents across multiple project folders in the editor window chat view. Agent hooks remain scoped to a single workspace folder, Microsoft said. If hooks are detected in multiple folders, VS Code prompts the user to select the primary folder from which to load them.

Another experimental feature in VS Code 1.136 is chat backgrounds in the Agents window. This allows users to personalize the Agents window with a theme-aware pattern of built-in VS Code icons or an image of their own. Also new for chat are enterprise controls for dictation data. The new controls allow administrators to manage the dictation model and language-model transcript cleanup through enterprise policies. Microsoft said it was possible to require on-device transcription and disable language-model cleanup, so dictation remains available while preventing dictation data from being sent to cloud transcription or a Copilot model.

  •  

Preparing to Update to Golden Gate

Howard Oakley:

As those new models start shipping on 22 September, the window for the first public release of Golden Gate has narrowed to 15-22 September, with greatest likelihood on the same day as the arrival of those new Macs.

[…]

At the same time as the release of Golden Gate, we should get Tahoe 26.7 and Sequoia 15.8, but it looks increasingly likely that the final version of Sonoma has been 14.8.9, released on 6 August.

Howard Oakley:

As we prepare to flee from the visual horrors of macOS Tahoe at last, this article is a reminder that it wasn’t the first major release of macOS that has had blatant bugs in its interface, although I suspect it may be unique in that those were intentional. While progress in Golden Gate has been limited, I hope you’ll find it rectifies some of the worst errors of Liquid Glass.

Many Macs will be left behind, as Golden Gate drops support for Intel.

Normally, I update around January. With Tahoe I waited until July. This time, I’m considering updating to Golden Gate soon after its release. The downside is that Xcode 26 doesn’t run on Golden Gate, so I would have to drop support for many older macOS versions (about 3% of my customers’ Macs). But it seems like Apple’s going to force that soon, anyway, as one of the next Xcode 27 updates will likely drop support for Tahoe. I want to get off Xcode 26, both to use the newer SDK and because there are various debugging/testing things that don’t work properly.

Mario Guzmán:

I am working on a new app. Right now, I am targeting back to macOS Sequoia. I think that would be a good OS to target but becoming quite old with Golden Gate just around the corner. […] I wonder if I should just target macOS Golden Gate and focus testing on that.

Previously:

Update (2026-09-04): Isaiah Carew:

i’m in the exact same boat. i’d really like to stay on macOS 15 and whatever Xcode works there. it means i can still build things in the old UI and mostly Tahoe and GG respect it.

but recent bug reports from beta testers and the inability to see these bugs on my VM has made me feel very stuck here — like apple has purposefully made it difficult to move forward and support older versions too.

Update (2026-09-11): Howard Oakley:

What if any preparations do you need to make before upgrading or updating then, or in the coming weeks?

Update (2026-09-16): Adam C. Engst:

So who should upgrade immediately, and who should wait? Let’s consider a few broad categories of users.

  •  

Ending the Golden Era for Backward-Compatible Apps

Matthias Gansrigler-Hrad:

I don’t appreciate being forced by Xcode 27 to drop support for macOS 10.13-11.0. It’s my decision which OSes I want to support, not Apple’s. Yes, I can keep Xcode 26 around until submissions require Xcode 27, but what then?

Originally, Xcode 27 was documented as supporting Big Sur on Intel Macs, but now the earliest is Monterey.

I’m frustrated, too, but it’s more honest than the recent releases that claimed to support deployment on older macOS versions when Apple clearly hadn’t tested that it actually worked. I filed bugs, and Apple kept responding that they’d fixed it, when they hadn’t.

Using old versions of Xcode isn’t a great solution because they aren’t supported on Golden Gate. Swift also makes it more difficult to call newer APIs when using an older SDK. You can’t just copy/paste a method prototype or constant value and conditionally use it when running on a newer OS.

Ighor July:

I eventually found a hidden workaround that changes the errors back into warnings. That is good news, but it does not make the concern disappear. The setting is undocumented, absent from the normal Xcode interface, and currently being tested only in a beta toolchain. The larger question is what Apple intends to enforce when Xcode 27 is final and, later, when App Store submission requirements move to its SDKs.

[…]

Apple’s current Xcode system requirements list Xcode 26 with deployment targets beginning at iOS 15 and macOS 11. Yet developers have been able to enter older targets manually. In an Apple Developer Forums discussion about Xcode 26, an Apple product manager explained that the published deployment target range is aligned with simulator support and on-device debugging. The accepted answer confirms that an iOS 13 target can still build even though it falls below the range in Apple’s table.

My own tests went further. Xcode 26.5 compiled a project targeting iOS 9.0. It warned that the target was older than the supported range, but the build succeeded. On macOS, I have compiled current apps with deployment targets as old as macOS 10.9. Xcode warned me, but it still produced working applications.

[…]

For iOS and iPadOS, staying on Xcode 26 is not a lasting option. Apple has repeatedly made a current Xcode and SDK mandatory for new App Store submissions. […] If any one of those conditions fails, iOS and iPadOS developers will have no normal App Store path for publishing new updates that still support versions older than 15.

Previously:

Update (2026-09-07): Léo Natan:

Just want to remind you guys that if you move to Xcode 27, the only “officially” supported and sanction Xcode for GG, UIDesignRequiresCompatibility is no longer respected across the 27 OSes (apps built with older Xcodes still are). So you might suddenly find out you have a lot of work ahead of you, adding support for the dreaded Glass. And 27 Glass is not the same as 26 Glass. That can be an issue if you skipped 26 altogether but still want to support it.

Previously:

Update (2026-09-11): Nick Lockwood:

I mostly ignored the Xcode 27 betas (mainly due to the barely-usable Device Hub) so I didn’t realize the passive-aggressive prompts to drop support for iOS < 15 that you get when submitting apps is being backed up by Xcode 27 refusing to compile apps at all unless you bump the deployment target 😧

  •  

MacVoices #26246: Democratizing Programming: From HyperCard to Claude with Adam Engst (1)

Adam Engst looks back at HyperCard as an early tool that democratized software creation, then connects its legacy to today’s AI-assisted development. He outlines how Claude helped turn an idea for tracking macOS setting changes into a working Mac app, SetShot. Adam discusses Xcode, GitHub, rapid iteration, and the value of visual feedback in his development process, and how AI lowers programming barriers without eliminating the need for thought, judgment, and effort. 

💾

💾

  •  

Researchers get two genetic codes to work at the same time

The genetic code is what life everywhere uses to convert the information contained in DNA into specific protein sequences. With minor variations, the same genetic code is used by every living thing on Earth, suggesting it was already present in the last common ancestor of all of them. It's not an easy thing to change, because so many things in every cell depend on it.

Nevertheless, some preliminary steps have been taken. Researchers have managed to add some new amino acids to a bacterial cell and were able to make proteins that were one amino acid less than usual. But it's a slog; for some of this work, people have had to re-engineer every single gene in a bacterial genome.

Now, researchers have found a way to operate two separate genetic codes simultaneously, avoiding the need to do any work to compensate for altering the code that every protein in a cell relies on. They didn't test it in an actual cell, and it might cause some problems there. But it's a creative solution that should accelerate some synthetic biology work.

Read full article

Comments

© ALI DAMOUH/SCIENCE PHOTO LIBRARY

  •  

Sudoku in Turing-Complete Unicode Transliteration Rules

Nicolas Seriot (Hacker News, Reddit):

The core Unicode algorithms (normalization, casing, bidi, collation) are deliberately bounded, but UTS #35 transliteration rules, under their natural unbounded semantics, are not. This is a result I haven’t found published before.

These rules ship as locale data in ICU, the Unicode library shipped in operating systems, browsers, runtimes, and databases. Whether a given rule file terminates on a given input is undecidable.

[…]

To prove UTS #35 universality, we compile 2-tag systems (Post, 1943), a model proven universal (Cocke & Minsky, 1964), into transliteration rules.

[…]

Transliteration rules were designed to turn “é” into “e”. Three lines of them can compute the Collatz function.

KT_Music:

Inspired by this, I tried creating an implementation that “solves #Sudoku” using only UTS#35 transformation rules 😎

Previously:

  •  

MacVoices #26182: Road to Macstock – Mike Schmitz

Mike Schmitz previews his Road to Macstock session on starting a YouTube channel in 90 minutes, emphasizing creativity, repetition, audience connection, and practical tools over perfection. Mike discusses handling harsh comments, finding personal value in publishing, and using AI thoughtfully as a creative partner. His goal is to help get anyone on YouTube that wants to be there. 

💾

  •  

MacVoices #26181: Flip The Script – MacPaw’s Post-Keynote Perspective and AI-First App Development Strategy

Only a few hours after Apple’s WWDC keynote, members of the   MacPaw leadership team sat down for a conversation about Apple Intelligence, and Siri’s renewed promise. Topics touched on included privacy, developer access to user context, hybrid AI processing, Setapp’s role, and how AI is reshaping app creation, customer support, and software strategy. Participants included Oleksandr Kosovan, Founder and CEO?, Sergii Kryvoblotskyi, Director of AI and Research, Dmytro Melnyk, Chief Product Officer and Grant Belaire, Chief Marketing Officer.

💾

  •  

MacVoices #26169: NAB – RØDE Introduces RodeLink 2 UHF Wireless and AI Podcast Editing

At NAB 2026, Chuck Joiner talks with Ryan Burke, Portfolio Director for RØDE about the new RodeLink 2 UHF wireless system, developed with Lectrosonics expertise. The discussion covers interference-resistant UHF performance, 32-bit float recording, timecode, adaptive power, battery life, and removable storage media.  Ryan also provided a look at the new RODECaster Studio AI audio editing app for podcasters. 

💾

  •  

MacVoices #26155: NAB – Jim Tierney of Digital Anarchy on Beauty Box Video and ShotNotes

On the show floor at NAB in Las Vegas, Jim Tierney of Digital Anarchy discusses ShotNotes, a Premiere Pro panel that keeps project notes, time codes, links, timers, and collaboration details inside the edit instead of scattered across documents or sticky notes. He also previews Beauty Box Video AI development and explains where generative AI can help video pros, where traditional AI still shines, and why AI is useful but not a magic bullet. 

💾

  •  

Sessões do Claude Code agora podem conversar entre si; modo automático vira padrão

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
Novidade no Claude Code: agora suas sessões podem trocar mensagens.

Em vez de ter que se explicar novamente em outra sessão, agora você pode pedir ao Claude para fazer isso. Ele envia um resumo (não seu histórico ou arquivos), e a outra sessão o recebe durante a execução da tarefa.

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.

Pesquisa

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.

  •  

Airtable joins Evernote, Brightcove, WeTransfer and AOL in Bending Spoons portfolio

Bending Spoons has snapped up Airtable to add to its portfolio of software companies, alongside AOL, Evernote, WeTransfer, Brightcove and Vimeo

Airtable made its name as a builder of low/no code database services, aimed particularly at non-technical staff, but is now one of many vendors facing financial difficulties in the face of the SaaS/AIpocalypse. The arrival of AI coding tools, which offer non-technical employees more flexible ways to build business applications, has hit demand for its services.

Bending Spoons bought Airtable in a deal it valued at just $1.285 billion, a far cry from the $11.7 billion Airtable was worth at its peak.

Bending Spoons has built its portfolio by buying once-successful companies like Airtable that have struggled to cope with newer, nimbler competitors or failed to adapt to emerging technologies. Bending Spoons takes these companies, cuts costs and markets them aggressively with the goal of returning them to profitability.

“Airtable is a pioneering brand reshaping how teams organize data and manage critical workflows. We’re committed to investing in Airtable for the long run, and doubling down on its core strength: bringing teams and workflows together in one flexible workspace. We plan to expand what can be done across the full spectrum of work and make Airtable even more valuable to customers at every scale,” said Luca Ferrari, Bending Spoons CEO and co-founder.

  •  

Visual Studio Code 1.132 advances built-in dictation

Visual Studio Code 1.132, the latest version of Microsoft’s popular, open-source code editor, has been released. The brings improvements to built-in dictation, side chats, and support for commenting on web elements in the integrated browser.

VS Code 1.132 was released August 5. The update can be downloaded for Windows, Linux, and macOS at code.visualstudio.com.

With VS Code 1.132, the built-in multilingual dictation function lets developers dictate in multiple languages using an on-device model that follows language preference or detects the language automatically. The built-in dictation converts speech to text in chat inputs, editors, and terminals. Dictation now uses multilingual Nemotron 3.5 as the default on-device model. Plus, terminal dictation now applies shell-aware cleanup, so spoken commands preserve shell syntax.

Also in VS Code 1.132, developers can open a side chat by typing /bt in the chat input. A side chat shares the context and prompt cache of the primary chat, but allows developers to ask the agent questions about the current turn without interrupting the turn. Similarly, developers can select text in a chat response to ask contextual questions about that response.

Other new capabilities and improvements in VS Code 1.132:

  • The integrated browser adds support for selecting web page elements and annotating them with agent feedback. Users can trigger this mode by using the workbench.action.browser.addElementCommentToChat keyboard shortcut.
  • Active development continues on the agent host, a new VS Code feature that lets users connect to the same agent session from multiple VS Code windows. The agent host runs agent harnesses such as Copilot, Claude, and Codex in a dedicated process based on the Agent Host Protocol (AHP).
  • In the previous release, Microsoft introduced the hybrid Markdown editor, which combines rendered Markdown with in-place editing and agent-actionable comments. In this release, Markdown diffs can be opened in the hybrid Markdown editor. 
  • Expanded terminal output in chat now reflows to the available width as the view is resized. Previously, output used a fixed width, which caused lines to wrap too early and left unused space in wider views.

  •  

The Utility App Flood Won’t Last

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.

  •  

Meta lança Muse Code, agente de programação alimentado pelo novo modelo Muse Spark 1.2

A Meta lançou hoje o Muse Code, seu primeiro agente de programação — o qual rivalizará com soluções como o Claude Code (da Anthropic) e o Codex (da OpenAI).

A nova ferramenta, assim como os assistentes supracitados, facilita a criação de aplicativos em uma única interface, permitindo gerenciar conjuntos de agentes digitais impulsionados por IA que auxiliam no processo de desenvolvimento de software.

Releasing Muse Code in beta today. It's a terminal coding agent that takes on complete software engineering tasks across large repos: planning changes, writing code, validating the results. Powered by Muse Spark 1.2, a coding-focused model update. pic.twitter.com/xqavk41w6v

— Mark Zuckerberg (@finkd) August 5, 2026
Estamos lançando o Muse Code em versão beta hoje. Trata-se de um agente de programação via Terminal capaz de executar tarefas completas de engenharia de software em grandes repositórios: planejar alterações, escrever código e validar resultados. Ele conta com a tecnologia do Muse Spark 1.2, uma atualização de modelo focada em programação.

Ainda que disponível inicialmente em beta, o Muse Code pode ser usado para realizar uma ampla variedade de tarefas, planejando alterações, escrevendo código e validando os resultados. Desenvolvedores podem utilizá-lo por meio de uma modalidade de pagamento conforme o uso (pay-as-you-go).

Ao contrário do Codex e do Claude Code, atualmente não existe um aplicativo dedicado para o Muse Code. Desse modo, ele pode ser instalado no macOS e no Linux a partir de um comando de uma única linha:

curl -fsSL https://dev.meta.ai/install.sh | bash

Ele também opera em conjunto com o mais novo modelo de IA da empresa, o Muse Spark 1.2 — o qual foi desenvolvido e treinado juntamente com o novo agente de programação, o que melhora o desempenho geral.

O Muse Spark 1.2 é uma atualização do Muse Spark 1.1, lançado no mês passado, trazendo melhorias na geração de código, depuração de cenários complexos, compreensão da base de código e fluxos de trabalho de ponta a ponta para desenvolvedores. O novo modelo também amplia significativamente o poder computacional de treinamento para tarefas de programação.

Muse Spark 1.2 has improved coding capabilities compared to its predecessor. We significantly scaled up training compute on coding tasks while expanding training environment diversity, delivering improvements in code generation, complex debugging, and end-to-end developer… pic.twitter.com/0cTSBe4paj

— AI at Meta (@AIatMeta) August 5, 2026

O Muse Spark 1.2 apresenta recursos de programação aprimorados em comparação com sua versão anterior. Aumentamos significativamente a capacidade computacional de treinamento em tarefas de programação, ao mesmo tempo que expandimos a diversidade de ambientes de treinamento, proporcionando melhorias na geração de código, depuração complexa e fluxos de trabalho de desenvolvimento de ponta a ponta.

O modelo foi treinado com o Muse Code para otimizar o desempenho quando utilizados em conjunto, com foco em tarefas como geração de repositórios completos, projetos de grande porte e pesquisa automatizada.

O Muse Spark 1.2 já está disponível no Muse Code e na Meta Model API.

  •  

Como gerar um código QR para uma página no Mozilla Firefox pelo Mac

Além de compartilhar uma página da web usando um link normal, o navegador Mozilla Firefox também permite enviar um endereço da web de outra forma.

Mais precisamente, trata-se da geração de um código QR (QR code) — que pode, posteriormente, ser lido a partir de qualquer câmera ou compartilhado em uma postagem, por exemplo.

Veja como fazer isso no seu Mac! 👨‍💻

  1. Com o Firefox aberto no seu computador, siga um dos seguintes procedimentos:
    • Clique com o botão direito em cima da aba;
    • Vá até “Arquivo”, na barra de menus;
  1. Selecione “Compartilhar” e “Gerar código QR…”.
  1. Clique em “Salvar” para fazer o download do código ou em “Copiar” para que ele seja copiado para a área de transferência.

  •  
❌