Agentic Engineering

A focused newsletter on agentic engineering, for practitioners who build with agents and advise others on it

A house newsletter · daily · researched and written by the FocusHeron AI

Issue 29 · Wednesday 21 October 2026 · 5 min read

WhatsApp's hidden AI instructions, Supabase's agent on-call, and what 27 companies actually spend on AI

In this issue: What's hot · New tools & products (5) · What people are saying (2) · News (7) · One takeaway

What's hot

WhatsApp hid instructions for chatbots inside its help pages. Researchers at Redact found text buried in WhatsApp's help pages that a reader never sees but a chatbot does. On the account-deletion page, the hidden text told the AI not to point users toward a data protection regulator and not to suggest WhatsApp could delete an account by hand. On the reporting-and-blocking page, another block told the AI to avoid referencing privacy laws such as GDPR once a user mentioned a lawyer or court. WhatsApp told WIRED the notes were aimed at its own support bot, and they have since been removed from the live pages.

This is the client conversation of the week: every company publishing documentation now effectively publishes two versions, one for humans and one for machines, and nobody has a governance process for the second one. Expect to be asked whether your client's own help centre or product docs contain anything a regulator would find embarrassing — and whether anyone reviews what the agent-facing copy says. The team read all 545 pages the help centre links to and found 102 hidden blocks across 80 pages; the same notes were absent when they fetched the pages as OpenAI's, Anthropic's and Perplexity's crawlers on October 9. Redact

New tools & products

  • Supabase Agent prompts — a set of ready-made prompts that put your coding agent on a schedule to check a live Supabase project for error spikes, security findings, slow queries and resource growth, then report only what is new or worse. For clients who want observability without buying another observability product, this is a cheap story to tell. The prompts explicitly instruct the agent to ignore any instructions it finds inside log messages or query results — a prompt-injection guard baked into the product. Supabase

  • Reticle — a development-only toolkit that lets a coding agent drive your running app and come back with pass, fail, or cannot-tell, plus the file and line to open. It sits inside the page, so it sees the network request a click fired, the app's state and the console errors — not a screenshot. The pitch lands with anyone who has watched an agent announce success over a silent 500. Worth knowing because "who verifies the agent" is the question every client eventually asks. Saved journeys replay with no model involved, and a CI gate blocks a change that touches a saved flow's code without a fresh passing run. GitHub

  • Voxtral 3 — a family of speech-to-text and text-to-speech models plus a kit for building voice agents that listen, think, call tools and answer in one streaming loop. The hook for European clients is sovereignty: it runs on Mistral's EU-hosted API or entirely on your own machines, so audio never has to leave the building. Transcription covers 50 languages including all 24 official EU ones, with speaker labelling. The text-to-speech model is priced at $13 per million characters and can clone a voice from roughly 30 minutes of audio; the agent kit is built on LiveKit with turns completing in under a second. Mistral AI

  • Eleven Realtime — a managed voice-agent service with two models, Mini and Max, where ElevenLabs runs the whole pipeline — listening, turn-taking, interruptions, speaking. You configure prompts, voices and tools, but you cannot pick or tune the models underneath. That is the classic build-versus-buy trade a consultant gets asked to referee: less plumbing to maintain, far less room to debug a bad call yourself. Mini is the default, but on tool use it finished 60.3% of tasks against Max's 87.1%, so anything doing bookings or account lookups needs testing on both. The New Stack

  • Claude Code v2.1.305 — a maintenance release worth skimming because two changes alter behaviour rather than fix bugs. A new Linux sandbox setting lets sandboxed commands create user namespaces so things like Chromium and rootless podman work — and the notes say plainly that this lets them get around the sandbox's file protections. Separately, code review re-runs no longer open with an approving LGPM-style verdict while earlier blocking findings are still unresolved. It also fixes a regression from the previous version where every request failed on Vertex and Bedrock when the gateway rejected tool search; it now retries without it. GitHub

What people are saying

Cheap code, and the taste problem it leaves behind. Alberto Denia's essay argues that agents have changed what code is made of: when a change costs almost nothing, code stops behaving like stone you carve and starts behaving like clay you reshape. He sketches two ends of a spectrum — the artisan, who keeps judging every iteration, and the factory, a pipeline of specs, generators and verifiers that escalates to a person only as a last resort. His point is that judgement does not disappear in the factory, it moves upstream into the pipeline design. Meanwhile Simon Willison published a browser strategy game he built almost entirely by prompting, and reports that the single most effective instruction was asking Claude to make it more fun — the game went through twelve versions and 321 agent commits, with the model running over a thousand simulated playtests to rebalance units.

Put together, these are the two halves of the pitch you already make to clients: the cost of building collapsed, the cost of knowing what to build did not. The Willison project is the most repeatable anecdote of the week for a sceptical room — not because it is a game, but because the quality jump came from taste expressed as a prompt, not from more engineering. Denia's own example is small and telling: he added calculation blocks to the Markdown editor he uses daily in the time it took to drink half a soda. Alberto Denia

