Skip to content

root / tags / cold-start

#cold start

2 fiches

Tools & Platforms Auto-verified translation

ChatGPT Desktop & Claude Desktop vs versions web — Rapport « What ? — So What ? — Now What ? »

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.

Tools & Platforms Auto-verified translation

ZML/LLMD : et si le « Docker des LLM » était français ?

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.

#LLM Inference#serving#ZML

SFEIR (voix éditoriale du cabinet)