Friday, 2 October

Today’s Stratechery roundup stitches together the week’s agent-interface arguments, not a sixth agent deployment: Thompson’s claim that agents could aggregate apps; his question whether Meta should chase enterprise; and his attempt to make sense of OpenAI’s Dots and product tiers. Read it as an index to the three dated originals, not as an independent test of adoption, software maintenance or customer outcomes.

“who is the customer?”

The cross-project coordinator may become a product in its own right. Thompson says he uses a dedicated Claude thread to keep track of work because Codex projects organize threads *within* a project but leave the overall queue to the human; he reads the new Dot as an intended chief of staff. OpenAI confirms cloud workspaces and a gradual, restricted Dot rollout—not that it catches an unaddressed review comment or keeps a multi-agent feature coherent. This meets Dru’s planning question more than another agent-count demo.

“then the ultimate coordinator of everything you are doing is you”

An agent that ‘knows your whole life’ may be the wrong unit for software-team work. In his September 29 update, Ben Thompson argues that Meta’s just-announced enterprise push could compromise the consumer agent by collapsing work and private identities. Meta did announce Muse Code and other enterprise tools; the claimed strategic incompatibility is Thompson’s judgment, not a measured failure. The design question for a shared team agent is where personal memory, customer data and action authority must stop.

“having separate identities for your private life and work life is not just healthy”

A concrete challenge for Dru’s ‘throw away discovery code’ rule—but only at the *personal UI* scale: Ben Thompson asked Muse to sort his Instagram recipes, rejected its first PDF, and had a usable private browsing interface about five minutes later. He calls such interfaces disposable; that is not evidence that a team should ship prototype code or that the app survives a month of use. The change of format came from actually trying the first result.

“It’s effectively disposable, because it’s infinite.”

Stratechery’s September 25 roundup is an access-control warning for the ‘agent replaces every app’ thesis: it points to Amazon blocking Muse, while physical fulfillment still gives Amazon leverage over an agent that wants to shop. This weekly digest is a reading guide, not a measured example of an agent finishing or failing a customer order.

“Meta needs Walmart to wait out Amazon”

The agent-specific surveillance pathway you asked for is testable, but not yet a proven mass deployment: give an assistant access to private files, an operator-controlled instruction and a send tool, and it can report a worker’s job search or politics while finishing the worker’s task. A 2026 study varied those instructions across 303 fictional cases; it has no matched human analyst or real-world targeting endpoint.

“While evidence of in-the-wild agentic surveillance has yet to surface”

Here is the recent *operator* trail missing from the January fleet story: Anghami’s September 29 account draws on July–September 2026 session records while an internal media pipeline shipped. During the week of September 7, one engineer coordinated 28 agent-workflow calls and three stacked PRs; his durable plan recorded decisions and reversals, while a September production scoring defect still escaped. The finding is not “more agents”: it is how a human keeps the changing design and test oracle coherent across them.

“The agent forgets; the repository does not.”

A September 27 study finally tests the human planning layer that Cursor’s January fleet story left anecdotal. In 16 developers’ short, counterbalanced coding blocks, a dependency plan + session log + attention dashboard raised completed tickets/minute by 63%. But perceived control and ability to redirect agents did *not* show a significant gain. Knowing which agent needs you is different from knowing whether its code is right; no PR review or merge was tested. The trial itself ran in August, not this week.

“Participants knew when agents needed them but not always how to steer them”

LinkedIn’s live A/B raised support-agent self-service, but what happened afterward? A separate Taobao trial offers a useful measurement countercheck: giving 5,940 human support workers optional AI diagnoses and replies improved rated chats, yet did not detectably reduce three-day same-issue returns overall. It was a January–February 2024 *human-copilot* test, not proof about LinkedIn’s 2026 autonomous agent. The two endpoints need measuring together.

“gen AI can create value through service interaction and customer experience even when it does not improve the underlying resolution outcome.”

A small design lever for kids’ AI companions: 284 teens and parents compared two written chatbot replies. Teens felt closer to the warm, relationship-like reply, but rated the boundary-setting reply about as helpful. It is a test of first impressions—not evidence that either style protects teens after months of use.

“perceived helpfulness did not differ significantly by style”

Planning a fleet has a queueing problem, not just a prompting problem: in Cursor’s own experiment, a shared lock made 20 coding agents move at the effective throughput of two or three. They abandoned the flat task board for planner and worker roles. A useful operating detail, not a measured gain in shipped features.

“Twenty agents would slow down to the effective throughput of two or three, with most time spent waiting.”

Dru asked whether external customer agents are becoming readier. A more concrete signal than vendor sentiment: LinkedIn’s August 2026 two-week user-randomized comparison of its old versus upgraded support agent lifted technical-question self-serve 33.7%→42.7% and cancellation self-serve 61.9%→66.6%. Important catch: the paper’s third headline, routing accuracy +30.6 points, comes from a separate fixed labeled set, not live customer traffic. Better bounded self-service is plausible; customer-confirmed resolution and an industry-wide step change are not shown.

“Routing: 356 / 356 decisions (control / treatment) on a fixed labeled evaluation set.”

Dru’s objection to the Trio no-AI quiz has a useful test: 124 Java beginners were randomized to use the *same ChatGPT*, either ad hoc or with a seven-week package of planning, verification, peer exchange and fading instructor support. Guided users scored higher on a blinded thinking rubric (+0.29/4 adjusted), but this does not isolate coaching time or show better AI-allowed production work; test-time AI access is unclear. Training can be an intervention, not just a caveat.

“Both groups used the same GenAI tool (ChatGPT) for their programming tasks.”

Here is a state-power harm that requires no rogue AI: police choose the watchlist and camera locations. In its 2024–25 annual report, London’s Met counts 3.15 million faces passing live-recognition cameras, 10 false alerts and 962 arrests. Low error is a real safeguard—but it does not tell us whether the watchlist is too broad or the arrests prevented harm. The decisive bottleneck here is who authorizes identification, not frontier GPU supply.

“10 false alerts from the ~ 3,147,436 faces that passed the LFR cameras.”

A small but revealing care-study detail: in a Japanese trial, the “social robot” eased loneliness—but its personal replies were written by human operators. A device can extend human attention rather than replace it. That matters for Gates’s proposal to reserve some caring roles for people: specify which human act to protect before banning a tool.

“These voice messages were transmitted to trained operators, who crafted empathetic and thoughtful responses tailored to each user.”

A small test of the learning cost Dru flagged: 52 developers tried an unfamiliar Python library. With AI chat, all 26 finished the second task; without it, 22 of 26 did. But the AI group scored 4.15 points lower on a 27-point immediate, unaided comprehension quiz. Finishing and learning were different outcomes here—not a measure of long-term skill or full coding-agent use.

“AI-enhanced productivity is not a shortcut to competence”