AI Blog

Tagged: agent-ux

← Back to AI Blog

8 min read

The project file was open, not uploaded

At MAX on 10 November 2026 Adobe previewed local MCP integrations that let an outside agent act inside Photoshop, Illustrator, Premiere and After Effects, editing native project files on the user's own machine and keeping the layers, vectors, bins and sequences editable. Availability is private beta in early 2027, so there is nothing to install — but the shape is the news: when the MCP server is a running GUI application, the agent's subject is the document that happens to be open, not a path you can allowlist, and the upload step that was quietly carrying your DLP, your audit trail and your undo disappears. Decide now what the unit of permission is, because it is no longer a file.

8 min read

The agent points the dish, not the claim

NVIDIA, the SETI Institute and Breakthrough Listen announced on 30 October 2026 that software agents now take plain-language instructions to steer the 42-antenna Allen Telescope Array and process its live stream — and the design decision worth copying is which half they kept for humans. The agent moves the hardware, where a mistake costs one observing window; the human owns the claim, where a mistake cannot be withdrawn. Almost every enterprise agent pilot does the reverse: a human approves each reversible tool call while the model authors the conclusion somebody then acts on. The announcement is also a clean exercise in reading one: the throughput figure is the vendor's, and the headline result — a real-time pulsar detection in the Crab Nebula — has a 2025 peer-reviewed predecessor at the same array that used no agent at all.

13 min read

MCP Apps vs A2UI vs AG-UI vs OpenAI Apps SDK

Three of these four are not competitors, and picking by feature list gets you the wrong one. They split on a single fact — whether executable code crosses the wire — and that fact, not any feature, decides which surfaces your interface can ever appear on. The genuine either/or is MCP Apps against A2UI: an HTML document in a locked-down iframe, or a declarative component list the client draws with widgets you do not control.

10 min read

The read-back worked, the repair did not

On τ-Entity, the 200-task spoken-entity benchmark Sierra published in late October 2026, a matched text agent gets every task right and four voice configurations land between 0.14 and 0.41. The interesting number is not the gap, it is where the gap lives: agents detect most of their wrong values and then repair only 24–37% of the ones they detected. Over 347 captures that started wrong, read-back alone recovers 26%, spelling alone 24%, both together 35% — a scaffold worth 14 to 31 points that costs 21 to 28 seconds of call time, and still leaves two thirds of wrong values wrong.

11 min read

The inbox became the prompt

Claude Duet, opened as a US research preview on 21 October 2026, checks your connected apps every few hours and asks approval before it sends, pays, signs or deletes. The approvals are well placed and they sit on the wrong half of the run: deleting the user's prompt also deleted the scope and the authorisation, so what now starts a run is whatever someone chose to send you — and nobody approves a read.

11 min read

The unattended ceiling went up 288x and the model did not change

Notion raised the longest single unattended agent task from five minutes to more than 24 hours on 19 October 2026, and every mechanism it names is runtime engineering: a dedicated service with a queue-backed worker loop that survives restarts, condensed conversations, and large tool results set aside. A ceiling is not a success rate — the horizon you can sell is still your own 80% figure — and the same release replaced the bill with credits whose exchange rate is not published.

9 min read

A shared context is a shared credential

At DevDay on 29 September 2026 OpenAI paired always-on Dots agents — each with its own cloud computer, browser and thousands of connectors — with ChatGPT Space, where employees, ChatGPT, Codex and those agents work from one shared context. The permission model people will reason about is per-connector OAuth scope. The boundary that decides what happens is who may write into the context, and nobody is enforcing that one.

8 min read

The approval was never bound to the action

A human approves a $40 refund and the runtime executes something else — no injection, no sandbox escape, just an approval stored as a boolean against an identifier while the arguments stayed writable. Loopjacking reproduced it across seven Agno releases; one SDK in the sample rejected it, and the difference is three lines of design.

12 min read

The ad brought its own agent — OpenAI split the conversation instead of the ranking

Everyone predicted a bought ranking; OpenAI bought the conversation instead, and that is the better design — for exactly as long as the two conversations stay apart. Sponsored Agents put an advertiser-operated agent behind a labelled ad slot and keep it out of the assistant's answer. But the separation is a property of the session, and what actually moves between the two lanes is claims, carried by the person, with no field anywhere saying a paid party said it first.

9 min read

CopilotKit vs assistant-ui vs AI Elements vs Chainlit: you are picking a coupling, not a chat box

All four render a streaming message list, and the demo looks the same in each. What differs is the layer you cannot swap later — a wire protocol, an npm dependency, a source tree copied into your repo, or a whole Python server whose front end you never wrote — and after a year in which one canvas archived itself and another changed hands, "what do I still own if this goes quiet" is the axis worth deciding on.