Good day, here's your AI digest for August 21, 2026. The big enterprise AI story today is model routing. AT&T is pushing more internal AI work toward open models and reserving premium systems for harder jobs. The claim is not that cheaper models suddenly match the best frontier systems everywhere. The claim is more operational: when a company has thousands of repeated tasks, it can measure which ones are routine enough for a smaller model, then route only the hard work to the strongest available model. Internal comments cited roughly 40 percent of employee AI usage moving to open models, with some coding workloads seeing large cost reductions and only a small quality tradeoff. The shape of the market is changing from picking one default model to building a dispatch layer that chooses per task. Ramp launched a model router of its own called Router. It can select a model based on cost, benchmark performance, or task difficulty. That makes the router itself part of the product surface, not just infrastructure hidden behind an API. Teams are starting to treat model choice like load balancing, database selection, or search ranking: a decision that should be evaluated continuously rather than hardcoded once. The hard part is measurement. Without evals tied to real work, routing becomes guesswork with a nicer interface. ChatGPT added an Apple Messages plugin for ChatGPT Work and Codex on Mac. The feature can search message conversations, catch users up on threads, and draft or send replies after the user connects the account. This is a notable expansion because messaging data is one of the richest private work contexts people have. It also raises the bar for permissions, auditability, and mistakes. An assistant that can read and act inside personal or work messages needs clear boundaries, predictable confirmation flows, and strong separation between drafting and sending. OpenAI also published new material around GPT-Image-2 generating transparent-background PNGs directly. That sounds narrow, but it removes a common production step for designers, marketers, and developers building reusable assets. Product cutouts, interface graphics, campaign elements, and presentation images can be generated in a format that is ready to layer into real layouts. The useful part is not only image quality. It is that the output format fits downstream work without a manual background-removal pass. ChatGPT Sites is being presented as a way to turn an idea, draft, or compatible local project into a hosted website directly from ChatGPT. It can save reviewable versions, deploy a live URL, and add capabilities like storage, sign-in, analytics, collaborators, or a custom domain. The key operational detail is that deployment URLs are production, so versioning before deployment becomes part of the workflow. This pushes conversational software building closer to a managed release process instead of a one-off prototype. Slack introduced Slack Code, which puts coding agents inside shared code channels. A project can have human teammates and agents in the same room, live previews, steering from non-engineering stakeholders, human approval before deployment, and an archived channel as the record of how the build happened. The interesting move is that Slack is not trying to be the best coding agent. It is trying to own the room where agents, developers, product people, and reviewers coordinate while software changes are made. Asana said it used OpenAI Codex to remove an outdated testing framework in two weeks for about twelve thousand dollars. The company had previously estimated the work at five years and six million dollars. Treat the numbers as a case study rather than a universal benchmark, but the pattern is clear: migration work with broad mechanical repetition is becoming a prime target for coding agents. These jobs still need human review, test strategy, and rollback discipline, but the economics change when an agent can keep grinding through similar edits across a large codebase. Claude Code added a Concise output style that leads with the result and stays short by default. The change comes after complaints about recent output quality and verbosity. It is a small product update with a broader signal behind it: developer tools are starting to tune not just raw capability, but conversational shape. When an assistant is embedded in coding work, too much explanation can become friction. The best interface is often the one that gives the answer, shows the changed files, and leaves room for the developer to ask for deeper reasoning only when needed. Perplexity launched an Agent API that puts 41 models from nine providers behind one endpoint, with web search, finance search, fetching, and sandboxed code execution included. The product sits in the same larger movement as routers and agent platforms: developers want one programmable surface for model access, retrieval, tools, and execution. The challenge is trust. Once an API combines model output with live web access and code execution, observability, reproducibility, and guardrails become core features rather than optional extras. Grok Build was opened as a prompt-to-app system for apps, games, websites, and dashboards. It can publish with its own domain and includes a coding agent with subagents, browser access, databases, secrets, and GitHub export. That places it in the growing category of agentic app builders that aim to move from idea to deployed product in one environment. The category is crowded, but the direction is consistent: prompts are becoming project starters, while durable value depends on source control, secrets handling, review flows, and the ability to keep improving the thing after the first generation. Adobe rolled out Firefly audio generation tools to all users, including music, voiceovers, and sound effects cleared for commercial use. This matters for software teams building media-heavy products, games, tutorials, ads, onboarding, or support content. The value is not just generating a sound quickly. It is reducing uncertainty around rights and reuse, which is often the reason teams avoid generated media in production. Taken together, today points to a more practical phase of AI tooling. The center of gravity is shifting from impressive demos toward routing, permissions, release controls, shared workspaces, output style, and production-ready formats. The tools are getting closer to the places where software is actually planned, built, reviewed, shipped, and maintained. This has been your AI digest for August 21, 2026. Read more: - AT&T using open models to curb AI costs: https://www.theinformation.com/newsletters/applied-ai/t-using-open-source-models-curb-anthropic-bills - Ramp launches Router: https://techcrunch.com/2026/08/20/ramp-launches-its-own-ai-model-router-called-router/ - ChatGPT Apple Messages plugin: https://x.com/ChatGPT/status/2090499359641329950 - GPT-Image-2 transparent image assets: https://developers.openai.com/cookbook/examples/multimodal/transparent-image-assets-for-campaigns-and-presentations - ChatGPT Sites: https://learn.chatgpt.com/docs/sites?surface=app - Slack Code: https://www.salesforce.com/introducing-slack-code/ - Asana Codex migration: https://openai.com/index/asana/ - Perplexity Agent API: https://www.perplexity.ai/hub/blog/agent-api-one-place-to-build-with-llms-the-web-and-agents - Grok Build: https://x.ai/news/grok-build-for-everyone - Adobe Firefly audio tools: https://blog.adobe.com/en/publish/2026/08/20/adobe-firefly-expands-its-creative-ai-studio-generate-music-speech-and-sound-effects-in-one-place