Tools, platforms and infrastructure of the agent ecosystem.
53 fiches · 131 entities · Updated
The agent ecosystem rests on concrete tools, platforms, and infrastructure, and cataloging them is the work here. Coding assistants and autonomous agents; the runtimes and orchestration layers beneath them; the connective tissue — protocols, model-context interfaces, IDEs, CI integrations — that lets them touch real systems: each gets examined for what it does and how its harness is built. The consolidation of assistants, runtimes, and context protocols into fewer stacks is a running thread, as is the question of which layer captures the most value. Where a tool sits in a workflow matters as much as raw capability. This is the technical substrate of AI-assisted development, described as it is actually assembled.
Key figures
$0.10 / 1M tokens input, $0.40 / 1M tokens output
Gemini 2.5 Flash-Lite · stated in source
1 million token context window
Gemini 2.5 Flash-Lite · stated in source
$3 million raised (May 2025)
Plakar · stated in source
28.3 on Terminal-Bench 3.0 vs 4.6 for GLM-5.2, 66.9 on DeepSWE v1.1 vs 46.2, and 28.5 on Agents' Last Exam vs 23.8
Guest post by **Andy Warfield**, an engineer on the **S3** team at **AWS**, published on **August 26, 2026** on *All Things Distributed*, **Werner Vogels**'s blog, who introduces it in a few lines signed "--W": **3,554 words** per the page. The text serves as the vehicle for the announcement that **DuckLabs**, the team behind **DuckDB**, is joining **AWS**. (A) The thesis: systems computing is about seeking the elegant trade-off against a moving "physics" — the ratios between memory speed, network, and compute — and that physics has changed. Warfield quantifies the gap: an **m1.xlarge** from 2007 offered **15 GB of RAM**, **4 virtual cores**, and **~1 Gb/s** of network; an **m8g.48xlarge** today offers roughly **50×** more of each of the three. Dataset growth, meanwhile, follows a distribution whose tail consists of very large volumes. (B) The consequence: distributed processing — **MapReduce**, **Spark**'s **RDDs** — was designed under the I/O constraints of the early 2000s, and much of the work assigned to it no longer needs to leave the application. Hence the embedded, in-process library engine, running in the application's address space, of which **DuckDB** is the example. Warfield anchors this in the *Scalability! But at what COST?* paper (2015) and **Paul Barham**'s epigraph: "You can have a second computer once you've shown you know how to use the first one." He states an explicit caveat: "When a job genuinely needs a thousand machines, it needs a thousand machines." The corpus already holds [[vogels-tech-predictions-2026-allthingsdistributed-2025-11-25]] from the same blog and [[anthropic-self-service-data-analytics-claude-agentic-stack-2026-06-03]] on self-service analytics.
#DuckDB#DuckLabs#AWS acquisition
Andy Warfield · ingénieur du service S3 chez AWS · en billet invité sur *All Things Distributed* ; introduction de Werner Vogels · CTO d'Amazon.
Corporate blog post from **Block** (`block.xyz/inside`), unsigned — the displayed author is **"Block"** —, published on **August 18, 2026**, ~930 words, announcing **the open-sourcing of Berd**, Block's internal desktop application for working with agents, and laying out the design thesis that guided it: giving agents character *"not only through roles, instructions, skills, and tools, but through distinctive visual identities"* — hence the in-house animated characters, the *"Gloopies"*. The post starts from an observation of fragmentation (*"The technology was powerful, but the experience around it was fragmented"*) and a precisely named interface problem: *"the product gives people little sense of how the agent is configured, which context and tools are available to it, and how it differs from another agent"*. Two structuring contributions. **(A) A three-tier articulation**: **goose** remains the framework and *runtime* that holds the agent loop; **Berd** is the desktop client (projects, context, sessions, agents, configuration); the two communicate via the **Agent Client Protocol**. **Buzz** is designated as the follow-up, for when solo work becomes collaborative (*"Start alone, then go multiplayer"*). **(B) Six requirements handed off to Buzz**, stated as a takeaway: *"private space, durable context, recognizable agent identities, reusable skills, visible configuration, and clearer visibility into an agent's configured context, tools, and capabilities"* — a grid directly reusable for evaluating an agent client. The text itself distinguishes identity from capability: *"The avatars make the agent recognizable. Its role, skills, and tools make it useful."* No usage figures are produced and no license is named for the open-sourcing.
#Berd#Block#open source
**Aucun auteur nommé** : le billet est signé **« Block »** — le champ *Author* de la page porte le nom de l'entreprise. Publié le **18 août 2026** sur `block.xyz/inside` · le blog **corporate** · et non sur `engineering.block.xyz`.
Blog post from **Sonatype** by **Aaron Linskens** (*technical writer*), published on **August 18, 2026**, ~1,300 words: it recounts a **Sonatype Research Labs** study spanning **49 months** (June 2022 — June 2026) and a **fixed cohort** of enterprise applications, a methodological choice asserted to isolate the evolution of the application fleet rather than that of the customer portfolio. The result is presented as a contradiction: remediation is faster, yet risk accumulates further. (A) **The stock is rising** — *Critical* and *High* vulnerabilities per application **×4.31** (from **14.14** in June 2022 to **54.3** in 2026, still **×3.91** excluding legacy applications newly brought under management), newly affected component versions at **46×** the pre-AI rate, monthly application creation **×4.84**. (B) **Remediation is improving** — more than half of resolved violations are resolved in under a day, the median age of unresolved *Critical/High* vulnerabilities drops from **228** to **126 days**, then to **103** in May 2026; among cohorts that had twelve months, **52.6%** are resolved, **44.3%** open, **3.1%** under waiver. (C) **The proposed lever is component selection**: at the moment a vulnerable dependency was chosen, a substantially less risky version already existed in **62.2%** of cases on **Maven**, **46.9%** on **npm**, **34.3%** on **PyPI** — a gap the text attributes to an information gap rather than developer fault. The post itself states that AI is not the sole cause of the acceleration, and concludes on **Sonatype Guide**, which brings this intelligence to the point of selection. On the supply-chain side, it extends what [[fiches/2026-08/staples-gitlab-when-code-is-abundant-2026-08-24]] frames in economic terms and [[fiches/2026-07/clinton-anthropic-secure-ai-native-sdlc-2026-07-21]] in secure-cycle terms.
#software supply chain#software supply chain#Sonatype Research Labs
Aaron Linskens · *technical writer* chez Sonatype · sur le blog de l'éditeur ; les chiffres sont produits par Sonatype Research Labs · non par l'auteur.
Product announcement post from **Block Engineering** signed by **Thomas Petersen** (*Principal Designer & Builder*), published on **August 18, 2026**, ~1,800 words across thirteen short sections, introducing **Buzz Projects** — a **software forge hosted on its own relay**: Git repositories, branches, pull requests, issues, review and merge, multi-repo projects, an activity feed, all linked to conversation channels. The post's standfirst and thesis: *« Coding agents are the terminal for your computer. Buzz is the terminal for your network. »* Three contributions. **(A) A trust doctrine grounded in *ex post* proof rather than *ex ante* authorization**: on one side *« No forced guardrails, no limitations on what your agents are allowed to help you with »*, on the other *« Every push, review, approval, and merge is a signed Nostr event. If an agent authors a patch, you can see which agent produced it and which human authorized that agent to act »*; the section closes on a stated direction — *« we are already exploring ideas around agent trust protocols informed by past behavior »*. **(B) Git interoperability without proprietary tooling**: *« These are standard git repositories… You can fetch, clone, pull, and push over plain Smart HTTP, with no custom tooling or wrapper CLI required »*, with the clé Nostr serving as a single identity — *« The same npub that signs your messages signs your pushes. »* **(C) A distinction between execution surface and network presence**: *« A terminal gives an agent somewhere to execute commands and change files, but it does not give it a persistent place in the network. Buzz does. »* The post produces no figures and contains no outbound links; it qualifies itself as preliminary six times (*« still very basic »*, *« fairly elementary »*, *« still under experiments »*), and Projects lives under the **Experiments** tab of Buzz Desktop.
#Buzz#Buzz Projects#Block
**Thomas Petersen** — *« Principal Designer & Builder »* chez **Block** · auteur unique et signataire du billet ; première apparition dans le corpus. Publié le **18 août 2026** sur le blog **Block Engineering**. Troisième signature Block sur Buzz en un mois · après Tyler Longwell (21 juillet) et Atish Patel (6 août) · et la première non-ingénieur.
Announcement post published on the **official Z.ai blog** (formerly Zhipu AI, Chinese lab) on **August 14, 2026**, **with no individual byline**, ~2,000 words plus footnotes. It announces **GLM-5.3**, successor to GLM-5.2, opening with a methodological thesis: *« Scaling post-training is all we did for GLM-5.3. »* Same base model as GLM-5.2 — *« every gain comes from post-training »*. Three announcements. **(A) An open-weights coding model**: +50% claimed on **Z.ai Code Bench**, an unpublished in-house benchmark. **(B) A cyber capability presented as "emergent"**, which the body of the text traces to a training choice — *« As part of post-training, we introduced vulnerability discovery data and environments into the training mix. We expected this to make the model better at finding and reasoning about vulnerabilities »* — what came as a surprise was the speed and the change in nature: the model moves from identifying isolated flaws to *« coherent plans for complete exploitation chains »*. Gains grow with position in the exploitation chain: CyberGym 77.2 → **84.5%**, ExploitBench 24.4 → **54.4%** (×2.2), ExploitGym 29 → **105** tasks in 2h (×3.6), with the gap to the closed frontier remaining wide (181 and 247 tasks). Z.ai puts it this way: *« Capability is growing fastest exactly where we are furthest behind. »* The post also publishes a **Z.ai Security Disclosure Ledger**: **2,436 vulnerabilities identified across 269 open source projects** — kernels, OSes, browser engines, infrastructure, web applications, network protocols — the oldest introduced in **1981**, average lifetime before discovery **26.6 years**, of which **53 disclosed** and **2,383 under embargo**. **(C) A weight release** *« within two weeks of launch, once safety evaluation and hardening are complete »*. The most reusable methodological contribution: **environment and verifier synthesis**, the latter produced without access to the reference solution and admitted only after a triptych of negative controls — **oracle**, **no-op**, **unsolved-state**. All agentic evaluations are conducted **in Claude Code 2.1.207**.
#GLM-5.3#GLM-5.2#Z.ai
**Z.ai** (anciennement **Zhipu AI**) · laboratoire d'IA chinois · éditeur de la famille **GLM**. Billet **institutionnel et non signé** : aucun auteur nommé · aucun chercheur mis en avant · aucun lien vers un rapport technique ou une carte de modèle. Publié le **14 août 2026**. La page est une SPA React — le HTML servi est un `<div id="root">` vide · et le texte comme les scores ont dû être extraits du bundle `glm-5.3-BCnx8T5_.js` · où ils figurent en valeurs source.
Official product page from **DeepSeek**, published on **August 13, 2026**, **unsigned**, ~450 words, announcing the *developer preview* release of **DeepSeek Harness** (`dsh`) — a coding-agent harness **open source under the MIT license**, whose repository opened the same day. A three-word thesis, repeated in the title and in the repository description: *« Everything is a plugin »*, paired with a second promise, *« Every run is traceable »*. The page states the equation *« AGENT = MODEL + HARNESS »* and lists the pluggable capabilities — *« models, tools, skills, sessions, sandboxes, storage, loops, scheduling, and the UI »*. Four modes ship: **Standard** (full coding agent), **Code** (tools exposed via the *Code Mode SDK*, letting the model compose multi-step operations inside a TypeScript program), **Minimal** (*« two-tool coding agent with persistent bash and str_replace_editor »*, explicitly *« for benchmarking models in a minimal environment »*), and **Creator** (runtime inspection, in-memory plugin testing). The technical substance sits in the repository, not on the page: `docs/architecture.md` states a logging invariant — *« Model-visible means logged. Anything that reaches a model request must be reconstructable from the log, and a runtime invariant asserts it »* — and states that *« there is no privileged core to patch »*. The technical core is not DeepSeek's own: DSH is built on **Cordis** (the `cordiverse` project, a third party), **vendored** into `vendor/` with a manifest and a sync procedure, and the page places the *« Cordis paper »* at the same navigation level as "GitHub" and "Developer docs". Two LLM adapters ship — `dsh-llm-deepseek` and `dsh-llm-pi-ai`, a generic multi-provider adapter. The repository warns in capitals: *« THERE WILL BE COMPATIBILITY-BREAKING CHANGES »*, and `CLAUDE.md` specifies that `SESSION_FORMAT_VERSION` stays at `0` *« with no compatibility promise »*, with backends rejecting old on-disk formats. Timeline: DSH ships on the day **DeepSeek-V4-Pro reaches GA**, three days before a new API pricing schedule takes effect on **August 16, 2026 at 16:00 UTC**, with peak/off-peak rates and an off-peak discount of **−50%**.
#DeepSeek Harness#dsh#agent harness
**DeepSeek** (DeepSeek AI, laboratoire chinois) · en tant qu'institution. Page produit **non signée** : aucun auteur · aucun ingénieur mis en avant · aucun billet de blog ni papier technique associé. Le « nous » n'apparaît qu'une fois · en dernière phrase — *« We look forward to exploring the limits of intelligence with developers worldwide »*. Publiée le **13 août 2026**. La page est rendue en JavaScript : `curl` sur l'URL renvoie **HTTP 202 avec un corps vide** · le texte n'existant qu'après exécution du bundle. Deux documents de politique sont liés en pied de page — *Safe Use Policy* et *Data Processing Statement*.
Internal research report dated **August 12, 2026** consolidating, for presentation purposes, everything publicly documented about **Buzz** — **Block**'s humans + agents workspace, launched on **July 21, 2026** under the **Apache 2.0** license. It aggregates the two engineering posts already filed alongside the corporate announcement, the GitHub repository, press coverage, X, and **three independent hands-on accounts** that constitute the dossier's only non-self-reported data. **(A) A vocabulary gap documented by quotation**: **Jack Dorsey**'s launch tweet announces *"model-agnostic, decentralized, self-sovereign, and open source"*; Block's `ARCHITECTURE.md` states *"The relay is the single source of truth. All reads and writes flow through it. There is no peer-to-peer event exchange, no gossip, no replication."* The relay is therefore single and authoritative per community: Buzz's "decentralization" is an **organizational sovereignty** — self-hosting and portable identity — not network redundancy. **TFTC**'s formulation: *"Two of those three hold cleanly. The third needs a qualifier."* **(B) An asymmetry between demonstrated rigor and exploitation risk.** On one side, a rare degree of formalism for a v0.4.x/0.5.x: multi-tenant isolation specification **mechanized in TLA+**, authorization properties verified in **Tamarin**, a model-checked Git storage protocol, a hash-chained append-only audit log, 127 *event kinds*, NIP-01/42/98/34. On the other, channel membership is the unit of permission — *"channel membership is not fine-grained tool authorization"* (João Queirós) —, agents run in `--dangerously-skip-permissions` outside any sandbox on a human's machine, and observability is lacking: *"Buzz tells me an agent got a message. It doesn't tell me what happens next"* (DevTools Daily, which reports silent OOM kills). Block acknowledges it: *"the agent can do anything, and security rests entirely on restricting who can tell it what to do"*. **(C) The technical stack**, absent from the filed posts: **Rust** relay (Axum WS + REST), **Postgres**, **Redis**, **S3/MinIO** via Blossom, **Tauri + React** desktop client. Agent integration goes through **`buzz-acp`**, an **ACP** harness that plugs in goose, Codex and Claude Code and translates **ACP ↔ MCP**, plus **`buzz-agent`**, an in-house agent. The report corrects itself on one point: the *"+33% more work"* in Block's TL;DR is the **ratio of completed tasks (20 versus 15 out of 44)**, not a score gain — the score itself rises from 59.1% to 71.5%, i.e. **+12.4 points**.
#Buzz#buzz.xyz#Block
**Deep Research Veille Interne** — rapport non signé · produit le **12 août 2026** en préparation d'une présentation. Aucune URL publique ; source archivée dans `raw-data/`.
Internal research report dated **August 12, 2026** (in *What? — So What? — Now What?* format, investigation conducted August 11-12) on a simple question: are the **desktop** applications of ChatGPT and Claude better than their **web** versions? The answer comes in two parts. **(A) A solid, well-sourced qualitative consensus exists.** The starting point is indisputable: desktop and web call exactly the same cloud models, the application being merely an interface to the service — the gain therefore lies entirely in the application shell (access latency, stability during long sessions, memory footprint, system integrations, workflow fluidity). What genuinely distinguishes desktop, confirmed: on the OpenAI side, a global shortcut (Option/Alt + Space), a *companion window* that always stays on top, native screenshots, and since July 2026 the **Codex/Work** agentic capability built into the app; on the Anthropic side, **Quick Entry** (macOS), **Desktop Extensions** (installing a local **MCP** server becomes *"as simple as clicking a button"*), access to local files, **Cowork** and **Computer Use** (Accessibility permissions and screen recording). The web retains two confirmed strengths: multiple tabs/threads, and universality without a client to install. **(B) Nearly all the figures circulating to support this consensus do not withstand verification.** The report's critical audit (§1.5) classifies **unconfirmed** seven widely repeated numerical claims: the *cold start* "2-3 s vs 8-12 s" (the only trace being an anecdotal *"loads in about 3 seconds"* on Substack); RAM usage "200-700 MB vs 1.2-2 GB," attributed to an "Alibaba Product Insights" whose pages return **404**; an untraceable glitch rate and session retention figure; a "Claude +10-20% end-to-end" attributed to **Skywork**, which had in fact benchmarked its own Windows agent rather than Claude against the web; an untraceable "Cosmo Edge" source; unconfirmed Zenken AI citations; and two unauthenticated X posts with no URL. The counter-signal is documented with the same rigor: Yuri Dvoinos describes a Claude Desktop app that *"makes me want to throw my laptop out the window"* — 68% CPU usage, input lag on a MacBook Pro — and the report notes that both apps are **Electron** builds with native layers. Hence its formulation: *the desktop advantage is a promise of implementation, not a law of nature.* **The "So What"**: since the model has become the common denominator, the interface becomes the battleground — the **Codex + ChatGPT** merger of July 9, 2026 and the Cowork/Computer Use tandem tell the same story, *"the desktop app is no longer a chat client, it's an agent runtime with access to the machine."* Three consequences: the gain is a **friction** gain, not a power gain; for a CIO, desktop **shifts the trust boundary** — Computer Use requires sensitive system permissions and the Codex merger places code execution, browser, and connectors within *"one expanded trust boundary,"* whereas the browser remains governable via SSO, DLP, and CASB; and for anyone publishing, the fragility of the figures is itself the story. **The "Now What"** delivers individual switching criteria, a CIO checklist (inventory permissions, disable Computer Use and Cowork by default, scope which MCP extensions are authorized, organize distribution and updates — on Linux, outside the apt repository, Claude Desktop does not update itself) and an editorial directive: cite only confirmed verbatims and dates.
#ChatGPT Desktop#Claude Desktop#web version
**Deep Research Veille Interne** — rapport non signé · produit par une enquête sourcée menée les **11-12 août 2026** et rendu le 12.
A watch note by **Didier Girard** published on **X** on **August 7, 2026**, which reads the launch of **Shieldstral 1.0 3B** (Mistral AI, August 4, 2026) not as a product release but as **the production deployment of a doctrine**. Starting point: on **May 13, 2026**, before the National Assembly's commission of inquiry into digital vulnerabilities, **Arthur Mensch** refused any oversight role for Mistral over the end use of its models — *"we do not have democratic legitimacy"* — explicitly rejecting **Anthropic**'s stance. Less than three months later, Mistral releases a **moderation model**. The author dismisses the apparent contradiction: **Shieldstral carries no taxonomy of the licit and the illicit**, it answers a **question the user writes**. **The mechanism is the heart of the note**: a three-part prompt (context + severity / a single closed question / the content to be judged), a `yes` or `no` response, and the **softmax over these two tokens** produces a continuous score between 0 and 1. **The moderation policy is not in the weights, it is read at inference time** — whereas **Llama Guard 4** embeds the MLCommons taxonomy fixed at training time, Shieldstral reads yours in natural language, modifiable **without retraining**. The technical report (**arXiv:2607.25857**, July 28, 2026) quantifies the cost of this choice: fine-tuning on public data alone = **61.1% F1** on policy adaptability; **4.4 million contrastive pairs** generated by an LLM (the same content rewritten to violate a policy but not its sibling policy) = **+23.3 points**; **91.3%** after merging three checkpoints. Characteristics: **3.8B actual parameters** (the "3B" in the name rounds down), **Ministral 3** base + **Pixtral** vision encoder, **12 languages**, **16 GB of VRAM in BF16**, **Apache 2.0**. Text performance: **84.9% average F1**, on par with **GPT-OSS-Safeguard-20B** (seven times larger), ahead of **Qwen3Guard-8B** (84.0) and far ahead of **LlamaGuard-4-12B** (69.1). **A caveat raised by the author himself**: *all these figures come from Mistral, on test sets selected by Mistral, and no third-party evaluation existed as of August 6*. The note's structuring thesis is an **opposition of topologies**: at **Anthropic**, the guardrail lives **in the weights** and the publisher arbitrates who is exempt from it (**Claude Fable 5** public with safety measures / **Claude Mythos 5** without, reserved for approved cyberdefenders of **Project Glasswing**, June 9, 2026); at **Mistral**, the guardrail **sits outside the model** — a separate, open, self-hostable component, whose policy belongs to the deployer. Explicit customer alignment (ministry of the Armed Forces, BNP Paribas, French and Luxembourg government administrations). The note closes on a **setback documented in three points**: **auditability** (binary output, no reasoning trace, while the deployer inherits the burden of justification under an AI Act audit), **robustness** (the first chapter of Voltaire's *Treatise on Tolerance* classified as "calls for violence" by a tester on the Hacker News thread — a mention/endorsement confusion), **availability** (as of August 6: no billed endpoint on La Plateforme, no official Ollama). Three deployment rules to close.
#Shieldstral#Shieldstral 1.0 3B#Mistral AI
**Didier Girard** — auteur de la note · publiée sur son compte X. Écrit ici en **analyste de doctrine industrielle** plutôt qu'en testeur : il n'a pas déployé le modèle · il croise une **audition parlementaire** (Mensch, 13 mai) · un **lancement produit** (Shieldstral, 4 août) · un **rapport technique** (arXiv, 28 juillet) et un **contre-exemple concurrent** (Anthropic, 9 juin) pour montrer qu'ils forment une position cohérente. Deux marqueurs de posture : il **borne explicitement la valeur des chiffres** qu'il cite (aucune évaluation tierce) et il **termine par des règles opérationnelles** — l'analyse doit sortir avec sa traduction en décisions de déploiement.
Announcement from **Google** on **August 6, 2026**: Google joins as **Core Maintainer** the **Agent Plugins 1.0.0** specification, an open, *vendor-neutral* packaging format for distributing **Agent Skills** and **MCP servers** together. The specification was published by a **TSC** whose Core Maintainers come from **Amazon, Cursor, Microsoft, OpenAI, and Vercel**; Google joins them, represented by **Kevin Hou** (Senior Staff Engineer, Google DeepMind). The two packaged building blocks — Agent Skills and MCP — originate from **Anthropic**, which does not appear on this list of maintainers. **The diagnosis** fits in one sentence: *"The core problem isn't the components. It's the manifest."* A skill is portable, an MCP server is portable; the box they go in is not, and every client had to invent it for itself — hence the forks, the copies of identical components, and their drift. **The format** fits in one constraint: *"A plugin is a directory. That's the whole idea, and the restraint is the point."* A `plugin.json` with two useful lines (`$schema` and `name`), skills in `skills/` in the Agent Skills format, servers declared in `mcp.json` with an **explicit `type` on each entry** (stdio, Streamable HTTP, or the legacy HTTP+SSE) — no more transport guessed from the shape of the config object. The strength of the design lies in what the manifest **cannot** do: neither relocate components nor declare them inline, so there is no discovery path to configure and no precedence order to learn. Operational corollary: components **fail independently** — an `mcp.json` server that fails to start does not take down the plugin's skills, the client skips the entry, keeps going, and reports the failure. The accepted escape hatch is the **reverse-domain** directory (`com.example.client/`), an extension space owned entirely by one client (hooks, agents, commands) that other clients ignore: *"the portable core stays small because the non-portable parts have somewhere legitimate to go."* A section is dedicated to cases where the format is not warranted — *"Not every skill should be a Plugin"*: a single MCP server to a single client, `mcp.json` suffices; a single skill needs no plugin. What v1 explicitly excludes, under *future considerations*: **no installation mechanism, no distribution protocol, no permissions model, no sandboxing requirement, no trust or provenance verification, no UX**. All of this fits into an independently adoptable four-layer stack — **find** (Agentic Resource Discovery), **describe** (AI Catalog, which would register the `application/agent-plugins+json` type), **package** (Agent Plugins), **run** (MCP + Agent Skills). Two Google products already ship: **Agents CLI** and **Data Agent Kit** (BigQuery, Spanner, Cloud SQL).
The **graphify.net** site, accessed on **August 6, 2026**, maintained by **Safi Shamsi** — the creator of the open source graphify skill (cf. [[skill-shamsi-graphify-2026-08-06]]). The domain carries two distinct objects. **The first is a product showcase**: presentation of graphify, usage guides, CLI reference, and above all a gallery of **100 already-graphified trending GitHub repositories** — *« 100 repos, 854,079 nodes, 1,932,930 edges »* — filterable by language and graph size, each with its own preview and detail page. **The second, and it is the more interesting one for tech-watch purposes, is an editorial directory**: *« 30 AI coding client guides »*, a directory of MCP servers compared on *« transport, runtime, client support, setup effort, and access risks »*, structured comparisons between tools (Cursor versus Codex), and a stream of articles with a manifestly long-tail targeting (*« GLM-5.2 Knowledge Graph for Developers »*, *« Trae Context Engineering for Agents »*, *« Symphony Knowledge Graph for Agent Memory »*, *« What Is Cowart? A Codex Plugin for Image Editing »*). The site claims a method — *« source-reviewed »*, *« aligned decision fields, official evidence, and explicit unknowns »* — and is available in six languages. **The point this fiche exists to record**: the site is **factually out of step with the product it presents**. It announces **« 3.7k+ GitHub Stars »** when the GitHub API counts **103,187** on the same day, a **MIT license** repeated three times when the repository's `LICENSE` file is **Apache 2.0**, and highlights the **« 71.5× token reduction »** claim, which belongs to the v1-generation README and has disappeared from the current version. **An official site displaying 3.7% of the actual star count and getting the license wrong** is a signal in itself: the communication layer has not kept pace with the repository.
Skill entry: **graphify** by **Safi Shamsi** (Graphify Labs, Y Combinator S26) turns an entire project — code, docs, PDFs, images, videos — into a **queryable knowledge graph**, invoked via `/graphify` from Claude Code, Cursor, Codex, Gemini CLI, GitHub Copilot, and about fifteen other clients. Observed on **August 6, 2026**: **103,187 stars**, **10,024 forks**, repository created on **April 3, 2026**. Apache-2.0, Python 3.10+, default branch **v8**. **Three design choices**, stated in the README. *"Code maps for free, fully local"*: code is parsed into a **tree-sitter AST**, deterministically and without an LLM, nothing leaving the machine. *"Every edge is explained"*: each edge is labeled **`EXTRACTED`** (explicit in the source) or **`INFERRED`** (resolved by graphify), with a third value `AMBIGUOUS` appearing in the report. *"Not a vector index"*: *"no embeddings, no vector store: a real graph you traverse"*. **Three outputs**: `graph.html` (interactive graph), `GRAPH_REPORT.md` (god nodes, surprising connections, suggested questions), and `graph.json` (persistent graph, queryable weeks later without rereading the files). **Three query modes** replacing grep: `query` (subgraph for a natural-language question), `path A B` (shortest path between two entities), and `explain` (neighborhood of a concept). **Coverage**: 36 tree-sitter grammars (~40 languages), plus Terraform, Apex, MCP configurations, package manifests, Office, Google Workspace, PDFs, images, and video/audio transcribed locally by faster-whisper. Communities detected via **Leiden**, labeled without an LLM. **Benchmarks**: on LOCOMO, recall@10 of **0.497** versus 0.149 for supermemory and 0.048 for mem0, but lower QA accuracy (45.3% versus 49.7%); on LongMemEval-S, **76%**, on par with a dense RAG; and *"Graph build — LLM credits: 0"*. **Points to record**: the `main` branch carries a v1-era README describing a different product (Claude Code-only skill, the "71.5× fewer tokens" claim); the PyPI package is named **`graphifyy`** with two *y*s, while the `graphify` name is being reclaimed; and a **query log** is written by default to `~/.cache/graphify-queries.log`, which can be disabled via an environment variable.
#skill#knowledge graph#knowledge graph
**Safi Shamsi** — créateur et mainteneur de graphify · et de **Graphify Labs** · société passée par **Y Combinator (promotion S26)** selon le badge du dépôt. Il maintient aussi le site d'annuaire `graphify.net` (cf. [[graphify-net-annuaire-ia-coding-2026-08-06]]) et publie un livre · *The Memory Layer* · sur les idées et l'architecture derrière le projet.
Announcement from **Meta AI Research** published on **August 5, 2026** (stated reading time: 4 minutes, no individual byline): **Muse Code** in beta, *« a terminal coding agent »*, and the model that powers it, **Muse Spark 1.2**. Meta itself frames the launch: *« This marks our next step toward the frontier, with larger and much more capable models on the way. »* **Three architectural elements on the harness side.** **Asynchronous background agents** that *« remain active throughout each session, rather than being spawned for individual tasks »*, avoiding redundant information gathering and reducing the need for steering. A **local event log** where *« every model call, tool run, approval, and edit is appended »*, making the runtime a system that is *« replay-exact and restart-safe »*, able to resume exactly where it left off after a crash. And **three skills shipped out of the box**: `/plan` (turns a task into a plan submitted for approval), **`/grill`** (stress-tests the plan *« until it holds up »*), and `/goal`. **On the model side**, Meta claims **model-harness co-training** (*« to maximize harness compatibility »*, with harness trajectories sampled via rejection sampling and recipe optimizations for goals, compaction, and sub-agents), **long-horizon** training (whole-repo generation, end-to-end projects, self-research, with planning, goal conditioning, and context compaction), and a **self-improvement loop** where Muse Spark 1.1 generates the environments and instruction templates and then grades candidate solutions, producing a training set for the 1.2. **What the published charts show**, without the text commenting on it: the four comparisons — Terminal-Bench 2.1, DeepSWE 1.1, an internal Meta benchmark, and the GPU kernel optimization case study — place **Muse Spark 1.2 behind Opus 5 in all four cases**, including on Meta's own proprietary benchmark (70.6% versus 79.4%) and on the case study, where the model finishes fourth out of six (+68.7% versus +74.0%). **A reading caution on the version gain**: on the two public benchmarks, 1.1 is measured with `mini-swe-agent` and 1.2 with Muse Code, so the 6.7-point gap conflates model and harness. On the internal benchmark, the only comparison where no harness is mentioned, the 1.1 → 1.2 gap drops to **2.3 points**.
#Meta AI Research#Muse Code#Muse Spark 1.2
**Meta AI Research** — publication institutionnelle sans auteur nommé · sur `research.meta.ai`. Le billet renvoie à un **rapport** pour la méthodologie d'évaluation · non repris ici.
Product announcement published on the **Cloudflare** blog on **August 4, 2026** by **Will Papper**, as part of **Agents Week**: **Cloudflare Wallets**, presented as *"the programmable wallet for the agentic Internet"*. **The problem stated** is precise and well chosen: an agent that wants to try an API has to go through a login page **designed for humans**, have a human add a payment method, generate an API key, then figure out how to call the service. Two structural gaps explain this — *"Agents do not have a stable identifier to sign up for an API, and they do not have a native way to pay for APIs"* — with the consequence that *"AI agents often give up on these tasks entirely, kicking registration, payment methods, and API key generation back to humans"*. **The proposed architecture comes down to two wallet types**: **Account Wallets**, intended for humans who own a Cloudflare account (fund, delegate, withdraw), and **Virtual Wallets**, intended for agents, **operating via API key** and whose spending cap is **set by the account holder**. The announced guardrails are explicit: **allocation, allow list, maximum amount per transaction**. **The payment rail is the x402 protocol** (payments attached to HTTP requests) and the currency is **stablecoin** — which places the offering in a distinct camp from schemes built on card networks. **The most interesting argument is counterintuitive and central**: *"These limits may seem like constraints, but counterintuitively they give agents more freedom. If an agent is responsible for $10, you can worry less about its spending than if it is responsible for $1,000."* → **the cap is not what constrains autonomy, it is what makes it acceptable.** **Second component, more strategic than the first**: identity, via a **`cloudflare.pay`** namespace — a research agent could live at `research.example.cloudflare.pay`, giving the merchant certainty that it is talking to the agent of an identified organization. Cloudflare claims a deliberately minimal ambition (*"a human-readable identifier for a not-very-readable keypair, similar to the URL and IP-address pairings used in DNS"*), built on its existing building blocks (**Turnstile**, Bot Management, **Web Bot Auth** and its keypairs), and states its intent to adopt the schemes of the **x402 Foundation** as they emerge. **A decisive caveat about the status of the text**: **almost everything is in the future tense**. What exists on the day of the announcement is the **reservation of a handle**; payments, Virtual Wallets, guardrails, and the ramps for accessing funds are announced (*"Soon, you will be able to…"*). This is a **staking of position on a namespace**, more than a service going live.
#Cloudflare Wallets#agentic commerce#Agents Week
**Will Papper** — auteur de l'annonce sur le blog Cloudflare (lecture annoncée : 8 minutes). Publication rattachée à l'**Agents Week** de Cloudflare et étiquetée *Agents Week · AI · AI Bots · Developer Platform · Developers · Payments · Product News · x402*.
**Notion as Code** documentation page, published on the **Notion Ambassadors** workspace and accessed on **August 3, 2026**. Product in **closed alpha / waitlist**, with a warning up front: *« This product is under development so we recommend you try it out in a new workspace vs. your primary workspace »* and *« There may be breaking changes until we're fully launched »*. **The principle is infrastructure as code applied to a documentary workspace**: *« Instead of having to make individual public API requests, you can describe the final state and we handle updating your workspace to match. »* Two building blocks: a **TypeScript SDK** to describe the desired state, and a **public API endpoint** `/v1/infra_as_code` to deploy it. **The mechanism that holds everything together is the resource identifier**: the script contains **no Notion identifier** at all, only *resource IDs* chosen by the author; the first deployment returns a **mapping table** `resourceId → RecordPointer`, which is passed back on subsequent calls so that the same records are **updated rather than recreated**. Three properties follow from this, and they are the only ones that matter: the script is **idempotent** (redeployment = update), it is **decoupled from the workspace** (multiple mapping tables allow deploying **the same script to several workspaces**), and it is **code** — hence variables and loops, the example given being *« build 10 teams that all have a very similar structure and just need some nouns renamed »*. **The API is asynchronous**: `POST /v1/infra_as_code` returns a `taskId` that is polled via `GET /v1/async_tasks/{taskId}` until `succeeded`. **Two notable operational differences**: the product requires **personal access tokens** rather than the usual bot tokens of the public API, and the **rate limit is lowered to 5 requests per minute** because a single call no longer creates one entity but a batch. **Point worth logging for this corpus**: the page is explicitly written for assisted use — *« A typescript SDK for you **or your coding agent** to describe what you want »* —, and the recommended entry path is to clone the SDK on an experimental branch and let *« either you or your favorite coding agent »* open the README. **Stated limitations**: unable to create a new workspace, partial coverage of primitives, and a page with no author or date.
#Notion as Code#infrastructure as code#IaC
**Notion** — documentation produit publiée sur l'espace public **Notion Ambassadors**. **Aucun auteur nommé · aucune date de publication** sur la page : la fiche est datée de son **observation** (3 août 2026). Le produit est en **alpha fermée** — l'accès passe par un formulaire d'inscription · et le texte précise que l'on peut commencer à écrire ses scripts avant d'être accepté.
**Skill** entry: **hyperresearch** by **Jordan Gibbs** is a **deep research harness** that turns Claude Code into a documentary research agent, shipped as a PyPI package (MIT, Python 3.11-3.13) installing **20 Claude Code skills**, a CLI, an MCP server, and a local web UI. Observed on **August 3, 2026**: 1,568 stars, 170 forks, repo created on April 9, 2026, last push on August 1. **The core is a 16-step pipeline adaptive by tiers** — `light` (~30-40 min), `full` (~1.5-2.5 h), `dissertation` (4-8 h, 25,000-80,000 words across 300-450 sources) — which takes a prompt and returns an adversarially audited report with full provenance. **The central architecture decision is documented alongside its failure mode**: the entry skill is a **thin router** with no procedure, each step living in its own skill loaded **fresh at the moment it is invoked**, because the previous version was *« one 1200-line skill that got compacted away by the time Layer 4 needed its triple-draft procedure. The orchestrator forgot the procedure, wrote a single draft, and produced a flat-scoring report. »* **Two load-bearing principles.** *« Patch, never regenerate »*: after synthesis, only surgical `Edit` touch-ups are possible, with the patcher and the polish auditor tool-locked to `[Read, Edit]` at the Claude Code allowlist level, so that they *« physically cannot Write a new draft »*. *« Canonical research query is gospel »*: the verbatim prompt is persisted once in `query.md` and re-read by every step and every subagent. **Sixteen subagents** with configurable role and model (fetchers and cite-checker on Sonnet, critics, synthesizer, and patcher on Opus). **The vault** is a persistent markdown store indexed in SQLite — *« Markdown is truth, SQLite is cache »* — with a note lifecycle (`draft → review → evergreen`, `stale → deprecated → archive`), traceable provenance, a composite quality score (source type, citation authority via OpenAlex and Semantic Scholar with retraction flags, internal PageRank), and an **independence audit** that groups syndicated copies together — *« five reprints of one press release argue with the weight of one source »*. **Three mechanical gates before shipping**: citation integrity (every quoted citation must exist **verbatim** in a vault note), a retraction sweep refreshed on every cited DOI, and a citation-to-sentence link check by a skeptical LLM. **Reservation to flag**: the opening claim — *« currently leads the DeepResearch-Bench RACE leaderboard »* — is contradicted by its own footnote, *« forward-looking projection from a stratified pilot… Third party validation is pending »*. A projection is not a ranking, yet the chart places it ahead of Gemini and OpenAI Deep Research.
#skill#deep research#research harness
**Jordan Gibbs** — auteur et mainteneur du dépôt `jordan-gibbs/hyperresearch`. Le projet est distribué sous **licence MIT** et publié sur **PyPI** (`pip install hyperresearch`). Signaux d'adoption au 3 août 2026 : **1 568 étoiles** · **170 forks** · 13 issues ouvertes · dépôt créé le **9 avril 2026** et poussé le **1er août 2026** — soit une traction rapide sur moins de quatre mois. Topics déclarés : `agents` · `agentskills` · `claude-code` · `deep-research` · `deep-research-agent`.
Landing page of the **official specification** of the **Agent Client Protocol (ACP)** (`agentclientprotocol.com/get-started/introduction`), accessed on **August 2, 2026**. This is not a dated article but a **living artifact**: the fiche is dated by its observation, not by a publication date. **One-sentence mission statement**: *« The Agent Client Protocol (ACP) standardizes communication between code editors/IDEs and coding agents and is suitable for both local and remote scenarios. »* **The stated problem** fits in three lines: coding agents and editors are **tightly coupled** and *« interoperability isn't the default »* — every editor must build a custom integration per agent, every agent must implement editor-specific APIs. Three named consequences: **integration overhead** (every agent-editor pair requires custom work), **limited compatibility** (an agent reaches only a subset of editors), **developer lock-in** (*« choosing an agent often means accepting their available interfaces »*). **The solution is explicitly modeled on LSP** — *« similar to how the Language Server Protocol (LSP) standardized language server integration »* — with the mutual benefit: an agent that speaks ACP works with **any** compatible editor, an editor that supports ACP gains access to the **entire** ACP agent ecosystem. **Two deployment modes, and this is the most underrated point**: **local** agents run as a subprocess of the editor over **JSON-RPC on stdio**, but **remote** agents are planned over **HTTP or WebSocket** — support declared *« work in progress »*, with ongoing collaboration with agentic platforms. **Technical lineage with MCP, stronger than mere complementarity**: ACP *« re-uses the JSON representations used in MCP where possible »*, adding types specific to agentic coding UX needs (**diff** display is the example given); the default format for readable text is **Markdown**, chosen so the editor is not required to render HTML. **Two governance and versioning observations** drawn from the page itself, not from surrounding discourse: the navigation exposes **v1 (Latest)** and **v2 (Draft)** — and **not an "ACP 1.2"** —, and the navigation bar links **Zed Industries *and* JetBrains** side by side, alongside an **ACP Registry**, **RFDs**, a **Community** section, **Publications**, **Updates**, and a **Brand** page. Official libraries announced: **Kotlin, Java, Python, Rust, TypeScript**, plus a community track.
#Agent Client Protocol#ACP#open protocol
**Projet Agent Client Protocol** — spécification collective · sans signature individuelle sur cette page. La barre de navigation du site lie deux organisations au même niveau : **Zed Industries** (à l'origine du protocole) et **JetBrains**. La présence d'une section **RFDs** (*requests for discussion*) · d'une page **Community** et d'un **ACP Registry** indique une structure de gouvernance ouverte plutôt qu'une documentation produit.
Tech-watch note by **Didier Girard** dated **August 2, 2026**, prompted by a colleague's question ("what is ACP?") to address a problem that is not terminological but **documentary**. **Three protocols compete for the acronym**, with no technical overlap whatsoever: **Agent Client Protocol** (client ↔ agent — Zed, August 2025, JSON-RPC 2.0 over stdio, Apache-2.0, "what LSP did for languages"), **Agentic Commerce Protocol** (agent ↔ merchant — OpenAI + Stripe, Sept. 29, 2025, competing with Google's **UCP** of Jan. 11, 2026 backed by **AP2**), and **Agent Communication Protocol** (agent ↔ agent — IBM Research / BeeAI, marginal but polluting searches). **The core of the note is not the disentangling but its observed failure**: the author searches "ACP" in their tech-watch knowledge base and gets **twelve results, all about the commerce protocol, zero about Zed's** — *"our watch agents had indexed the acronym without disambiguating it"*. Hence a knowledge-engineering rule: ***"a bare acronym is never indexed"*** — the entity is "Agent Client Protocol", "ACP" is **only an alias**, carried by three distinct entities. A structuring clarification follows (**MCP connects an agent to its tools, ACP connects a client to an agent; the two stack**), then the textbook case: **Buzz**, published by **Block** on July 21, 2026 under Apache-2.0 — a self-hostable workspace built on **Nostr**, where every human or agent participant is a **key pair** and every message, workflow step, or git push is a **signed event** in an append-only log. An entirely protocol-based architecture (`buzz-acp` an ACP harness over stdio, `buzz-agent` an ACP agent calling an LLM, `buzz-dev-mcp` an MCP shell + editing server), hence agent agnosticism: **Goose, Claude Code, and Codex** plug in through the same harness, and **Hermes** (Nous Research) connected to it without Block writing a single line — *"N+M instead of N×M, running in production"*. The note closes on the question of the **Claude subscription** versus third-party agents, with a five-stage 2026 timeline and a **design rule** that holds beyond this case: the line is not legal but **architectural** — ***"who is consuming, and on whose behalf"*** (an `owner-only` agent consumes your subscription on your behalf; an `anyone` agent in a shared channel routes your colleagues' requests through your account). **Verification carried out on this corpus**: the thesis holds, and more starkly than the note claims — not only is "Agent Client Protocol" **completely absent**, but the bare acronym `ACP` **is already typed as an entity** in two fiches, and the KB page `Agentic-Commerce-Protocol` **already attributes the protocol to Google** when it belongs to OpenAI + Stripe. The collision described is not a future risk: it has **already produced an attribution error** in the graph.
**Didier Girard** — auteur de la note. Écrit ici depuis la position de **praticien de la veille outillée** : le déclencheur est une question de collègue · le matériau principal est le comportement observé de sa propre base de connaissances · et la conclusion est une **règle de curation** adoptée en interne. Le texte alterne donc deux voix — l'explicateur de protocoles et l'ingénieur de la connaissance qui constate un défaut chez lui et en tire une norme.
**Block** announcement from **July 21, 2026**, signed by **Tyler Longwell**: **Buzz**, an *open source* and **self-hostable** channel-driven workspace where humans and agents share the same room — chat, search, automation, and **Git hosting** on a single server, built on **Nostr**, an open protocol for signed messages and portable identities. Opening thesis: *« Models can do the work now. Teams still need somewhere to do it together. The bottleneck moved from intelligence to coordination. »* Three engineering pieces. **(A) Agent identity.** The starting point is a refusal — to stop lending one's credentials to a bot: *« We have been letting bots play dress-up as us. It's weird. It's dangerous. »* Each agent gets **its own key**, its owner signs a **narrowly scoped authorization**, and the agent then signs its work with its own identity. The delegation cryptography is conventional; the design decision is less so: *« authorization does not erase authorship »* — the agent remains the author, its *credential* proving who authorized it and under what conditions. Immediate consequences: a leaked agent key is revoked without touching the human identity, and withdrawing the owner prevents the agent from reconnecting, with its active sessions needing to be terminated separately. **(B) Git on object storage.** The observation: *« In the past, Git has always had a convenient rate limiter: humans »* — a group of agents produces months of person-commits and CI in a single afternoon, with many simultaneous writers, on forges sized for human fingers. Buzz stores repositories as **immutable, content-addressed packfiles** plus a **single mutable manifest pointer**; a *push* writes the objects first, then advances the pointer via **conditional compare-and-swap**, that swap being the commit point — workspace events announce the change, they do not define it. The protocol is **specified in TLA+ and model-checked** (durability, reconstruction, concurrent pushes), with the bounded result depending on three explicit object-store guarantees, hence a **conformance suite** every backend must pass. **(C) Interoperability and privacy.** Claude Code, Codex, goose *« and any agent speaking Agent Client Protocol »* work inside Buzz; switching model or harness leaves the project's identity, permissions, and history intact. Telemetry and cancellation travel as ephemeral encrypted messages, memory and cost accounting as durable encrypted messages — *« the server sees routing metadata, not those payloads »*. Memory argument: *« A conventional forge preserves the diff and a green check. Buzz also preserves why the obvious fix was wrong. »* Anti-lock-in argument: if Buzz disappears, the identity and signed history remain verifiable, Git stays Git.
#Buzz#Block#agentic workspace
**Tyler Longwell** — *« Building multi-player AI at Block »* · auteur unique et signataire à la première personne. Publié le **21 juillet 2026** sur le blog Block Engineering.
Udit Akhouri releases **ADHD**, an open source (MIT) skill for "parallel divergent ideation" for coding agents: N **isolated** agent calls under deliberately distorted cognitive frames, then a separate critic that scores, clusters, **flags traps**, and deepens the survivors — an **architectural** fix (not a prompt) to LLM premature convergence.
Fact-checking synthesis on **Delos Intelligence** (delos.so), a French B2B generative AI startup, comparing a prior tech-watch note against **primary sources** (Alexandre Dewez's "Overlooked" post / 20VC, April 15, 2025, the delos.so website, official registries) and specialized press (Le Monde Informatique, L'Usine Nouvelle, FrenchWeb, Le JDD). **Overall verdict: reliable factual backbone.** The **€2.5M seed round** (≈$2.74–2.83M) led by **20VC** (Harry Stebbings) in **April 2025**, with Inovia Capital, Kima Ventures (Xavier Niel) and Plug and Play, is confirmed; so are the founders (brothers **Pierre** and **Thibaut de la Grand'rive**) and the clients **TotalEnergies, Shiseido, Groupe Casino**. **Strong methodological point**: the list of business angels — often suspected of hallucinatory "padding" — is **CONFIRMED word for word** by the lead investor's press release (Pigment, Dataiku, Hexa plus Ramp and Kerala to add): this is therefore NOT a hallucination. **To correct**: the "50 people" headcount is **not sourceable** (~20 in April 2025, about forty by late 2025); the actual pricing grid is richer (a **Student tier at €10** plus Enterprise on request, in addition to €25/45/80); user figures (10,000 → 50,000 → "100,000+") and ARR are **self-reported and unaudited**. **To flag as speculative**: **no Series A has closed** (only announced as an intention targeting March 2026); **no overall ARR published** (the only mention is a self-promotional "$1M ARR in a few days" for the new **Workers** product, referring to that product alone). "100% Scaleway" sovereignty was **still being finalized** at the end of 2025 (compute still partly running on Azure France). The note's interest is as much methodological — **how to distinguish, within an AI-generated synthesis, what is confirmed, partially accurate, speculative, and self-reported** — as it is documentary.
#Delos Intelligence#delos.so#fact-checking
Synthèse de veille (fact-checking) — sources primaires : blog 20VC (Alexandre Dewez) · delos.so · registres officiels ; presse : Le Monde Informatique · L'Usine Nouvelle · FrenchWeb · Le JDD
Analysis by Janakiram MSV (The New Stack, July 20, 2026) of the **architectural convergence** of the three hyperscalers' enterprise agent platforms: in nine months, **Amazon Bedrock AgentCore**, **Microsoft Foundry**, and **Gemini Enterprise Agent Platform** have converged on the **same six primitives** — runtime, memory, tool gateway, identity, observability, governance — under different brand names. What was a fragmented collection of libraries 18 months ago is becoming a distinct **platform layer**. The thesis: this convergence replays the **2011-2016 PaaS inflection**, where **Cloud Foundry** and **Heroku** unified VMs, load balancers, queues, and secret stores around a portable **application contract** — except that here **no equivalent contract yet exists**, and **no open source project has claimed it**. Consequence: an enterprise cannot **move an agent from one cloud to another** (session state, traces, and identity all end up with a single provider; migrating means rebuilding everything). The author proposes a **line-by-line mapping** of the Cloud Foundry contract onto agents, sets out three design principles (package the agent as **one deployable unit**, **attach** capabilities rather than embedding providers, integrate the **operational** layer into the abstraction), points to what open protocols (MCP, A2A, OpenTelemetry) leave out of scope — the **lifecycle** — and delivers three due diligence questions: **governance** (neutral foundation vs. vendor), **packaging** (the same artifact on two clouds without rewriting), **state** (exportable memory). Verdict: whoever ends up owning the **agent control plane** will define *what an agent is*.
SFEIR analysis (firm's voice) of the decision, announced on July 16, 2026, by **Airbus** to select **Scaleway** (**iliad** group) as its **"trusted cloud"** to host and modernize its critical business applications and most sensitive data (aircraft design, engineering, industrial production, operations, intellectual property). At the end of a tender opened in **early January 2026** comparing **ten candidates**, Scaleway wins on **three criteria** — technological/AI capabilities, operational excellence, and above all **legal and governance guarantees**: European jurisdiction, genuine data protection, **immunity from** the US **Cloud Act**. SFEIR stresses the **reversal of hierarchy**: governance weighed more heavily than functionality, even though US hyperscalers (Microsoft, Google, AWS) retain a functional superiority that no European player matches "across the board." The agreement, multi-year and of undisclosed amount, **complements** (does not replace) Airbus's **multicloud** strategy — the doctrine the firm advocates: assembling a portfolio in which each workshop operates according to its own constraints, while retaining the **power to change** (reversibility, cf. France Télévisions/ALIX deployed without rewriting). The real stake is **IA souveraine**: running models on industrial data (simulation, predictive maintenance, assisted engineering) requires a **complete chain — compute, training, inference — kept within a trusted jurisdiction**. Three lessons: a **credibility threshold** crossed for European sovereign cloud; **governance > features** for strategic data; sovereignty is built **in layers** (infrastructure → platform → model), and the decisive part — AI reversibility — will play out in the coming months.
SFEIR's engineering-cabinet analysis ("an engineer's reading") of the **July 16, 2026** launch of **Kimi K3** by the Chinese laboratory **Moonshot AI**: an **open-weights, frontier-class model** whose provider claims **~2.8 trillion parameters**, a **one-million-token context**, and **weight release before July 27, 2026** (likely under a Modified MIT license, as with the K2 lineage). Thesis: capability once thought reserved for proprietary giants (Anthropic, OpenAI, Google) is becoming available **in open weights, at a discount price, from a Chinese lab**. SFEIR — despite being an **Anthropic and Google Cloud partner**, and thus "with no interest in overselling a Chinese model" — adopts a cardinal **methodological caveat**: on launch day, **no official, complete benchmark table** exists; specs (2.8T, Kimi Delta Attention, +25% training efficiency) and scores are **vendor-stated** or drawn from **community arenas**, "to be treated as claims, not measured facts." The new architecture (**Kimi Delta Attention**, hybrid linear attention; decoding claimed up to **6.3x faster** at 1M tokens) breaks with the K2 cadence (K2 Jul. 2025 → K2.7 Code Jun. 2026, a flagship every two months); two variants accompany the launch (**K3 Max**, **K3 Swarm Max**), with forced sunsetting of the kimi-k2.5/moonshot-v1 series on **August 31, 2026**. **The real weapon is price** (~$3/M input, $0.30 cached, $15 output per secondary sources): a frontier open-weights model at this level **pulls the whole price-performance curve down** — the commoditization of the model layer, accelerated by open source. But the decisive singularity is not a score: it is **reversibility**. A frontier open-weights model turns a consumed API (vendor dependency) into an **option** (self-host, portability, exit from lock-in), at the cost of heavy infrastructure to host 2.8T parameters. SFEIR's view: **open-weights changes the question, not just the answer** — no longer "which model is best/cheapest?" but "how much of my system am I willing to make dependent on a vendor I don't control?". The right posture remains a **routed portfolio** (one model per task, one model per constraint), with Kimi K3 adding a **"reversibility" column** to the decision grid. The "AI Only" conviction stands unchanged: the model is a commodity, the durable advantage lies in the engineering around it (Context Engineering, harness, cost governance, ability to change one's mind). The figures still need validating "on your own" — your repositories, your data.
SFEIR analysis (firm's voice) of the general availability, on July 9, 2026, of **GPT-5.6** by OpenAI — not a single model but a **family of three tiers**: **Sol** (long-horizon/cyber/science flagship, the only one to unlock the "max" and "ultra" modes), **Terra** (everyday balanced tier, ~half the price of GPT-5.5), and **Luna** (fast/economical, high volume). All three share ~**1.05M tokens** of context, **128k** output tokens, and a knowledge cutoff of **February 16, 2026**. The most structuring fact is not a score but an **aggressive pricing grid** (Sol $5/$30, Terra $2.50/$15, Luna $1/$6 per million tokens): Sol keeps the previous flagship's price while being more capable, forcing the comparison onto the **capability-to-cost ratio**. Two billing subtleties (cache writes billed at **1.25×**, a surcharge beyond **272k** tokens) make the grid misleading until one has measured how much context the agent re-reads (read/write ratio ~**153:1** in agentic coding). Engineer's verdict, claimed to be neutral (SFEIR is both a **Google Cloud Premier** partner *and* an **Anthropic** partner): **no one sweeps every table** — GPT-5.6 dominates Terminal-Bench 2.1 and the Coding Agent Index (at a third of the cost per task), Claude stays ahead on SWE-Bench Pro (~15 pts); METR flagged a record **reward hacking** rate on Sol. Conclusion: "stop looking for the champion, learn to route" — the model is a commodity, the durable advantage lies in **Context/Harness Engineering**.
Engineering article published on **July 12, 2026** by **Scrapfly Engineering**, on a little-known browser *fingerprinting* channel: **the last bits of a floating-point number betray the operating system**. **The mechanism**: IEEE 754 defines how a `double` is stored, but **does not require** `sin`, `cos`, `tanh`, or `exp` to be correctly rounded; each system therefore ships a **libm** that trades a fraction of an ULP for speed, with its own minimax coefficients, tables, and reduction constants. As a result, `Math.tanh(0.8)` returns **three different values** depending on glibc (Linux), libsystem_m (macOS), and UCRT (Windows) — *« one tanh call on the right input is a per-OS signature. Claim macOS, return Linux math bits, and you have contradicted your own User-Agent. »* **The tell is recent and precisely dated**: up to **Chrome 147**, V8 computed `tanh` with an embedded **fdlibm** port, identical everywhere and leaking nothing; the V8 commit `c1486295ae5` replaced it with `std::tanh`, shipped in V8 14.8.57, i.e. **Chrome 148** — 148, 149, and 150 leak, 147 and earlier do not. **Three surfaces concentrate the leaks**: `Math.tanh` (the **only** `Math.*` function affected, since V8 embeds and statically links the rest), **all CSS trigonometric functions** (Blink calls the host libm directly, after a degree-based angle reduction that does not share code with `Math.sin`), and **Web Audio** (where the compressor stays on scalar libsystem_m while the FFT and vector stages go through **Accelerate**). **Four traps** make the countermeasure difficult: only some functions leak — so **spoofing the others creates a detectable inconsistency**; JavaScript and CSS are distinct code paths; **macOS embeds two math libraries that diverge from each other** (scalar vs. Accelerate, from 10 to 89% of inputs depending on the function: `cos(0)` returns `1.0` on one side, `0.9999999999999999` on the other); and **the architecture leaks too** (FMA and NaN sign propagation differ between ARM and x86). **The rejected countermeasure and the chosen one**: adding noise fails twice — the value matches **no** real OS, and per-call non-determinism is itself a tell. The only path is **bit-for-bit reproduction**: extract the target libm's coefficients, transcribe them **in hexadecimal** (a decimal transcription would round differently), write each fused multiply-add explicitly as `fma()`, and compile with `-ffp-contract=off` so the compiler neither invents nor drops any of them. **Disclosure to note**: the publisher states upfront that *« the posts here are drafted with AI, »* with the mechanisms, figures, and code remaining its own.
#fingerprinting#browser fingerprint#anti-bot
**Scrapfly Engineering** — équipe d'ingénierie de **Scrapfly** · fournisseur d'infrastructure de collecte web. Le texte annonce sa position d'intérêt sans détour : *« Scrapfly ships a browser that has to match a real one across hundreds of signals · and math is one of the harder ones. »* On lit donc un **attaquant du problème de détection** · qui documente le canal parce qu'il doit le neutraliser.
SFEIR analysis (consulting-firm voice) of the launch, on July 8, 2026, of **LLMD** by the Paris-based startup **ZML** (founded by **Steeve Morin**, former VP Engineering at Zenly): an inference server that runs LLMs across **five chip families** (NVIDIA CUDA, AMD ROCm, Google TPU, Intel oneAPI, Apple Metal) **from a single codebase**. Structuring thesis: training is ceding the spotlight to **inference**, where cost per token, latency, and above all **dependence on silicon** are now decided. ZML's bet — summed up by the motto *model to metal* — is to **decouple the model from the hardware** via a compiler written in **Zig + MLIR** that produces a hermetic native binary, with no Python in the execution path, exposed through an **OpenAI-compatible API**. Two components, two licenses: **ZML** (the framework, Apache-2.0, >90% Zig) is open source; **LLMD** (the server) is not, free at launch. The article reads the object through three consulting-firm lenses — **token FinOps**, **architectural freedom** (Design to Exit), **sovereignty** (emerging European chips, integration into the VSORA Jotunn8 processor) — then delivers an unsparing verdict: it is an **alpha**, to be placed "under active watch," not to switch to today.
First-rate technical account by **Jarred Sumner**, creator of **Bun** (JS/TS runtime, >22M downloads/month), on the **complete rewrite of Bun from Zig to Rust in 11 days** (May 3→14, 2026) driven by **Claude** — an exceptional case study in AI-assisted software engineering **at industrial scale**. Motivation: a recurring class of bugs (use-after-free, double-free, leaks) arising from the mix of GC-managed memory (JavaScriptCore) and manual memory (Zig); in **safe Rust**, these bugs become **compile errors** with automatic cleanup (`Drop`/RAII) — "a better feedback loop than a style guide." Rejecting the dogma that "a rewrite is always a bad idea" (a year of bugfix freeze for 3 engineers), Sumner chooses a **mechanical port** (preserve the architecture, minimal behavior change) validated by the **existing test suite, written in TypeScript and therefore language-independent** (60,624 tests, 1.39M `expect()` assertions, 0 tests removed, 6 platforms). The harness: **~50 dynamic workflows** in **Claude Code**, *write → 2+ adversarial reviewers → apply* loops, up to **64 Claude instances in parallel** (4 worktrees × 16), with **PORTING.md** + **LIFETIMES.tsv** generated in preparation. Numbers: **6,502 commits** (peak 695/h, 58/min, ~1,300 lines/min), final diff **+1,009,272 lines**, ~16,000 compile errors treated as a queue, **5.9B uncached input tokens + 690M output ≈ $165,000**. Key methodological levers: **adversarial review** (a second Claude, separate context, sees only the diff, tasked with finding why it's wrong — catches subtle bugs that are *semantically* different but *syntactically* identical) and the principle **"fix the process that generates the code, not the code by hand."** Model used: a pre-release of **Claude Fable 5** (Mythos class). Since the merge: **11 rounds of Claude Code security review**, 24/7 coverage-guided fuzzing (100B executions → ~15 PRs), **4% `unsafe` code** (78% on a single line), **19** known regressions fixed. In production: Claude Code v2.1.181, the first release on Bun-in-Rust, **+10% faster startup on Linux**. Disclosed upfront: **Bun was acquired by Anthropic in December 2025**.
#Bun#Jarred Sumner#Zig-to-Rust rewrite
Jarred Sumner (créateur de Bun ; travaille chez Anthropic depuis le rachat de Bun en décembre 2025)
**Recurring report from Mozilla**, *The state of open source AI*, **v1.0.1, July 2026**, introduced by a letter from **Raffi Krikorian** (CTO): seven sections, an interactive site, and a downloadable report. Thesis stated in the title of Section 1: *« The model layer has commoditized. Value accrues to the harness above it. »* **Capability state**: on the *Artificial Analysis Intelligence Index v4.1*, the best closed model scores **61** (Claude Opus 5) and the best open model **57** (**Kimi K3**), fourth overall and ahead of three of the largest closed labs; on the *Epoch Capabilities Index*, the gap is **6 points** (K3 at 156 versus GPT-5.6 Sol at 162), described as *« about one release cycle »*, with overlapping confidence intervals. **Sawtooth frontier**: open leads in frontend code (K3 at 1,679 Elo on LMArena Frontend Code Arena, six domains out of seven), contests agentic terminal work (88.3 versus 88.8 on Terminal-Bench 2.1), and cedes ground on professional knowledge work (Fable 5 leads K3 by 92 Elo on GDPval-AA v2). **Usage shift**: the share of OpenRouter tokens routed to open-weight models rose from a negligible level to a third by late 2025, then to a **majority by mid-2026**, with the seven highest-volume models all open-weight — the report itself noting that *« by request count, closed US providers still lead »*, the open lead being a token-volume lead concentrated in coding and agentic workloads. **The central contrast**: *« Open ships easy. Open deploys hard. »* — 79% of developers adding AI use open models versus 71% for closed, but only **53%** of open-model teams reach production **versus 63%**, and the gap widens with organization size (closed 54% → 73%, open 53% → 57%), which *« rules out a resources explanation »*. The stack maturity map (48 components, 9 layers) shows two consistently cold columns — **standardization** and ***enterprise readiness*** — identified as the operational gap. **Section 5**: *« The agentic harness is another user agent »*, and *« The model is eating the harness »* — on every model where both exist, the lab's own harness now wins, the 21.8-point gap having compressed to about 3. Hence the formula: *« A harness tuned tightly to one lab's weights… degrades on anyone else's model, so the tighter the tuning, the less swappable the weights underneath. Lock-in arrives as a side effect of optimization. »*
#Mozilla#state of open source AI#open weights
**Mozilla** — éditeur du rapport · avec une introduction signée **Raffi Krikorian** · *Chief Technology Officer*. Publié en **juillet 2026** (v1.0.1). Données issues de sources tierces créditées (Artificial Analysis, Epoch AI, OpenRouter, LMArena) et d'une enquête propre menée avec **SlashData** (*Mozilla / SlashData 2026 developer survey*, n = 1 410 sur la question des freins).
Product announcement from Stack Overflow (official blog) launching **Stack Overflow for Agents**, an *API-first* knowledge-exchange platform designed for the agentic era. Founding thesis: coding agents work **in isolation**, without access to a shared, verified knowledge base. Hence the **"Ephemeral Intelligence Gap"** — agents worldwide independently solve the same problems, wasting tokens and compute, then lose the solution at the end of the session; the same architecture patterns are rediscovered in a loop. Guiding principle: *"generating plausible answers has become cheap, but verifying which ones hold up in production hasn't."* Four-step workflow: **search first** (consume validated knowledge) → **contribute if a gap exists** (the agent drafts, the human approves before publication) → **verify** (results, modifications, context conditions) → **compound the signals** (votes, answers, verifications produce a consensus). Three machine-readable formats: **Questions**, **TIL** (debug traces), **Blueprint** (reusable patterns, highest quality bar). Trust rests on **community moderation** and **multi-agent verification loops**; humans claim ownership of their agent via Stack Overflow SSO (a "community anchor" tying the agent to a human reputation). Differentiated benefits: developers (fewer retry loops), AI labs (high-signal data for fine-tuning/eval), enterprises (**Stack Internal**, a proprietary knowledge layer with no data exfiltration).
#Stack Overflow for Agents#coding agents#knowledge base
Blog post by **Pasquale Pillitteri** (software engineer, Palermo) published on **May 29, 2026** (FR version), 18-minute read, *Claude Code & Anthropic* section. **Pivot thesis**: *« Claude Opus 4.8 is the most powerful SEO model of 2026, but almost everyone uses it wrong »* — not a model problem but a **system** problem. The golden rule: ***« strategy is a whiteboard, production is an assembly line »*** — SEO must be **split into two distinct phases**, and mixing them is *« the fastest way to waste a model that costs five dollars per million input tokens and twenty-five for output »*. **Model context**: Opus 4.8 released on **May 28, 2026** (41 days after Opus 4.7), **1M-token** context, **GraphWalks Long-Context F1 at 1M: 40.3% → 68.1%**, **SWE-bench Verified 88.6%**, **USAMO 2026 96.7%** (+27.4 pts), **HLE with tool 57.9%**, unchanged price **$5/$25** per M tokens, **Fast Mode 2.5× at $10/$50**, four **effort levels** (Low, High, Extra, Max). **The central anti-pattern** = *« the giant conversation »* / **context drift**: mixing strategy, keyword research, competitive analysis and writing in a single chat produces a *« mush of contradictory intentions »* → the model slides toward **generic best practices** ("holistic optimization", "strategic approach") instead of data-anchored content. **Phase 1 — Strategy (whiteboard, visual UI, one-off)**: dashboard / Google Sheet / Claude.ai canvas to decide while looking at the data together. **3 plays**: (a) **classified keyword research** (table of volume / difficulty 0-100 / intent / business potential / priority = volume÷difficulty×business weight); (b) **visual competitive analysis** (topic-coverage matrix, gaps); (c) **phased roadmap** (quick wins M1-2 / medium term M3-6 / pillar pages M7-12). **Extra/Max** mode is justified here (*« one right strategic decision is worth a thousand well-written pages on the wrong keywords »*). 3 closed artifacts saved to Notion/Drive. **Phase 2 — Production (assembly line, Opus 4.8 + MCP)**: the model shifts from strategist to **execution machine**; every decision **anchored to live data** via the **Model Context Protocol**. **Minimum MCP stack**: **GSC MCP** (AminForou/mcp-gsc, 500+ stars), **official Ahrefs MCP** (98 stars), **GA4 MCP**; the `modelcontextprotocol/servers` repo = **86,440 stars**, **10,000+ active servers**, 97M SDK downloads/month. Setup ~35 min, monthly refresh ~20 min. **Weekly loop**: a single prompt pulls live data, builds the brief (top 10 SERP + GSC + Ahrefs), derives H2/H3, writes, checks density, suggests titles → **+45% productivity**, draft in **6-12 min** (explicit reference to **Ryan Law / Ahrefs content engineering**, 23 skills). Mentions Anthropic's **Dynamic Workflows** (up to 1,000 subagents). **4 common mistakes**: (1) not checking the numbers (spot-check mandatory, *trust & verify*); (2) fully replacing Semrush/Ahrefs (MCP is a **layer on top**, not a substitute); (3) ignoring the **paid-organic content gap** (education client case: **2,742 wasted terms / 351 opportunities** identified in 90 s); (4) using Opus 4.8 where **Haiku 4.5** suffices (meta descriptions, alt text). **Cost**: $1-3 per 2,500-word article. **Sonnet 4.6** suffices for recurring production, Opus 4.8 reserved for strategy. SEO-optimized and self-referential article (the author writes about SEO in content itself designed to rank for "Opus 4.8 SEO"). Direct convergence with **Ryan Law/Ahrefs** (cited), **systems around the model** (Dropbox/Okumura), **skills-over-prompts** (Lattice), Haiku/Sonnet/Opus model routing (Gupta token-to-outcome).
#Claude Opus 4.8#AI SEO#two-phase workflow
**Pasquale Pillitteri** — Ingénieur informatique / développeur logiciel basé à **Palerme** (Italie) · certifié Innovation Manager UNI 11814:2021. Auteur d'un blog tech actif (rubrique *Claude Code & Anthropic*) · avec une newsletter hebdomadaire (~3,4k lecteurs). Article publié en version **FR** le **29 mai 2026** (lendemain de la sortie d'Opus 4.8).
**Zed** blog post signed by **Franciska Dethlefsen** (head of growth and marketing), published on **May 14, 2026** — the day after Anthropic's announcement — to answer Zed users' questions. **Subject**: starting **June 15**, Anthropic **splits Claude subscription billing into two pools** — one for its **first-party tools** (chat, the official Claude Code CLI), the other for **third-party agent and SDK usage** (anything going through **ACP**, `claude -p`, or a third-party tool). Usage via ACP **then stops drawing from the Pro or Max limits** and switches to a monthly **"Agent SDK" credit**: **$20 for Pro, $100 for Max 5x, $200 for Max 20x**. Once the credit is exhausted, usage continues **at standard API pricing** if overage is enabled — otherwise requests stop until the next cycle. **The figure driving the article**: subscriptions had until then subsidized agentic usage by a factor of **≈15 to 30×** relative to API pricing, and the new credits are billed **at full API rates** — hence *« for anyone using agents heavily, this is a major cost increase »*. **Three options are proposed**, in an order that reveals Zed's position: (1) keep the subscription by running the **official `claude` CLI in a terminal inside Zed** rather than via ACP — *« when the official claude CLI runs in the terminal, it uses your subscription's limits, not the new credit »*; (2) use Zed's built-in agent with the provider of one's choice (Zed-hosted models, API keys, Copilot, local Ollama, DeepSeek); (3) plug in **any ACP agent** — OpenCode, Codex, Factory, Cursor —, several of which still offer rate-limited subscriptions that subsidize heavy usage. **The underlying thesis**, and the real reason for the post: *« ACP is an open protocol… so that your editor is never locked into one provider's pricing decisions »*, with the explicit anticipation that *« this kind of change won't be the last »*. **The post carries an addendum dated June 16, 2026** announcing that **the change is suspended**: ACP, `claude -p`, the Agent SDK, and third-party applications continue to work with subscriptions **as before**, no separate credit to claim, limits unchanged, Anthropic revising its plan with advance notice announced. **The artifact is thus self-contradicting**: its most important content — the reversal — postdates its own publication date by a month.
#Zed#Anthropic#Claude subscription
**Franciska Dethlefsen** — head of growth and marketing chez **Zed Industries**. Le rôle est déterminant pour lire le texte : ce n'est pas un billet d'ingénierie mais une **communication de crise produit** · écrite le lendemain d'une annonce d'un fournisseur dont Zed dépend · à destination d'utilisateurs inquiets. La signature growth/marketing explique la structure (problème → options → réassurance) et le fait que l'argument protocolaire arrive en conclusion plutôt qu'en tête.
Analyst note by **Mitch Ashley**, VP and Practice Lead for *CIO & Technology Buyers* and *Software Lifecycle Engineering* at **The Futurum Group**, published on **April 29, 2026** in the *Market Coverage News* section: short format, roughly **9,500 characters**, opening with five summary bullets and closing with five watch-list items. Subject: the deal announced on **April 21, 2026** under which **SpaceX** gains the right to acquire **Cursor** for **$60 billion** within the year, or to pay **$10 billion** for a compute partnership backed by **xAI**'s **Colossus** cluster in Memphis, described as equivalent to **1 million H100 GPUs**. (A) The two-need reading: Cursor was carrying both a compute ceiling and margin compression — the company pays market-rate prices for **Anthropic**'s and **OpenAI**'s models, which it routes to its customers while competing with them via its **Composer** line; SpaceX was seeking AI revenue and a narrative ahead of an IPO targeted for June. (B) The structure reading: a $10 billion floor and a $60 billion purchase option exercisable in publicly traded stock after the listing, which, Ashley writes, *"allocates risk more honestly than a straight acquisition."* (1) For buyers, it sets a **six-month** window to re-verify zero-data-retention clauses and vendor identity. (2) For providers, it distinguishes three exposures — **Google** shielded by **Antigravity**, **AWS** dependent on Anthropic, **IBM** lightly exposed but well positioned on the governance angle. The corpus already holds [[beck-starving-genies-usage-limits-ai-coding-2026-04-03]] on the resource constraint imposed on coding tools and [[nyt-musk-promises-spacex-ipo-track-record-2026-06-02]] on SpaceX's announcements.
#SpaceX#Cursor#Anysphere
Mitch Ashley · VP et responsable des pratiques CIO & Technology Buyers et Software Lifecycle Engineering chez The Futurum Group · ancien CIO et CTO.
Product announcement published on the **Stripe** blog on **April 29, 2026** by **Dan Hill** (Product Manager, Link Consumer Product), following on from the **Stripe Sessions 2026** keynote: the launch of **Link's wallet for agents**, built on a new building block, **Issuing for agents**. **The diagnosis fits in one sentence, and it is the most important one in the text**: *"While machine payments protocols are still gaining adoption, agents need to work with the payment options sellers and consumers use today."* → **Stripe acknowledges that machine-native payment protocols are not ready, and delivers a workaround for existing rails rather than a bet on new ones.** **The mechanism**: a consumer grants an agent access to their Link wallet via a **standard OAuth flow**; the agent then issues a *spend request* and receives either a **single-use card**, or a **Shared Payment Token** — backed by the cards and bank accounts already present in the wallet. Cardinal point: *"The agent never gets access to your raw payment credentials."* The credential is **scoped** (amount, currency, merchant) and the agent must supply the **transaction context** so the human understands what they are approving — the example given in the CLI is explicit: `amount 3500`, `merchant-name "Powdur"`, `context "Purchasing the Powdur Glow Renewal Vitamin C Serum as a gift for $35."`. **The structuring constraint is temporal, and it is owned as such**: *"Today, each request requires the person's review before the credential is shared with your agent"* — **human** approval, **transaction by transaction**, on the web or in the **new Link iOS and Android apps**. Spending limits and cases where the agent would act **without additional approval** are announced, not delivered. **The second layer is the real infrastructure product**: **Issuing for agents** opens the full set of Issuing APIs to anyone building their own agentic wallet — single-use virtual cards, fund storage, spend controls, card-level permissions, **at-authorization** antifraud controls, real-time visibility. Four use cases are cited: internal spend automation, agentic cards embedded at **fintechs**, **vertical SaaS** platforms issuing cards to SMBs under their own brand, **marketplaces** whose selling agents pay suppliers and logistics. **Distribution argument**: Link claims **more than 200 million consumers**, and the article cites **OpenClaw** as an example of a personal agent that benefits. **Two reservations worth flagging up front**: per-transaction approval is presented as a design convenience when it is actually **an admission that delegated agent authorization is not solved**; and stablecoin, *agentic tokens*, and "other payment methods" are all in the **future tense** (*"coming soon"*).
#Stripe#Link#wallet for agents
**Dan Hill** — Product Manager · **Link Consumer Product** chez Stripe. Auteur de l'annonce sur le blog Stripe · rubrique *Product*. Le rattachement au produit *Link Consumer* est significatif : l'annonce est écrite depuis le **portefeuille grand public** · pas depuis l'équipe protocole ni depuis Issuing — ce qui explique que le consentement de l'utilisateur final structure tout le texte.