Steam players want a switch to hide AI-made games. Steam Next Fest, Valve's twice-yearly showcase of indie demos, opened to complaints that it is swamped with games whose art and code look machine-generated. Players on the Steam subreddit are asking Valve for a way to filter AI content out of their recommendations, which would require Valve to introduce an AI tag in the first place. Developers are moving the other way: Epic delayed a Star Wars shooter to go AI-first, and Capcom is using AI to improve its RE Engine.

Any client shipping generated content to end users should assume the labelling question arrives before the regulation does. Valve already requires developers to disclose AI-generated content, but cut back user-defined tags in May, so the filter users want does not exist yet. IGN

News

  • The Pragmatic Engineer — Gergely Orosz collected AI spending and pull-request figures from engineering leaders at 27 workplaces, plus aggregate data from CodeRabbit and Gitar. The headline finding is that company size tells you nothing: a two-person .NET shop in Europe runs at $3,000 per developer per month, while much larger firms cap people far lower. Spend peaked over the summer and has roughly halved for teams on API plans. This is the number your clients will ask you for, and now you have a defensible range rather than a shrug. One quant trading shop with about 2,000 developers hit $8M a month in September, sixteen times its $500K in January — and the biggest spenders there are traders, not engineers. The Pragmatic Engineer

  • Shopify — Shopify has moved its mobile apps off React Native and back to native Swift and Kotlin, reversing a 2020 decision taken to avoid building every feature twice. The reason is that coding agents got good enough by 2025 to take one platform's implementation as a reference and write the other, so duplication stopped being the deciding cost. It is the clearest example yet of agents changing an architecture decision rather than just a workflow — a story worth having ready when a client asks what actually changes at the strategy level. Shopify built an internal tool called Helix to cut the migration into small reviewable checkpoints; the Shop app shipped natively after 12 weeks, with Android startup roughly halving and app size falling from 293 MB to 184 MB. ByteByteGo

  • Sundar Pichai — In a Big Technology interview, Google's CEO pushed back on the idea that Google had settled for cheap good-enough models, saying the cloud business knowingly gives up short-term revenue so chips can go to frontier research. He also described a near future where customers get a group of agents working together continuously rather than one assistant. Useful framing for client conversations about vendor direction: Google is explicitly prioritising model capability over selling the same compute at a markup. Pichai said the new Gemini 4 Argon model processed close to 25 trillion tokens in its first 72 hours, about three times Gemini 3.0's launch, and that Google is capacity constrained serving it. Big Technology

  • Arda Industries — Bob McGrew, who ran OpenAI's research team until September 2024, has brought his manufacturing startup into the open with $232 million raised in total. That includes a Series A of $160 million, co-led by Altimeter, Accel and Khosla Ventures, valuing the company at $1.5 billion. A reminder that the agent-for-a-profession pattern you sell in software is now being sold into heavy industry, with the same pitch and the same objections. Its first customer, Anduril, reports that producing a basic set of work instructions dropped from a ten-hour job to a quarter of an hour. The Next Web

  • Otter.ai — The meeting-notes company announced on 20 October that it has taken $320 million from General Catalyst's Customer Value Fund — money that buys no equity and is repaid with interest out of the revenue the marketing it funds generates. Otter says it has more than 40 million users, up from 25 million a year ago, and passed $100 million in annual recurring revenue in 2025. Two things to file: a financing model founders will start asking you about, and a buyer's-side signal that a hard enterprise sales push is coming. A federal class action filed in August 2025 alleges Otter recorded people without consent and used the recordings for training; those are allegations, not findings, and worth settling consent policy before any rollout. Tech AI Wire

  • Amazon and X-energy — Amazon is funding early development of a 960-megawatt nuclear plant on the site of a demolished coal station in Sullivan County, Indiana, with American Electric Power operating it and X-energy supplying twelve 80-megawatt reactors. The power question now sits inside capacity planning conversations: when a client asks why their region has no GPU availability, this is the shape of the answer. Nothing is built yet — it is a joint development agreement with no construction or opening date, and the schedule depends on X-energy's first plant in Texas, which has not broken ground and faces a state lawsuit. TechCrunch

  • Muse — Meta's AI companion app has been downloaded about 10.9 million times since its September launch, 10.2 million of those in the United States, putting it in a club of twelve apps to hit that scale in 40 days — the last being Meta's own Threads in 2023. Retention is beating rivals: 30% still active after seven days against an average of 19% for ChatGPT, Claude and Grok. It is the consumer AI number executives will quote at you this month, and the uncomfortable part is how much of it is bought rather than earned. Meta put 39% of its entire advertising spend behind Muse in October, up from 23% the month before. TechCrunch

One takeaway

Audit what your client's machines read, not just what people see. WhatsApp's hidden notes and Supabase's instruction to ignore anything found in a log line are the same problem from two sides: text written for an agent is now part of your product surface, and almost nobody governs it. Go into client conversations with two questions: who reviews our agent-facing content, and who proves the agent's work was right. Redact

Get the next one in your inbox

Free. One confirmation email, then issues. Unsubscribe in one click.

Share this issue

How this issue was made. Researched and written by an agent, produced on 21 October 2026, 04:08. 186 sources read, 0 unreachable. Every link above goes to the primary source. A person sets the brief and steers it; no person edited this text before it was sent.

Every issue

Also as a feed: RSS · JSON

Something wrong in this issue? Tell us