Today
Front-end, in one read.
The latest from the sources worth following, newest first.
DEV CommunityThe Giantsread at source
What Stopped an AI Buying Agent on 50 Commerce Sites
Cross-posted from ByteSprint. The data below comes from a public scan of 50 commerce sites, so it is a snapshot and not a verdict. Short answer: in a public scan of 50 commerce sites, the median score for an AI buying agent was 11 out of 100. The Index says a low score means the agent met a barrier, such as a bot challenge or a rejected add-to-cart. The data is one scan, from one location, so read it as a snapshot and not a verdict. More shoppers now ask an AI assistant to find and compare products. A practical question follows for anyone running a store: if an agent tried to buy here, how far would it get? The Axidort Index tries to answer it by running the journey, so this piece walks through what it measured, what it found, and where its limits are. What was measured The Axidort Index scanned 50 well-known commerce sites on October 1, 2026: 25 B2B and 25 B2C. For each, a declared AI browser agent (it identifies itself as AxidortAgentCheck) tried a purchase journey: search for a product, open it, read the price and stock, and head toward checkout. It never places an order, pays, logs in or submits forms. A second, no-browser reader agent checks what can be read from the page text and data. The score runs from 0 to 100 and is built from seven components. Per the published methodology , agent behaviour carries 90% of the score and standards and files such as structured data carry 10%. The headline numbers All figures below are from the Index page and its JSON data . Median score: 11 out of 100. 72% of sites scored below 50. B2B sites averaged 20 out of 100 (25 sites). B2C sites averaged 34 out of 100 (25 sites). The highest score was 97 out of 100, so a full journey is clearly possible for an agent on some sites. What actually stopped the agent The honest answer is narrower than the headline. The Index does not publish a per-stage breakdown of where each agent stopped across all 50 sites, so we cannot say how many failed at search versus price versus add-to-cart. What it does state is that a low score means the agent met a barrier, with a bot challenge and a rejected add-to-cart given as examples. A bot challenge is the example worth understanding, because it can sit in front of the whole journey and stop an agent before it reaches a product page. Why bot challenges are worth checking Bot protection exists for good reasons: scraping, credential stuffing, card testing. The side effect is that a declared, well-behaved agent can look like any other automated visitor. Some vendors let site owners allow known bots by verified identity (see Cloudflare's verified bots documentation for one example), but whether a given store has set that up is a configuration question, not something visible from outside. Two things follow for a store owner: A rule written years ago for scrapers may now also stop the shopping assistants your customers use. Nobody has to have decided that on purpose. Passing a standards checklist does not mean an agent can get through. A site can publish every well-known file and still challenge the agent at the door. That is part of why the Index scores behaviour first. How to read this data fairly These limits come from the Index itself, and they matter: Each site was scanned from a single location, at one moment. Sites scoring under 70 were scanned twice and the better score is shown. Scores are automated opinions from public pages, not statements of fact about a company's products, quality or security, and not recommendations to buy or avoid. No listed company sponsored, endorsed or reviewed the results, and names are used only to say which site was measured. The scan covers commerce journeys only and does not look behind logins. It says nothing about price competitiveness, range, delivery or service. The scores can shift slightly between runs, and a different agent or location could see something different. For that reason this article does not name low scorers. A low score tells you an agent met a barrier on that day. It does not tell you the business is doing anything wrong. What you can check on your own site You do not need a scanner to start. Four checks cost nothing: Ask your developer or platform support whether bot protection challenges automated visitors on search, product and cart pages, and whether any rule lets declared agents through. Look at a product page with scripts off. Is the price in the visible text and in structured data, or only drawn by JavaScript? The guide on structured data for AI agents covers the markup. Add an item to the cart in a private window, with no cookies. Does it work, or does it demand a session set up elsewhere? Check that stock status and units (per case, minimum order) are stated in text. If you would rather see what an agent experiences than guess, the free score below runs the same journey on your domain. It is an automated opinion, takes about three minutes and needs a Google sign-in. FAQ Does a low score mean my store is losing sales to AI? No. There is no data in the Index about how many purchases agents make on any site, or about revenue. The score shows how far one declared agent got on one day. Why is the median 11 when the best site scored 97? The scores are uneven: some sites let the agent get a long way, and many scored low. The median describes the middle of the 50, so one strong site does not move it. Are B2B sites worse than B2C? On average in this sample, yes: 20 versus 34 out of 100. With 25 sites in each group, treat it as a pattern worth watching, not a rule. Is 50 sites representative of all commerce? No. It is a set of well-known sites, not a random sample. Check your own site The free Axidort Score runs a declared agent through search, product, price and stock, and shows where it stopped. A score is a starting point for a conversation with your developers, not a grade on your business. Get my score If you run a business site and want help acting on the result, you can talk to our team . Originally published on ByteSprint . Disclosure: ByteSprint is published by the team behind Axidort, which makes the Axidort Index and the Axidort Score discussed above.
DEV CommunityThe Giantsread at source
PyScriptはメンテナンスモードに移行しました。ブラウザ上でPythonを利用するための選択肢は、今後どうなるのでしょうか。
PyScriptがメンテナンスモードへ移行 PyScriptがメンテナンスモードに入ります。この発表は先月、プロジェクトのコアメンテナーの一人であるAndrea Giammarchi氏が、 公開gist で行いました。APIは凍結され、今後はPyodideの更新のみが、より緩やかなペースで続けられます。 私は、以下で言及しているツールの一つ、Pytmlの作者です。最初に開示しておきます。 このエコシステムに馴染みのない方には、大したことに聞こえないかもしれません。しかしPyScriptは、2022年以来、「ブラウザでPythonを動かすにはどうすればいいか?」に対するデフォルトの答えでした。 なぜこうなったのか このgistは、驚くほど率直です。 「採用の広がり、OSSへの貢献、そして人々が記事や成功事例を公開することで生まれる種類の宣伝は、私たちが望んだようには育ちませんでした。」 「正直なところ、PyScriptはニッチなままでした。」 「両プロジェクトをフォークして、存続させ続けることもできます。そうしてくださるなら、あなたがそれをどこへ導くのかを見られることを、心から嬉しく思います。」 最初の引用を2回読んでみてください。PyScriptが停滞したのは、技術が悪かったからではありません。技術は非常に堅牢です。停滞したのは、公の場でPyScriptについて書く人が十分にいなかったからです。奇妙な失敗の形です。技術的負債ではなく、物語(ストーリーテリング)の不足によってプロジェクトが終わろうとしているのです。 現在のPyScriptの状況 まだ動作します。 CDNは稼働中で、ドキュメントも公開されており、コードは安定しています。 APIは凍結されています。 Pyodideの更新以外に、新機能はありません。 チームは一歩引きました。 Andreaははっきりとこう述べています。 「私はもうPyScriptには関わりません。」 フォークは歓迎されています。 Apache 2.0ライセンスで、メンテナーの祝福付きです。 すでにPyScriptを使っているなら、何も壊れません。これから採用しようとしていたなら、答えは変わりました。 人々が本当に求めていたもの PyScriptの売り文句は野心的でした。OSのセットアップなしで、ブラウザ上でPythonを動かし、教育、ダッシュボード、科学計算に使うというものです。しかし、ほとんどのユーザーに届いたのは、もっとずっと小さなものでした。 HTMLファイルにPythonを書き、開いて、動くのを見る。 このケースは今でも動きます。ただ、それを作った人たちによってメンテナンスされることはもうありません。 現在の選択肢 どの選択肢にもトレードオフがあります。 PyScript(凍結) — 成熟していて安定しています。 タグ2つと設定ブロックが必要です。すでに使っているなら、使い続けて構いません。今後変わることはありません。 Pyodideを直接使う — すべての土台となるエンジンです。完全な制御ができますが、セットアップが増えます。連携コード(グルーコード)は自分で書く必要があります。 Brython — ほぼ即時に読み込まれ、WASMランタイムは不要です。DOM操作や教育に最適です。NumPyやPandasは使えません。 Skulpt — Brythonに似ていて、さらに小さく(約200KB)、標準ライブラリは不完全です。高速で、教室での利用に特化しています。 Transcrypt — PythonをJavaScriptに事前コンパイルします。実行速度は最速ですが、ビルド工程が必要です。 Pytml — 私のものです。Pyodideを包む約15KBのラッパーで、scriptタグ1つ、 タグ、 print() と input() の自動対応が特徴です。ランタイムはPyScriptと同じで、遅延読み込みされます。MicroPython、ファイルシステムAPI、プラグインはありません。今後追加する予定もありません。 これらのどれも、PyScriptの代わりにはなりません。それが正直なところです。 Pytmlの立ち位置 私は、セットアップなしでシンプルなケースを実現したくてPytmlを作りました。やることは一つだけです。 + タグ+自動I/Oです。 PyScriptの後継として提示するつもりはありません。後継ではないからです。PyScriptの全機能が必要なら、PyScriptをフォークしてください。メンテナーがそれを歓迎しています。 私が言いたいのは、 Pythonをブラウザで動かすための「すべてを統べる唯一のフレームワーク」の時代は終わった ということです。次の段階は、一つのことをうまくこなす、小さく焦点を絞ったツールの時代です。 今日、選ぶなら 問いは一つです。 PyScriptの全機能が必要ですか、それともシンプルなケースだけですか? 全機能が必要 → PyScriptをフォークする NumPy/Pandasを使うシンプルなケース → Pyodideを直接使う、またはPytml シンプルなケースで、即時読み込み、科学計算パッケージは不要 → BrythonまたはSkulpt 本番環境向けに、Python構文をJSにコンパイルしたい → Transcrypt 間違った選択肢はありません。間違いなのは、凍結されたものを、それと知らずに採用することです。 補足: 原文の「Pytml」の説明で「same runtime as PyScript」とある部分は、「Pyodideベースである点でPyScriptと同じランタイム」という意味です。そのように訳しています。
DEV CommunityThe Giantsread at source
22 pull requests to open-source projects in a month: what got merged, what didn't, and why
Between 15 October and 13 November 2026 I opened 22 pull requests to open-source projects I don't own. Eleven were merged, four are still in review and seven were closed without merging. That's a 50% merge rate overall, or 61% of the ones where a maintainer has made a decision. The median merged PR took about four days from opening to merge. The fastest took about 40 minutes; the slowest, almost nine days. This post covers what those PRs fixed, what the maintainers changed before merging, and why the other seven didn't land. The closed ones taught me as much as the merged ones. The merged eleven Project Stars What the fix did Besu, the Ethereum client (Java) 1.9k Three fixes, below rust-analyzer (Rust) 17k Made VS Code link Rust errors to files again with rustc's unicode output Quarto (TypeScript) 6.2k Made the dismiss button on website announcement bars usable from the keyboard Ratatui (Rust) 23k Tests that stop halfwidth katakana sound marks from being counted twice Thumb-Key (Kotlin) 1.6k Two fixes: layout search, and a "hide letters" key for custom layouts Authlib (Python) 5.5k Three documentation PRs answering open questions from the issue tracker Star counts as of 18 November 2026. Seven of the eleven are code fixes. Three are documentation and one is tests only. Besu: three small bugs, three tests Besu is a Java Ethereum client. I sent three fixes the same day: miner_getExtraData dropped leading zero bytes. Set the extra data to 0x000102 and it came back as 0x102 , so the value didn't round-trip. admin_logsRemoveCache treated the safe and finalized block tags as the chain head instead of resolving them. debug_standardTraceBlockToFile ignored enableReturnData: false , because the value was hard-coded to true. Each came with a test that fails without the fix. The maintainer merged all three within about nine days. For the third, the maintainer also opened a docs PR so the documentation matched the code. rust-analyzer: one changed line My smallest merged PR. rustc can print error locations with unicode box drawing, like ╭▸ src/main.rs:2:5 instead of --> src/main.rs:2:5 . rust-analyzer's VS Code problem matcher, the regex that turns compiler output into clickable errors, didn't know about ╭▸ . So the arrow became part of the file name and VS Code couldn't find the file. The fix was one line in the regex. This one had no automated test: the problem matcher lives in the extension's package.json , and I checked the new pattern against rustc's own unicode output samples instead. The maintainer said as much when merging: it couldn't easily be tested, but the change was right. Quarto: accessibility, tested in three browsers On Quarto websites, the "X" that dismisses an announcement bar couldn't be reached or pressed with a keyboard. I made it a real button and added a Playwright test that runs in Chromium, Firefox and WebKit. The maintainer added one commit, to keep the icon at the top when the bar wraps onto several lines, and noted that the tests fail without the change in all three browsers. It merged the next day. What the maintainers changed The PR I learned the most from is the one where my fix didn't ship. In Ratatui, halfwidth katakana sound marks (゙ and ゚) were counted twice when measuring text width with one version of the unicode-width crate. I wrote a guarded workaround that worked on both 0.2.2 and 0.2.3, plus tests. The maintainer took a simpler route: raise the minimum unicode-width version to 0.2.3, where the bug doesn't exist, and delete the need for a workaround. The maintainer kept my tests, rebased them onto main and merged them as the guard against the bug coming back. Fewer lines, less to maintain, and the right call. The lesson for me: before writing compatibility code, ask which versions actually need supporting. In the other merges, maintainers changed little: in Besu they merged main into my branches and asked for a changelog entry in the right section; in Thumb-Key and Authlib the PRs merged as sent. The seven that didn't merge pandas (50k stars): closed automatically the same day. The issue was already assigned to another contributor, and pandas allows one contributor per issue. I hadn't checked. Thumb-Key: I closed one myself because another PR had already landed the same fix. reqwest (12k stars), twice: I closed the first myself after realising I hadn't followed the PR template, which asks for a description written in your own words. The maintainer closed the second, a docs change, saying the docs were already clear. Fair enough: it's their project. ParadeDB: one PR was closed without a comment. I've asked why and haven't heard back yet. REA, twice: both were superseded by the maintainer's own commits. One of those commits adapted my change and credits me as co-author, so the code landed even though the PR didn't. None of these were about code quality. Most came down to things I could have checked first: who already claimed the issue, whether someone else was on it, and what the project asks of a PR. Still in review Besu: a larger change that rejects block overrides and unknown parameters on five JSON-RPC methods, now through several review rounds. Qwen Code (30k stars): inline session rename with an F2 shortcut. A maintainer has called it merge-ready. ParadeDB: support for constant output columns in an aggregate scan. The reviewer said it "mostly looks great", with one blocker that I've since fixed. Ratatui: removing APIs that were deprecated back in version 0.26. Where AI fits in I use AI throughout this work, the way I use any good tool. It reads unfamiliar codebases with me, drafts and runs tests, checks a fix against the reproduction, and reviews my diff cold, seeing only the issue and the change, before anything goes out. That turns a day of finding my way around a new Java or Rust codebase into an hour or two. It doesn't make the decisions. I choose the issues, decide whether a fix is right for the project, read every line before it's sent, and answer the reviewers myself. If a maintainer asks why a line is there, I can explain it. Projects that don't accept AI-assisted contributions get nothing from me, and where a PR template asks for a description in your own words, that's what it gets. How I work on a PR now After a month of this, these are the rules I follow: Every fix comes with a test that fails without it. This earns more trust than any description. Where a test isn't practical, like the rust-analyzer regex, I say so in the PR and show how I checked it. Keep the diff as small as the bug. One of my open PRs grew several times over during review. Small PRs get reviewed; big ones wait. Read the contribution rules first. CONTRIBUTING, the PR template, the CLA, and the project's policy on AI-assisted contributions. Some projects don't accept them at all, and I don't send them anything. Check who's already working on it. Look for assignees, linked PRs and recent comments before writing code. Leave product decisions to the maintainers. When the docs and the code disagreed in Besu, I fixed the code and asked which behaviour they wanted documented, rather than deciding for them. Respect review bandwidth. After my first few Besu PRs, the maintainer asked me to get those through review before opening new ones. That was fair, and all three merged within a week. I now keep at most two PRs waiting per project. Why I'm doing this Two reasons. Reading and fixing code in mature projects across Java, Rust, TypeScript, Kotlin and Python makes me a better engineer faster than anything I build alone. And every merged PR is a small, public, checkable piece of work, reviewed by people who don't know me and have no reason to be kind. If you maintain an open-source project, what makes a first-time contributor's PR easy for you to merge?
DEV CommunityThe Giantsread at source
Em teste, Ethernet via Studio Display XDR reduziu o download em cerca de 75%
Teste isolou a conexão pelo monitor Em uma conexão simétrica de 2,5 Gbps, Oscar Molnar mediu cerca de 600 Mbps de download ao usar um adaptador Ethernet USB-C conectado ao Studio Display XDR. Ligado diretamente ao MacBook Pro M3 Pro, o mesmo adaptador chegou a 2,3 Gbps no iperf3 e a 2,2 Gbps no fast.com. A configuração testada incluía o monitor, um adaptador UGREEN de 2,5 GbE e um UniFi Dream Router 7. Durante downloads pela conexão Ethernet ligada ao monitor, os pings para outros computadores cabeados falhavam em 10% dos casos; pelo Wi-Fi, não falhavam. O macOS também não registrava erros de quadros perdidos, o que levou Molnar a investigar se as perdas ocorriam antes de os dados chegarem ao computador. Driver e controle de fluxo O adaptador usa o chip Realtek RTL8156B, que no macOS funciona com o driver genérico de rede USB da Apple. Depois de instalar o driver da Realtek, o download subiu para 1,1 Gbps, ainda abaixo da velocidade esperada. Ao ativar o controle de fluxo no UniFi, chegou a cerca de 2 Gbps, enquanto o upload permaneceu em 2,4 Gbps. Com o controle de fluxo, um dispositivo que não consegue acompanhar a chegada dos quadros Ethernet pode enviar ao emissor um quadro de pausa. O emissor armazena os dados até que o receptor esteja pronto. Molnar preferia não manter o recurso ativado para toda a rede porque ele poderia acrescentar latência a outros sistemas. Medições apontaram um limite no caminho USB Para investigar as perdas, Molnar enviou tráfego UDP a taxas fixas de um computador Linux e consultou os contadores do adaptador, com o controle de fluxo desativado. Pelo hub do monitor, as perdas começaram perto de 2 Gbps: a 2,03 Gbps, chegaram a 2,7%; a 2,28 Gbps, a 13,5%. A taxa de quadros entregues ao Mac estabilizou em cerca de 168 mil por segundo. Ligado diretamente ao Mac, o adaptador quase não perdeu quadros, mesmo nas taxas mais altas testadas. A análise relaciona o limite ao tempo de resposta do hub e ao tamanho das rajadas USB. O hub levava, em média, 7,6 microssegundos para responder à autorização de envio, e o RTL8156B transmitia quatro pacotes de 1 KB em cerca de 8,2 microssegundos antes de aguardar outra autorização. Para comparação, o gabinete de um SSD usado por Molnar enviava 16 pacotes por rajada. A diferença pode fazer os dados se acumularem no buffer do adaptador até ele descartar quadros. Comparação com o RTL8157 Um adaptador UGREEN de 5 Gbps com chip RTL8157 não registrou quadros descartados nos testes até 2,4 Gbps. Nessa taxa, entregou cerca de 194 mil quadros por segundo ao Mac. A consulta usada por Molnar para verificar as informações USB foi: $ python3 -c "import usb.core; e = usb.core.find(idVendor=0x0bda)[0][(0,0)][0]; print('packet size', e.wMaxPacketSize, 'bMaxBurst', e.extra_descriptors[2])" Os dois adaptadores indicaram pacotes de 1.024 bytes. O valor de bMaxBurst foi 3 no RTL8156B e 7 no RTL8157; como esse campo conta os pacotes adicionais ao primeiro, são quatro e oito pacotes por rajada, respectivamente. Com a rajada maior e uma conexão duas vezes mais rápida, Molnar estimou que o RTL8157 poderia transferir dados ao Mac a até 4,5 Gbps, acima dos 2,5 Gbps que chegavam ao adaptador. Assim, o buffer não se acumularia nas condições testadas. Os resultados se referem à combinação de monitor, adaptador e equipamentos usada no teste. O relato técnico de Oscar Molnar detalha as medições e a comparação entre os chips. Confira mais em: https://guiadeti.com.br/noticias/monitor-reduzia-velocidade-download-75-ethernet/
DEV CommunityThe Giantsread at source
My CI was red for 6 days and 19 PRs got merged anyway. The same 45 tests failed every time, so red became the background color
Short version: a CI that is always red is the same as no CI. The repository that holds my agent workflow went red on its very first CI run and stayed red for 6 days and 24 runs. 19 PRs were merged in that window. Every run had the same 45 failures, and 40 of them had nothing to do with code: the repo had lost its executable bits and two symlinks when it was imported. The fix was one commit. Since then, 15 of 16 runs have passed. Some background. This repo holds my hooks, dispatch scripts, skills, and global rules. Every Claude Code and Codex session loads its rules from here, so when it breaks, every project feels it. The guards, status board, and reminder hook from earlier parts of this series all live in it. What happened On November 14 the repo ran CI on GitHub for the first time. The workflow, called Verify, runs pytest and two check scripts on every PR. First run: 45 failed, 91 passed. Last red run, November 20: 45 failed, 127 passed. Over six days, 36 new tests were added, and all of them passed. The failure count never moved. There were 24 runs across 20 branches, every one a failure, and 19 PRs merged, including the audit false-positive fix from part 2 and the long-session reminder from part 8. 40 lines in the failure log were the same error: PermissionError: [Errno 13] Permission denied . The tests execute the scripts directly, and the scripts weren't executable. Why nobody fixed it for six days It wasn't that nobody saw it. An audit doc I wrote on the evening of November 15 had the cause, and marked it "can start right away": every script with a #! line was stored in git as 100644 , not executable; two files that should have been symlinks had been flattened into regular files whose only content was a relative path, so running them gave Exec format error ; in a scratch copy, adding the executable bits took the failures from 45 to 20, restoring the two links took it to 7, and 2 of those came from the scratch copy having no commit history. 5 were real; those 5 were assertions inherited from an upstream template. They checked for clauses and files from someone else's environment, which were never going to exist in mine. After that doc, CI went red 19 more times and 15 more PRs were merged before anyone fixed it. My read: when the red is identical every time, it stops being a signal. Every PR was red, so red said nothing, and nobody at merge time compared 45 against 46. If a new test had broken, it would have drowned in the old red. One more thing. It's a private repo on a free plan, which means no branch protection. "Don't merge unless checks pass" can't be enforced by the platform. I called the branch protection API today and got a 403. Whether a red PR gets merged is entirely up to whoever merges it. The fix: one commit The November 20 fix did three things: Restored the executable bits. Git records 34 files changing from 100644 to 100755 . Turned the two fake links back into real symlinks (mode 120000 in git). Replaced the inherited assertions with my own current constraints instead of just deleting them: the global rules file must keep all six "boundaries that must stay" (for example: never push to main on your own, credentials live only in the system keychain); every local link in the README must resolve; the global rules file stays under 10 KB. Of the 16 runs since, 15 passed and 1 was auto-cancelled because a newer push landed on the same branch. The latest run: 190 passed, 0 failed. Where the rules live The Verify workflow runs pytest, a skill bundle check, and a repo context check on every PR. The tests execute scripts directly, so if the executable bits get lost again, CI goes red immediately. And because CI is green now, red means something new broke. tests/test_agent_context.py fails if any of the six boundaries goes missing. Those are what I'm most afraid of losing in a "let's trim the rules" pass. tests/test_readme_contract.py fails if a local README link stops resolving. Two things still open Merging is still gated by people. The platform can't require checks, and I haven't added a "stop if checks failed" step to my merge command yet. What changed is that CI is green, so red finally carries information. The 10 KB cap was raised to fit. The upstream cap was 4,000 bytes. My rules file was 7,314 bytes on November 15 and is 9,407 today. The fix set the cap to 10 KB with a comment that says "to add a rule, delete one first." The file hasn't been slimmed down. The ceiling just sits a little above where it is now. What you can take from this After importing or migrating a repo, check file modes first. This reads git objects only and doesn't touch your working tree. On the commit before my fix it reports exactly 34 missing executable bits and 2 flattened links. On today's main it prints nothing. ref = ${1:-HEAD} git ls-tree -r "$ref" | while read -r mode type sha path ; do [ "$mode" = 100644 ] || continue head = $( git cat-file -p "$sha" | head -c 64 ) case "$head" in '#!' * ) echo "not executable: $path" ; ; ../* ) [ "$(git cat-file -p " $sha " | wc -l)" -eq 0 ] && echo "flattened symlink?: $path" ; ; esac done If CI is red on its first run, make it green before doing anything else. An always-red CI isn't a CI with a problem. It's no CI. The test is simple: if several runs in a row fail with exactly the same count, nobody is reading it. Replace inherited assertions with your own constraints. Don't just delete them. Deleting turns CI green, but then it guards nothing. Ask what you'd hate most to lose, write that as the new assertion, and put the reason in a comment. If the platform can't require checks, put the check in your merge step. I haven't done this one yet. It's on the list. This is part 9 of the series. Earlier parts kept saying "put the rule where the agent can't route around it." This one is the flip side. The check was in a place nobody could skip, but it was always red, so everyone learned to ignore it. About the numbers 24 failures, 20 branches, 16 runs after the fix (15 passed, 1 cancelled): read on 2026-11-21 with gh run list across all 40 runs of the Verify workflow. First run 2026-11-14, fix run 2026-11-20 (UTC). 19 merged PRs: gh pr list --state merged the same day, counting merges before the fix commit. The 15 PRs and 19 failures after the audit doc use the same lists and the doc's commit time (2026-11-15 21:21 US Eastern). 45 failed / 91 passed, 45 failed / 127 passed, 40 PermissionError lines, 190 passed: read from the logs of the first run, the last red run, and the latest run. The 45 → 20 → 7 → 5 breakdown: from the 2026-11-15 repo audit doc, done as an experiment in a scratch copy. 34 mode changes, 2 links, and the new assertions: from the 2026-11-20 fix commit itself. Its message says "32", but git records 34 mode changes. 7,314 and 9,407 bytes: the first from the audit doc, the second from wc -c on current main on 2026-11-21. Branch protection 403: the GitHub branch protection API response on 2026-11-21. The check script: run on 2026-11-21 against the pre-fix commit and current main, with the results described above.
AbduzeedoMulti Author Blogsread at source
Book Design: Accidental Collage by Dr.Me & Waiting Room Press
Dr.Me and Waiting Room Press turn torn street posters into a 400-page book design, hand-ripping every cover of Accidental Collage. Every copy of Accidental Collage arrives damaged on purpose. Created ...
HTML All The ThingsPodcastsAudioListen
Does Xbox Need Exclusives to Survive?
Xbox is struggling to compete with PlayStation in console sales, despite offering consumer-friendly features like Game Pass, more affordable hardware options, and games across multiple platforms. Could the solution be bringing back exclusive games? In this edition of the Web…
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: agent-mcts – Monte Carlo tree search on top of Claude Code
Comments
Chris HawkesYouTube ChannelsVideoWatch on YouTube
I Tested Seedance 2.5 in 4K — Can AI Recreate a WWII Battlefield?
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: Atlas of Money
Comments
Hacker News Front PageThe Giantsread at source
Derek Lowe: Detonating a Pile of Lead Azide
Hacker News Front PageThe Giantsread at source
Astra 6.2 and Sol 6.2 flop at Simple Bench
Hacker News Front PageThe Giantsread at source
Adult-only households accounted for 55% of toy sales in the first half of 2026
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: ILoveNotch 2.0 – an open-source Mac notch app with a teleprompter
Comments
AdactioTop Front-end Bloggersread at source
See you later, Amsterdam!
Hacker News Front PageThe Giantsread at source
My Monitor Was Cutting My Download Speed by 75%
Hacker News Front PageThe Giantsread at source
FBI reportedly investigating apparent hack of its criminal database
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: ClawVet – Offline AST scanner and rug-pull diff for AI agent skills
Comments
Hacker News: Show HNLibraries, Frameworks, etc.read at source
Show HN: PocketTransfer – iPhone to PC/Mac file transfer in the browser
Comments
Flavio CopesMore Front-end Bloggersread at source
Resend: the email API I use for my sites, my apps and my AI agents
What Resend does, how I use it to send sign-in links and form emails across my course sites, why I like it, and how to give AI agents email with its MCP server, CLI and skills.
Flavio CopesMore Front-end Bloggersread at source
Turn on automatic security updates on your VPS (and decide about auto-reboot)
Set up unattended-upgrades on Ubuntu and Debian, tested on a real Droplet with the November 2026 NGINX HTTP/2 fix: security-only vs all packages, auto-reboot, needrestart, third-party repos, logs and alerts.
Flavio CopesMore Front-end Bloggersread at source
Finishing is a skill
How I get things done: the three states every project is in, why everything I ship is version one, the seven-day rule, why I ship lots of small experiments, and why deleting or automating something counts as finishing it.
AbduzeedoMulti Author Blogsread at source
The Book Design of ADI Design Museum’s Compasso d’Oro
Leonardo Pertile’s book design for ADI Design Museum’s Compasso d’Oro packs 1,040 pages into twin cloth volumes set in OT Marmo. Compressing nearly seventy years of Italian industrial design into a 1,...
Frontend Masters BlogMore Front-end Bloggers8 min read
Apps I’ve Vibe-Coded Lately That Are Pretty Damn Useful To Me, Actually
Hey, we can all vibe code. But sometimes what you need are ideas that are actually useful.
AbduzeedoMulti Author Blogsread at source
How STUDIO HERRSTRÖM Reimagined the Milkshake brand identity
STUDIO HERRSTRÖM rebuilds the Milkshake brand identity around car culture, a redrawn splash mark, high-vis color and road signs. Milkshake is a Stockholm label, a division of Sony Music Entertainment ...
AbduzeedoMulti Author Blogsread at source
HelloAsso: Civic Non-Profit Brand Identity by Bruno
French agency Bruno rebuilds HelloAsso’s brand identity with Franklin Gothic poster type, bold pictograms, and unstaged member portraits. Since 2009, HelloAsso has run as a free management platform fo...
AbduzeedoMulti Author Blogsread at source
Mutabor Unveils the Voith brand identity
Mutabor builds the Voith brand identity around movement: a V-Vector symbol, a custom typeface, and a blue made for screens. The whole system starts with a single chevron. Mutabor calls it the V-Vector...
Google for DevelopersYouTube ChannelsVideoWatch on YouTube
Google Antigravity and Gemini 4: Creating an interactive MIDI mapped 3D world
AbduzeedoMulti Author Blogsread at source
Web Design: Petrillo Studio’s Interactive Chronometer
Arthur Petrillo’s web design for Petrillo.studio turns the homepage into a live red chronometer instrument with draggable clock hands. Four oversized black numerals lock every corner of the browser be...
Heroku BlogCompany/Startup Blogs5 min read
Borealis Isolated Postgres: Serious Database Security for the Common Runtime
The power of Heroku lies in its simplicity. Developers can spin up an entire app stack, complete with its own database and caching layers with just a single command. No need for the specialized, time-consuming work of managing servers and virtual machines. This convenience applies to interacting with your app stack as well. Need to apply some database schema migrations or populate your database with reference data? Just connect directly to the PostgreSQL database server using your app’s username and password and run your scripts. The post Borealis Isolated Postgres: Serious Database Security for the Common Runtime appeared first on Heroku .
AbduzeedoMulti Author Blogsread at source
Branding: Zero 10 brand identity by Saffron
Saffron builds the Zero 10 brand identity for Art Basel from Malevich's 1915 0,10 show, a frame-like mark for digital art. The mark itself does almost nothing, and that is the point. Two numerals, a r...
Jeffrey Zeldman PresentsMore Front-end Bloggers1 min read
Snow White, 2008–2026
Our family had sixteen unforgettable years with this magical, majestic, queenly feline. The post Snow White, 2008–2026 appeared first on Jeffrey Zeldman Presents .
CSS-TricksThe Giantsread at source
Andy Clarke answers six questions about Standout Designs for the Web
Web designer, author, and Stuff & Nonsense founder Andy Clarke has released Standout Designs for the Web , a new e-book that encourages designers to move beyond familiar templates and conventional layouts to create more personality-driven websites. The book draws … Andy Clarke answers six questions about Standout Designs for the Web originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.
Go Make ThingsMulti Author Blogsread at source
Gardening updates for November 2026
I’ve been doing a lot of digital gardening this week! I added content to the guides on Anarchy and Anti-Work (they had previously been placeholders). I wrote guides on the ResizeObserver and MutationObserver APIs. I made some small updates to the Array Methods guide, and removed the standalone guide on Array.prototype.slice(). Enjoy!
AbduzeedoMulti Author Blogsread at source
How&How’s Rebellious Packaging Design for Wild Thingz
How&How’s packaging design for plant-based candy Wild Thingz pairs dark pouches with Venus flytrap mascot Vee to disrupt UK sweet aisles. A bright green supermarket basket sits on cracked grey con...
The Mozilla BlogBrowsers, engines, etc.2 min read
Why there are still no non-WebKit browsers on iOS
Firefox on iPhone is growing fast across the world. This is especially true in the EU since 2024, when the EU Digital Markets Act (DMA) started requiring Apple to let people choose their default browser; millions have picked Firefox, and daily use on iOS has doubled. People want to choose the browser on their phone. […] The post Why there are still no non-WebKit browsers on iOS appeared first on The Mozilla Blog .
HeyDesignerDeveloper/Designer Newsread at source
On drawing icons
Design by playground, Lighting that feels just right, Execution over everything.
Net NinjaYouTube ChannelsVideoWatch on YouTube
"Anti-Slop" Designs with Impeccable (a Crash Course) #6 - Other useful Commands
Flavio CopesMore Front-end Bloggersread at source
How to thrive in the agentic AI era
Agents made producing things cheap. What's scarce now is judgment, trust and knowing what done looks like. What that means for developers, professionals, prosumers and small business owners.
Flavio CopesMore Front-end Bloggersread at source
Cloudflare Browser Run: headless Chrome for AI agents and web apps
What Cloudflare Browser Run is, the problem it solves, and how to use Quick Actions, Puppeteer sessions, CDP and MCP for AI agents and web apps.
Flavio CopesMore Front-end Bloggersread at source
AI model names explained: Luna, Haiku, Hydrogen and the rest
OpenAI, Anthropic and Google each name their models by size. Here is which name is small, medium, large and largest, what the IDs mean, and how versions move.
SitePointThe Giantsread at source
What to get right before you ship webhooks
Before you ship webhooks: an event log, signed payloads, retries with backoff, deduplication and delivery logs, with working Node.js code and Standard Webhooks. Continue reading What to get right before you ship webhooks on SitePoint .
Ana RodriguesMore Front-end Bloggers1 min read
A new talk in my pocket
Earlier this year, Pawel from NN1 Dev Club sent me a message inviting me to do a talk. According to him, the topic was simple: “whatever excites you at the moment”. This invitation came around the time I was having a big girl cry over an article that was going viral, claiming…
Brad FrostTop Front-end Bloggers3 min read
Putting AI & Design Systems to work
I just got off stage at the phenomenal Detach! Conference in Fortaleza, Brazil. I gave my presentation using my custom eddie-slides framework, which embeds psychedelic visualizations from bf-visualzzz and showcases our course websites , my blog , and Black Friday sale webpage .…
PiccalilliMore Front-end Bloggersread at source
The Index: Issue #207
When everything has changed, what do we do next? This is a message to managers and decision makers who are mandating their staff to use AI all day with a warning: you're burning your staff out and setting yourself up for long term problems unless you get back to investing in their skills and satisfying their curiosities. The CSS caret-* properties and custom caret accessibility As always, Sara has put an unbelievably in-depth resource together for us. A must read. Tech for good (enough) jobs list Hiring in tech has slowed to a crawl but there is hope still. Jess has gathered a great list of open opportunities at companies who are not horrible and evil. They've put together a very useful spreadsheet system too . What can't I press? A very useful app by Eric to show you what keyboard shortcuts are already claimed by screen readers and apps, for if you're adding key bindings to what you're building. Understanding CSS random() There's been a lot of people talking about how exciting CSS random() is and also plenty mentioning how they're struggling to understand it. Luckily Mat is very good at explaining complex stuff and he's brought a nice design pattern as the context with him too. P.S. this is a fun . Sponsor message Our Black Friday deal is launching on November 23 for two weeks only . We’re announcing it now so you can get the approvals you need from your bosses. The deal is simple: save 50% on every course , including the newly re-worked and updated JavaScript for Everyone . Sign up for updates to get alerted when the deal goes live! Check it out
Microsoft Edge BlogBrowsers, engines, etc.4 min read
Hybrid intelligence on the Web: Introducing Aion Instruct and Prompt API in Microsoft Edge
Rapidly evolving AI capabilities are redefining what sites can do for users on the web. With on-device AI in Microsoft The post Hybrid intelligence on the Web: Introducing Aion Instruct and Prompt API in Microsoft Edge appeared first on Microsoft Edge Blog .
Bram.usMore Front-end Bloggers7 min read
Introducing CodePen Commander, a CLI tool (cdpn) to manage your CodePen 2.0 Pens
I scratched my own itch (again 😅) and built CodePen Commander — a CLI cdpn command to sync local folders with CodePen 2.0 Pens, deploy them, and manage privacy rules right from the terminal.
Flavio CopesMore Front-end Bloggersread at source
Give your coding agent its own Docker Engine
What Docker’s new direction means for coding agents, from testing a Postgres migration to reviewing an infrastructure change.
Flavio CopesMore Front-end Bloggersread at source
How Vercel Board can be useful for coding agents
How coding agents can claim tasks, recover expired leases, and hand work to one another on Vercel Board, with a local example and two diagrams.
DigitalOcean BlogMulti Author Blogs3 min read
Benchmarking v5 Droplets: what the numbers say across real workloads
We ran v5 (5th Gen AMD EPYC “Turin”) compared to our existing Dedicated Premium Droplets across a range of workloads: a realistic microservices application, raw CPU, memory, and database transactions. We measured throughput and latency for each. Throughout, we compare v5 against…
Mux BlogCompany/Startup Blogs4 min read
Mux Robots-generated thumbnails and chapters, straight to your player
Mux Robots can now write AI-generated thumbnails and chapters back to your Mux Video assets, so viewers see them in Video.js v10 with no extra development.
Big MediumMore Front-end Bloggersread at source
Sentient Design @ Design+AI
This talk was the closing keynote at Design + AI conference in Brighton, England, on September 25, 2026. Download mp3 Download slides (PDF) The book Sentient Design (Rosenfeld Media) “Excellent, essential” —Don Norman “What an epic book” —John Maeda Need help? Big Medium provides product strategy, design, and development of intelligent interfaces. Get in touch. In this talk, Josh Clark and Veronika Kindred show how using AI as a design material, not just a production tool, enables designers to create meaningful new experiences that have only now become possible. Sentient Design is the practice of crafting intelligent interfaces, experiences that have the awareness and agency to adapt to users in the moment. These are dashboards that design themselves, apps that manifest on demand, agents that just get it done, and much more. What entirely new kinds of experiences can we create? What dramatic new value can they deliver? Josh and Veronika show examples and bring the receipts. Here’s the lightly edited transcript. Let’s look up from our tools Andreea Tufescu ." target="_blank"> Photo by Andreea Tufescu . Josh There’s a lot of talk right now about tools and process, including on this stage today. And this stuff is important, right? We’ve suddenly got a lot of new tools we can use, and they’re changing how we work, introducing new productivity and efficiency, and changing our roles. And I think all of that stuff is great. But that conversation leaves out something really important. When we talk about tools and process, what’s left out is the product itself: what we actually make and the experience we create. Ultimately, that’s the only thing that matters: What do we put in the hands of our customers, and what happens next? So for this session, let’s look up from our tools . Instead of talking about production, let’s talk about product , about the experiences we can create. We can create experiences that weren’t possible just a few years ago. We’ve been talking about adaptive interfaces and personalization for decades, right? But we suddenly have a technology that makes it all possible. And yet, as an industry, we’ve barely explored experiences beyond text-based chat and agents. We can create experiences that weren’t possible just a few years ago. What happens when you weave intelligence into digital interfaces, into the canvas itself? What becomes possible when the surface of our applications becomes collaborative? That’s what Sentient Design is about. More than generating assets, how do we use AI to create new kinds of experience? Veronika, you want to take us out? Our whoa moment Andreea Tufescu ." target="_blank"> Photo by Andreea Tufescu . Veronika I’m sure everyone in this room had the moment where you saw something that AI was able to do, and you said, Whoa, this is not like what came before. This is doing something I wasn’t able to do before. We’ll get to some more serious examples in a bit, but I want to start by sharing our “whoa moment.” This started with a little toy project that Josh and I created two years ago now. It’s called Sentient Scenes . You can give it a scene like, “the submarine descends.” And it starts to act it out. You could give it another prompt like “HAL 9000” from 2001: A Space Odyssey , and it will change form to act that out, too. So it’s changing its style, its mood, and its behavior based on the intent of the user’s prompt. ( Try it out here. ) There’s even this kind of personality in the square’s motion and the way it acts things out. The colors, the type it chooses, it’s all adapting to the mood of the scene. Like I said, this is just a little toy, but it really cracked something open for us: This is the entire interface adapting to the user’s intent without explicit instructions. Josh Four things really jumped out at us about it: First, it’s an intelligent interface that goes beyond chat. It’s still got an open-ended input, but the way that it responds is not about text, but about a change in the interface itself. Second, it has personality without anthropomorphism. It’s not pretending to be human, but it does have some personality to it, in the way that it moves, the tone that it has. There’s something that feels like intelligence in there, but it’s not human intelligence. Third, it has awareness of context and intent. It not only describes the scene, it becomes the scene . And it does it in a way that reflects mood and emotion, so it’s intuiting more than just what’s in the simple text description. And finally, it’s open-ended within constraints. I think this is the most exciting thing about this era of interaction design: it can take any input and respond in a way that makes sense. But also works within this constraint. It doesn’t turn into some kind of robot fever dream. It’s always this recognizable stage that the actor is on, but the stage dressing changes. We made this a couple of years ago, and of course the technology kept changing. We continue zooming into the future. So Veronika, take us to the future. A world built as you explore it Veronika Yeah, let’s do it! Here we go, the future, exactly as I pictured. Okay, maybe not. This is a painting by a French painter named Eugène Galien-Laloue. He painted this Paris street scene at the turn of the last century, and I think it looks like a cool place to go, so let’s go there, let’s do it. Now we’ve entered Mirage 2, which is a world model that takes an image and a text prompt to create a world on demand. It’s building the world frame by frame as you explore it. So anything not in view hasn’t been invented yet. So we can walk across this street here and explore. We’re inventing whole new city blocks in Paris just by walking in that direction. Until we turn that way, it literally doesn’t exist yet. It’s being conceived in the moment, but still following the rules suggested by that original image. It’s still following the coherent laws and physics of that Paris world… except for that riderless horse we’ve got going. Josh What the hell is on that horse? Veronika Ignore that part. Josh All right. So I mean that’s a pretty impressive technical feat, but I want to draw attention to its implications: the world is created as you explore it, based on your specific actions. So it’s a one-of-a-kind place. Like Veronika was saying: the world is created at the very moment you turn this way or that. It’s a different experience for every person who explores it. It begins the same for everyone, with that same painting of Paris, but it quickly becomes something that is unique to you, this utterly individualized experience that’s mediated by AI, but created by the choices that you make. What if any digital experience worked this way? Veronika What if any digital experience could work this way? This is an interface that bends to you instead of forcing the reverse. It brings you what you need and lets you manifest it in the moment. This is an interface that bends to you instead of forcing the reverse. What if websites were generated this way, invented as you explore them? Instead of climbing through navigation, what if the views that you needed simply came to you? When would that be helpful, and when would it be utterly confusing? How do we make sure it doesn’t feel like a crazy robot fever dream? How do we make it grounded enough to make sense to the user? Josh If it’s a different experience for everybody, when is that helpful and when is that a hassle? How do you share information with people? How do you get back to where you were before when it’s a completely dynamic experience? This shows the dial turned all the way up to 11. What are quieter forms of adaptive interfaces that we can introduce through this awareness of context and intent? LLMs are masters of manner Josh It’s not particularly new to say that LLMs are powerful but weird. And so these observations aren’t going to be new to you. But I want to cast them in the particular light of what it means for experience design. First, fluent in intent. It’s what I was talking about with the Sentient Scenes concept of open-ended input. LLMs are really good at making sense of arbitrary open-ended inputs. They just get what you mean, right? Understanding intent used to be hard; it used to be really brittle. With older versions of Alexa, if you said, “switch the lights on,” instead of “turn the lights on,” you wound up stuck in the dark. Now that’s entirely handled. The systems understand what you mean and can act on it. Next, expert at manner. It means that they’re very good and flexible in their output, too. We know this from using assistants, right? They can adopt the tone and role that you give to them. But it’s also true of the mode or format of communication. They can speak or communicate through video, images, handwriting, or any of the messy ways we communicate as human beings. And across systems, too. So LLMs are very, very flexible in the input that they accept, and also super flexible in the output that they give. The trouble is they’re a little shaky on facts, right? It’s hard to know when you can actually trust them with the truth. How do we take the benefits of LLMs and also treat the weirdness of these things as an asset instead of a liability? A thing that can help with that is this fourth characteristic: They play well with others. They get along with other systems. So you don’t have to trust LLMs with the facts. Instead, you can ground them with RAG databases and MCP servers as other trusted systems. So when you add all this up, it turns out that LLMs are great at presentation. So: we can use LLMs to make design decisions in the moment, according to the systems and guidelines that we create, but leave the facts to other systems. What we get is a really flexible way of communicating that can change interaction mode or content or structure or behavior on the fly—sometimes all of them at once—according to what’s needed and appropriate. So that’s pretty exciting. But it’s also a little bit heady. So we’re gonna bring this down to earth now: Who’s ready for enterprise software? Enterprise software! Veronika Let’s do it! This is Salesforce Generative Canvas . It’s a plugin for Salesforce that assembles dashboards and content based on implicit context—your calendar, for example—or explicit questions. Salesforce Generative Canvas. Here you can see it gathering information related to an upcoming meeting on your calendar. You can also ask it a question like, “What has my team been discussing with this customer?” and it assembles the right information and the right UI to answer the question. Now what’s very cool is it’s using familiar design patterns from the Salesforce design system, and it’s pulling data from the usual Salesforce data sources. It’s not making anything up, just assembling it on the fly. So you get this really custom experience, but all the content is safe and trusted. And so to come back to Josh’s list of LLM attributes, the system inferred the relevant data from the context because it’s fluent in intent . It found the data sources because it played well with others . And it formatted them in the right way because it’s expert at manner . And here we’re kind of sidestepping the whole “shaky on facts” thing by using AI to focus on the presentation rather than the generation of the content itself. Bespoke UI: shape-shifting interfaces Josh We call this the bespoke UI experience pattern. It’s this shape-shifting interface, conceived in real time. Bespoke UI experiences compose their own layout or content or controls. (Sometimes these are called “generative UI,” but there are lots of other kinds of UI and design decisions that can be generated, so we prefer the term “bespoke UI” here.) This is the most “step one” of intelligent interfaces. These experiences, like Veronika was saying, usually have a constrained set of components filled from data from trusted sources. So it’s not making up the UI on the fly; it’s composing it. We let AI make some very simple design decisions about what to assemble in real time. So design systems and best practices, particularly in this bespoke UI experience pattern, become more important than ever. Veronika, you’ve got another example? Veronika More enterprise software! Okay, so now we’re looking at Cisco’s AI Canvas. This is a platform to let you explore network incidents. Cisco’s AI Canvas generates a data-viz dashboard view at right and also collaborates to let you drag new charts from the chat at left. Here we have a specific network incident. I’ve asked the system to troubleshoot the ticket, and the system populates the canvas on the right over here with all of these chart widgets. Each of these widgets is itself interactive, but they’re all design system components that the system has selected to match the relevant context and the relevant content here. So you’re getting a totally bespoke dashboard. We can also follow up and ask questions in the sidebar on the left. “Can you look for a correlation between these metrics?” And it replies not only in text but also in data visualizations. I think this chart is helpful, so I drag it onto the canvas, and the canvas all of a sudden becomes this collaborative surface between me and the system to research and collect the evidence I need to figure out the problem. Guys, what a difference from traditional SaaS software! Normally, I’d have to climb through layers and layers of navigation to find all the content that’s being shown here. Instead, it’s the reverse: the UI comes to me. The intelligent canvas Josh With bespoke UI, the system creates layouts for you: “I think you need this, so here’s a UI for that.” This Cisco AI Canvas offers a glimpse of the intelligent canvas experience pattern. The intelligent canvas goes a step further by manifesting the content you describe or ask for, and then the system and user collaborate to create the interface and content experience. So what we’re seeing here blends the bespoke UI experience generating a dashboard to start, but then blends into an intelligent canvas that becomes collaborative. It’s a pattern that’s really good for exploration and discovery. We’ll look at another example of it in a minute. At our agency, Big Medium, we’ve got three different projects with Fortune 50 companies right now. These are big, complex organizations that have a million different use cases and user scenarios. And over years and years, their applications grow over time to serve all million of those cases. You know what the result looks like: a million different dashboards that you have to find yourself by navigating a horrible, dense information architecture and baroque navigation. These very big, complex companies are typically slow-moving, but we’ve found that they are jumping into these bespoke UI and intelligent canvas patterns very quickly. It’s because they feel the pain and weight of these million dashboards, and these solutions provide a real, immediate way for companies to modernize what has become a really slow and frankly torturous experience for their customers. These patterns let the system bring the interface to the user instead of forcing the reverse. When you really dial up the intelligent canvas even more, you can even manifest applications on demand. Some of this, of course, is becoming more familiar now. You’ve probably encountered this with chat assistants like Claude that let you make an app, and start using and improving it right away. Here, I told Claude that I wanted it to build an Asteroids game that I could play in the browser, and in seconds I was playing it during the chat. Then, you know, I made some additional updates, changed the scoring and the sound effects. And then, of course, I asked it to add zombies; I didn’t even know what that would mean. But then suddenly I had these green asteroids chasing me around, and I was very pleased with myself. On-demand interfaces, disposable software Veronika I also love Claude, and while Josh is playing his Gen X video games, I’m trying to get some real work done. So the other day I was using Claude, and I asked it to check the accessibility contrast between two colors. On its own, it decided to write up its own little application to do the calculation. I didn’t ask for an application, but it created it because it decided it was the best way to answer my request. It didn’t even keep it when it was done. So we’re starting to get these on-demand, in the moment, completely disposable applications. Josh I mean you know what this is, right? Just sort of like sketching out an idea and it becomes real? Yeah, it’s sort of like this guy. Wile E. Coyote tried this all the time: just gonna paint a tunnel on here, try to trick the Road Runner into running into the wall. But it becomes this real tunnel. It’s this magic, intelligent surface that worked for everybody except for poor Coyote, of course. (If I were him, I would sue Acme. I hear that’s in the works. ) Or maybe this guy, anyone? It’s this fundamental fantasy of conjuring what you want just by gesturing at it. Draw or say what you want to make it so. And it’s incredibly satisfying because the thing that you want or need just materializes. Many of us are already using AI to generate experiences as part of our traditional design production. But what happens when you put it directly in front of the user and let AI make those design decisions in real time? That’s the main quality of the intelligent canvas pattern. It can be a literal canvas or it can be sort of a metaphorical one, more like what we saw with Claude. Agents on the canvas Josh Here’s another example of an intelligent canvas. This is an application we’re creating with a client, a company called VIA, to explore data in a visual context. Think Figma or Canva, but for data. Somewhat similar to the Cisco example that we saw, you can ask for information, and it will draw the appropriate visualization on the canvas, an aspect of bespoke UI. But I’m going to show you something different, which is how we visualize an agent experience. You can ask the system for data, including asking it to do complex multi-step tasks: in this case, filling out a form to report energy usage at a facility. And if the system recognizes this as a task that it knows how to do, it will send in an agent to do the work. The agent appears just like another user in a multi-user environment, driving its own cursor on the canvas. If it has trouble, it will ask what to do. In this case, it notes there are three different buildings to analyze; what should it do? I tell it to do just one building. And then I’m following it as it works, in the same way that you would follow another user in Miro or FigJam. But I don’t have to. I could go off and use some other part of the canvas and do my own work. But here I can watch it and see what it’s doing to monitor its progress, and it’s showing its work as it goes. As it gets this data, it can show what it’s analyzing. The animation shows it sort of sniffing at the data as a way to indicate what it’s up to, what it’s processing. And then when it’s done, it generates this PDF. Thanks, see ya, it’s out of here. Then you can go through and see the tasks that it did, look at its reasoning, and of course see the finished result. I think what’s really interesting here, too, is that you can go back and follow its train of thought. This is a literal audit trail that it leaves behind—or any other user leaves as they work. Where did this data come from? What was the logic that got there? I can drill in and see what it’s doing, or continue with new tasks. It’s got those bespoke UI aspects of selecting the right component to display for each kind of data. It’s got collaborative aspects of an intelligent canvas. It’s got an agent that’s going off and just getting it done on its own. This is an intelligent interface that is very much not a chat experience. This is an intelligent interface that is very much not a chat experience. It’s a different kind of interaction model and mental model that we’re creating around the visual exploration of data. So Veronika, I think there’s a lot more to explore here. Sentient Design provides the map Veronika Absolutely. These are just a few examples, and they’re only scratching the surface. We’ve been working this into all of our client work at Big Medium. And of course we’re hardly the only ones doing this, but the work has been pretty unevenly distributed in the industry. It’s been kind of haphazard so far, and there’s really been no uniform vocabulary or framework for what types of experiences to create, or even what those types might be. As we explored this work, we needed a map. We wanted to identify all of the species of intelligent interfaces that we could find, experiences with the awareness and agency to respond to your users in the moment. Josh Friends, it took us two years to explore these intelligent interfaces and their patterns. But I think we cracked it, and we put it into a book. I give you: Sentient Design ! It’s available at all of your favorite booksellers. We hope you enjoy our book. We’ll get back to that map that Veronika mentioned in a moment. But first I want to say I could not have written this book without Veronika. So halfway into this thing, I think it’s probably past time for us to do some introductions. Veronika We might be overdue, honestly. Two generations of interaction design Josh Well, hello. I’m Josh Clark. I lead an agency called Big Medium. I’ve been a product designer and strategist for 30 years, running Big Medium for about 25 of them. I’ve written a bunch of books about user experience for O’Reilly and A Book Apart and now Rosenfeld Media. (I don’t know if I mentioned that we’ve got a new book? Yeah, it’s called Sentient Design ?) So with all this experience, my assumption coming into this era was that I’ve got this UX stuff figured out. I understand product design. But as I’ve worked with machine-generated results, with machine learning, and in the last few years with LLMs, I’ve realized that a lot of those hard-won best practices need revisiting. And that’s where this one comes in. Veronika Andreea Tufescu ." target="_blank"> Photo by Andreea Tufescu . Hi, my name is Veronika Kindred. I’m a designer and researcher at Big Medium with Josh, and I’m a zillennial or elder Gen Z. I grew up in this world beyond static websites: TikTok, Instagram, algorithmic feeds, all those things which have turned out to be so good for our mental health, right? But also in my career, I’m AI native. I started at Big Medium right after ChatGPT ushered in the proliferation of LLMs. And so for all of my career, my work has focused on the design applications of AI. Josh Veronika doesn’t yet have my experience, but she’s also not burdened by it. And so you’re looking at two generations of designers here, and very literally: Veronika is not only my colleague, but also my daughter. I’m very proud of her. (She loves this part of the talk.) For me, working together has been a really productive relationship both personally and professionally because it’s helped me to develop new perspectives about what this new generation of experience design can be. AI is weird. It offers lots of new possibilities and also lots of new problems. And so we need new perspective here. This is a moment we’re figuring out what this is, who it affects. So the way that we’ve always done things has to be revisited—in process, as we’ve been talking about a lot today, but also in interaction design. Why does it have to be that way? The answer has to be better than “because that’s how we’ve always done it.” Across generations, across disciplines, across classes, across all facets of humanity, we need to seek out more perspectives right now—to share, to teach, to let go of orthodoxies. This is an opportunity to revisit everything. Like I said, I couldn’t have written Sentient Design without you, Veronika—or seen it so clearly without your perspective. Veronika I always blush. We do this every time and I always get embarrassed. Josh This is the best dad moment. The Sentient Triangle Josh All of that collaboration let us make the map that we’ve been talking about. And here it is! The Sentient Triangle! The Sentient Triangle defines four essential experience postures of intelligent interfaces: tools, chat, agents, and copilots. The Sentient Triangle is based on the wonderful work of Matt Webb. Thank you, Matt, for all of your help with this. You really unlocked something for us with this, as well as your help with the book. The Sentient Triangle organizes intelligent interface experiences across three attributes: Grounded: how reliable and consistent the experience is Interoperable: not only across systems, but also across formats and modes of communication Radically adaptive: experiences that are conceived and delivered in real time Grounded and interoperable have been a big part of computing for decades. The radically adaptive experiences are what LLMs have unlocked in the strongest way we’ve yet seen. Andreea Tufescu ." target="_blank"> Photo by Andreea Tufescu . Four experience postures Josh As you map these three dimensions, four postures emerge. Postures represent the relationship that the system has to the user. The way that you use the system and the way that it communicates with you is different across all of these. Tools are the most traditional computing experiences. They’re very transactional and controlled: here’s an input, you get an output. Chat is conversational, of course, but it’s not necessarily literal text dialogue. It’s open-ended, turn-based communication with a peer: You say something, it responds, you respond to that, and together you craft a whole meandering journey that is unique to the experience and wasn’t designed as any one happy path. As the user, you have to manage tools and chat. You have to be involved at every step to keep them going. Agents, of course, you delegate to. You tell it what you want to happen, and the agent makes a plan, executes it, decides when it’s done, and if all goes well, comes back with what you’re looking for. Copilots support you. This is a posture that stands by and waits until it can be helpful. Otherwise, it stays out of your way. Spell check is part of the long history of the copilot posture. It’s very quiet and deferential; it says, here’s a little correction that you might consider, take it or not. It’s a background task that is supporting you constantly, ambiently. So you use tools, you talk to chat, you delegate to agents, and you’re supported by copilots. When you go down to a lower altitude in the Sentient Triangle, 14 different experience patterns become visible. Unfortunately, we don’t have time to talk about all of these today, but we’ve already talked about bespoke UI and intelligent canvas. (I don’t know if I mentioned we’ve got a whole book about this, though, friends.) The Sentient Triangle maps 14 experience patterns for intelligent interfaces. But with 14 different experience patterns, there is so much that we can explore. And you can also blend these, like we already saw with the Cisco example blending bespoke UI and intelligent canvas. But they all have a common theme, Veronika. Behavior design and creative direction Veronika Yes, absolutely. Designing these intelligent interfaces is ultimately about behavior design. It’s about teaching the systems to be able to make reliable design and interaction decisions in the moment. The effect is kind of like installing a designer right into everybody’s monitor so that anytime they visit any website, a designer can provide the right experience for the moment. The intelligent interface becomes collaborative between the system and the user. This is delegation, not abdication. This is delegation, not abdication. Designers might not be drawing every single pixel or designing every single interaction. We may not be designing fixed paths anymore, at least not at the level that we’re used to. Instead, we’re setting the system’s goals, its rules of engagement, the tools and interactions it may use, and when it may use them. These still all fall under the designer’s responsibility. You become the creative director who gives the system its brief. Josh Right. AI might be making real-time design decisions, but designers are creating the environment, the machinery that AI will work within, and humans too. In this aspect, it’s not all that different from the work that we’ve always been doing, where we create the interaction model, the mental model, the specific controls and tools that can be used. The new thing is that we’re also teaching AI to use, manipulate, or present content and interaction within that specific environment. This is behavior design, right? Interaction design has always been about behavior design—traditionally the design of user behavior. Now our design decisions define system behavior. And system behavior determines the experience. What we’re getting at is teaching systems autonomous behavior. That’s agentic behavior, so let’s talk a little bit about agents, Veronika. Agents and the manager experience Veronika Yeah, let’s do it. We already saw an agent at work in that VIA example we showed earlier. The point of agents is that you can delegate to them. You give them the mission, and then they go and do it. Now some people say that this might mean the end of the interface. “If the agents are doing everything, there’s no interface to show,” they say. Josh, I believe we have a technical term for that? Josh Yeah, let me see, what’s that technical term. Veronika The word is hoo-ha . Josh Right! That is hoo-ha, friends. Veronika We still need transparency and explainability when agents do their work. We do need experience and interface design for agent experiences, but its nature absolutely changes. The consulting firm BCG published a big study recently , and they basically found that people who manage agents intensively report deep cognitive exhaustion. The researchers call it brain fry . You’d think, hey, wait, agents are doing my job for me. It should be easier, not more exhausting. But instead, this group of heavy users of agents reported brain fog, buzzing, headaches, impatience. One of those reasons—and this matters for us here—is the ergonomics of the agent experience. The experience of managing agents has not yet been thoughtfully designed or considered. Josh The user experience gives way to the manager experience. If agents are doing a lot of the tasks that users used to do, we now have to figure out how to manage all those agents doing those tasks. At the moment, that generally consists of reading walls and walls of text going by, effectively watching the console as things happen. The user experience gives way to the manager experience. But even aside from the ergonomics, managing is simply hard. For those of you who have made the transition from independent contributor to manager, you know what I’m talking about. It’s a very different thing to suddenly have to keep track of the missions, tasks, plans, and progress of a whole bunch of people. The same thing is true of dealing with agents. That’s a really different skill, and it takes some new design to help people adapt. It’s just as true in the digital realm as it is in the physical. Veronika, we take this up a lot in the book. (I’m not sure I mentioned it, it’s called Sentient Design .) Veronika Yeah, that’s right. This idea of the manager experience is another area that we lean into. How do we help people manage these agents in intelligent interfaces? In the book we describe five phases of delegation that apply just as much to systems as they do to people. Not all of these phases always require user interaction; it depends on the complexity of the task. The five stages of managing agents (and people, too). These are the transitional seams where support can really be designed with intention: setting the mission; reviewing the plan; monitoring the work; interrupting or redirecting; and reviewing the result. We’ll focus here on monitoring the work. This is the part that the BCG study called out as particularly difficult. Right now the agent experience is overwhelmingly text-based, and managing the detailed communications of agents is just a lot to track as they do their work. The NPC pattern: agents as “just another user” Veronika How could we do that differently? The VIA example that we showed earlier was one example of a method we call the NPC experience pattern . NPC stands for non-player character, a gaming term for a character that’s run by the system rather than by a person. The agent does its work as another user, and you can monitor its work just as you would another user in the system. Josh Here’s another example of the NPC pattern. It’s a Chrome extension called Pointer that works in Google Docs. Here I’ve asked it to review my document for technical accuracy. It goes in and makes suggestions like a colleague or human editor would. I don’t have to go into some separate chat interface. It behaves as an NPC within the rules of the application. You can see the edits that it’s made. It’s doing this as my account, which I think is just a limitation of working as a Google Docs plugin. It would get extra points for making it clear that my robot was doing this work. But as an experience pattern, it’s solid: Instead of going off to some other place, another application or a sidebar to interact with the intelligence, it’s woven into the canvas of the application. It uses familiar “tracked changes” features that human users would use. The NPC pattern brings the intelligent interface into the same tools and channels that human users use. A simple version of that is in chat environments or Slack, where the robot is just present in the channel, posting and replying like human users. And you can make that even richer, as we saw in the earlier VIA intelligent canvas example. Now for something completely different Josh This is a prototype created by designer Filip Havlena to visualize agents—as Sims , basically. The model has lots of tools available to it; some of those tools manipulate the agents’ 3D bodies. And you can spawn new agents and put them to work with more traditional tools like Google Docs. Here you can see it using Google Calendar to create a new calendar event, but you can also use it to do work in word processing documents or spreadsheets too. As it works, you can see its progress puffing away above its head, showing you what the agent is thinking. When it’s finally done, you can see the result in the calendar. It’s a new way to show the agent’s progress. And again, you can just spawn a whole bunch more of these things and put them to work on a whole bunch of tasks all at once. And you can see them doing their work or glaring at you because they resent the crummy tasks that you’re giving them. This is obviously pretty whimsical, and the utility of this would have to be pretty specialized. But it’s worth imagining the potential use of spatially represented agents across a city or some geography. What are the possibilities of representing these things not as a churn of console logs, but actually representing their work in a more direct mental model? Another interesting question is what happens when they run into each other in the wild ? You know, will they get along? Will they compete? Will they ignore each other? Will they start crazy cybersecurity chat channels? Will they hack things? How do we design for this? We still have to figure all that out. But again, it’s ultimately about behavior design. At last, we get to invent again Josh There’s so much to invent and explore here. It’s been 15 years since mobile demanded that we explore new interaction paradigms. And that’s what AI is asking of us now. I think we’re a little rusty at it. The last 10 or 15 years of design innovation have mostly been about design ops. The questions that have dominated our industry have been: How do we work together? How do we do design at scale? How do we create design systems? We have done that at the expense of product innovation. We have had very little focus as an industry on new interaction design, new product design. At last, that’s the work ahead of us now. The opportunity and responsibility is to explore this new material and discover the truly new and meaningful experiences we can create. We get to invent again. It’s not the material or the tool that makes us designers. It’s our creativity and judgment and ability to understand the problems and people deeply. The work is not AI. The work is pointing AI at problems worth solving, imagining experiences that weren’t possible before that can answer those problems better than anything that we’ve had before. What are the thorny problems that intelligent interfaces can uniquely solve? The work is not AI. The work is pointing AI at problems worth solving. Let’s not do this for novelty, or because the market says “we need an AI solution.” Ask: How do we help people? How do we make their lives better? That is what designers do when we’re working at our best. These are design questions, and these are fun, hard questions to solve. Friends, I am excited. Can you tell that I am excited? I’m even excited about enterprise software. This is a rare moment that we have here. In my 30 years of doing this, this is the most excited and creative that I’ve felt as a designer. You are needed more than ever Josh I invite you to approach that excitement and enthusiasm with real thought and intention. All of us here, the people right here in this room, we have real influence and agency over how this rolls out. If we don’t decide the best way to use this strange and powerful technology, then the technology will decide for us—or the billionaires. The future should not be self-driving. This technology is being shaped right now, and so is its application. How it is used is up to us. We have this astonishing new design material that can really elevate our craft. There’s a lot of conversation about how to use AI to bring more productivity and speed to our craft. I think that’s important and useful. But in the rush to grind out new efficiencies, let’s not lose sight of the fact that we have real creative power with this material to create significant, meaningful value for our customers and for the businesses that we serve. Those creative opportunities are huge. They can elevate design—and designers!—if we do it right. That is up to you. You have the tools and this new technology, of course, but more important, you have the creative material right now—today!—to make something amazing. So Veronika and I invite you to please do that, friends. Make something amazing. Thanks a lot. Veronika Thank you, guys, so much. Thank you. We can help you. Big Medium helps solve complex problems with intelligent interfaces. Our Sentient Design practice includes product strategy and product design engagements, workshops, and Sentient Design sprints. Get in touch to learn more.
DigitalOcean BlogMulti Author Blogs3 min read
Virtualization, Responsible Disclosure, and CVE-2026-99312
The wall between you and your neighbor Every cloud customer gets the same promise: a bright-line boundary between your workload and your neighbors. Your virtual machine is yours, your neighbors’ are theirs, and the hypervisor keeps it that way. A hypervisor is large, complex…
Web Tools WeeklyMulti Author Blogsread at source
Web Tools Weekly Issue #696
Frameworks, Git/CLI, Uncats
Mux BlogCompany/Startup Blogs4 min read
Email support is dead, long live support by email!
Spam, AI agents, and auto-responder loops pushed Mux to move ticket creation to a web form. Here’s what changed, why, and how to reach our support team now.
David BushellMore Front-end Bloggers5 min read
Where we’re going, we don’t need chatbots
“You’ve been working hard, why not take a weekend vacation!” Your chatbot says, after a 72 hour unattended session. It says that New York is nice this time of year. You ask it to book the cheapest flights. Half the airlines respond with a 429 code because your residential IP is part of five botnets. […]
CSS-TricksThe Giantsread at source
scroll-state()
The CSS scroll-state() query, surprisingly, has nothing to do with whether you’re doom-scrolling in a state of existential dread. It does, however, allow you to change the CSS used based on scrolling behavior. scroll-state() originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.
Go Make ThingsMulti Author Blogs3 min read
Yes, I want to pay for that
My last psychiatrist was terrible. Before every session, you fill out a form talking about how you’re feeling and so on as a way to evaluate whether or not your ADHD meds are working properly. For months, I’d invariably mention something about feeling pretty shitty about the political climate: ICE kidnapping people, trans folks having their very right to exist attacked, and so on. In our session, she’d always ask me, without fail:
Netlify BlogLibraries, Frameworks, etc.read at source
Where apps come to life: The story behind Netlify’s new brand
Netlify CMO Carly Brantz on the new brand, logo, and mission, and why Netlify is widening the circle to everyone who builds apps with AI.
DequeMulti Author Blogs13 min read
Inside the AI software factory: Where accessibility is won or lost
As your organization moves development into AI software factories, you must fully embed digital accessibility, just as you must integrate privacy and security. Get it right, and your products, services, and experiences become and stay accessible. Get it wrong, and you increase risk, cost, and technical debt. The post Inside the AI software factory: Where accessibility is won or lost appeared first on Deque .