Essay by **Bill Staples**, CEO of **GitLab**, published on **August 24, 2026** on the about.gitlab.com blog: an announced **31-minute** read, roughly **39,000 characters**, presented as the sequel to a memo written to the board of directors in January 2026 and partially published in May under the title *GitLab Act 2*. The text presents itself as a response to **Anthropic**'s AI-native SDLC playbook, published three days earlier, from which it borrows the opening line — "Code is no longer the bottleneck" — to pose the question that drives it: what becomes scarce when code becomes abundant. (A) The economic diagnosis: the useful unit is not cost per line but **cost per accepted change**, which aggregates generation, environment, context, verification, review, remediation, and governance; AI collapses the generation term alone, which makes the others proportionally heavier — an organization ten times faster at generating "will simply move the queue." (B) The architectural response: four capabilities — agent platform, machine-scale execution, durable context, governance — forming an enterprise layer that outlives the model, "The model should be replaceable. The agent should belong to the customer." (1) Three modes coexist durably, from human-driven legacy to autonomous development, against the idea of a single maturity curve. (2) The CI/CD pipeline becomes the place where the inner loop runs, instead of being an end-of-line gate. The figures cited are Stripe's, Spotify's, and Amplitude's; GitLab produces only one, about its own source control. The corpus already holds [[claxton-anthropic-ai-native-sdlc-playbook-2026-08-21]], the source this text responds to, and [[sfeir-sdlc-pdlc-articulation-2026-07-22]] on the SDLC/PDLC articulation that Staples adopts as his own.
#code abundance#cost per accepted change#theory of constraints
Bill Staples · directeur général de GitLab (fonction non affichée par la page) · sur le blog about.gitlab.com.
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.
Long-form essay by **Shubham Saboo** (X/Twitter) advancing a thesis on the Product Manager role in the age of agents: the next key skill is **not prompt engineering** but **Loop Engineering** — designing a *system that improves with every run* rather than writing the perfect prompt every time. A **loop** is a repeated cycle: change what shapes the agent's behavior → run it → evaluate the output → keep the change if quality rises, revert otherwise → **compound the learning** so the next version starts ahead. For a PM, the entry point is not code but the **durable artifacts** that encode their judgment: PRD-review skill, customer-call *summarizer*, evaluation rubric, launch checklist, research workflow, `CLAUDE.md`, prompt template, prioritization framework. Because they are reused, these artifacts **compound in both directions** — and **drift** silently (a CLAUDE.md that keeps growing, a checklist that gets ignored…): the model has not regressed, the artifacts have drifted unwatched. A loop has **5 parts**: trigger, action, **proof**, memory, **stop condition** (the most critical). **Evals** become PM work (testing the artifact against known examples: 3 good / 3 bad PRDs, 5 understood calls, 2 past launches). **Memory** lives on **GitHub** (the repo becomes "product memory": commits, diffs, eval results, decision log, rollback). Recommended first loop: a **weekly product signal loop** (every Friday). Taste remains central — but it now needs **proof**. Cites Boris (creator of Claude Code): "he no longer writes prompts, he writes loops."