The Tokenpocalypse Is Here: Companies Are Scrambling To Stop Spending So Much on AI

There's a fun anecdote from Accenture (apparently via leaked meeting audio recordings) in this 404 Media piece from June 24th:

“We’re seeing from some of the data internally at least that it’s actually not our engineers that are driving the token consumption. It’s a lot of the non-engineers that are doing some of those behaviors [...] you were talking about,” Justice Kwak, Accenture’s agentic AI strategy lead, said [...]

Stuart Henderson, Accenture’s client group lead, interrupts. He jokes he hopes Kwak didn’t just convert a PDF into images and then into markdown files. “I’m learning that’s one of the big token chewers,” Henderson says. “Turning PDFs into markdown: is that right?”

That’s when Kwak says that’s what Accenture’s own data shows.

Maybe if Accenture figure out that PDFs are a terrible medium for communicating information they'll be able to push that message out to the rest of the business world too!

Via @404.media on TikTok

Tags: pdf, markdown, ai, generative-ai, llms, ai-misuse

OpenAI is sharing preliminary cybersecurity evaluations for Astra and the steps we’re taking to strengthen safeguards and security controls.

Auto mode is now the default in Claude Code for Pro, Max, and Team plans

Running auto mode in production

Back in 2020, we committed to Manifest Version 3 (MV3) as the future direction of the Chromium extensions platform. Since then, we've worked with developers, listened to feedback, and continued evolving Microsoft Edge toward a more secure and performant extensions foundation. Today, we're announcing the next phase of that journey. With 95% of the top MV2 extensions on the Edge Add-ons store already moved to MV3, the ecosystem has made meaningful progress. Beginning in August 2026, Microsoft Edge will start the consumer transition away from Manifest Version 2 (MV2) extensions and toward MV3. Our goal is to complete the consumer transition by the end of 2026, with enterprise deprecation following in early 2027.

The ecosystem is ready for the next step

This is a significant milestone for the extensions community, and one we have approached deliberately. Microsoft Edge continued to support MV2 extensions so developers, enterprises, and users who depend on specific extensions had more time to adapt. The move to MV3 has come a long way. MV3 offers security and performance improvements over MV2, and developers across the ecosystem have done the work to modernize their extensions. To put some numbers around the progress the ecosystem has made, there are only 58 MV2-based extensions in the Edge Add-on Store with any meaningful usage. Of these, only three don't have a publicly available MV3-based extension already available. Developers and users have spoken: the vast majority of extensions of all types—from password managers to VPNs to ad-blockers—have successfully transitioned to MV3 with no loss of customer functionality. We're committed to working with all developers with MV2-based extensions to smoothly move their users to MV3 extensions.

What to expect next

Starting in August 2026, a subset of users with MV2 extensions installed will begin to see notices on the Manage Extensions page (edge://extensions) and on Microsoft Edge Add-ons product detail pages. The very few developers with an MV2 extension will see a similar notice in Microsoft Partner Center, along with a direct outreach from our team to help them complete the migration. Over the next few months, MV2 extensions will be gradually turned off by default. Users will be notified in advance and directed to recommended MV3 versions where available. These changes will start in the Canary, Dev, and Beta channels and gradually broaden to Stable in the following months, with the goal of completing the consumer transition by the end of 2026. Managed devices will not be affected during the consumer rollout. Enterprise deprecation will follow in early 2027. We will keep the community updated on the status of the rollout on a regular cadence.

What developers should do now

For developers who still maintain MV2 extensions, now is the time to complete the move to MV3. Ship an MV3 version of your extension and submit the update through Microsoft Partner Center. The Migrate an extension from Manifest Version 2 to V3 guide outlines the required changes. This progress only works because of the developers who have already moved their extensions to MV3 and shared feedback along the way. Thank you for your partnership and continued support in improving Microsoft Edge. If you run into questions during your migration, please reach out to the Microsoft Edge extensions team. We're happy to help.