Willison merges a blog feature from his phone; Wispr Flow idles at 800MB

TL;DR

• Simon Willison shipped a Sightings blog feature from his phone via Claude Code for Web.
• The build backfilled 10+ years of iNaturalist observations into homepage, archives, and search.
• Veracode found 52% of Claude Opus 4.7 tasks introduced at least one security vulnerability.
• Wispr Flow’s Electron app idles at ~800MB RAM, contending with VS Code for CPU on dev machines.
• SuperWhisper’s $249 lifetime license pulls privacy-sensitive buyers off $12-15/mo subscriptions.

Today’s AI Tech sits at the personal-workflow layer — what one developer can ship from a phone, and what’s actually running on a laptop while you dictate. Simon Willison merges a new Sightings blog feature built end-to-end on mobile through Claude Code for Web, the cleanest worked example yet of Anthropic’s mobile-agent rollout. Alongside it, an audit of Wispr Flow finds the voice-dictation app idling at ~800MB with 12 named subprocessors and zero-retention Privacy Mode shipping off by default — pushing privacy-conscious buyers toward SuperWhisper’s $249 on-device alternative.

The two stories share a shape. Willison’s phone build lands in minutes, but Veracode’s new study puts a 52% vulnerability rate on Claude Opus 4.7’s task output. Wispr’s 150+ WPM dictation is real throughput, and so is the RAM, the subprocessor list, and the opt-in default. The personal AI tool stack works — once you read past the demo.

Willison ships a blog feature by phone using Claude Code for Web

Source: simon-willison · published 2026-05-02

TL;DR

• Simon Willison built and merged a new blog feature — “Sightings” — entirely from his phone using Claude Code for Web.
• The system backfilled 10+ years of iNaturalist observations as first-class content on his homepage, archives, and search.
• The build is a canonical demo of Anthropic’s mobile-agent rollout: Claude Code Remote plus the GitHub-wired web sandbox.
• Backdrop: a Veracode study found 52% of Claude Opus 4.7 tasks shipped at least one security vulnerability.

A working demo of the “taxi-to-beach” pattern

Willison’s new Sightings feature pulls his iNaturalist wildlife photos into his blog as syndicated content — same treatment as his link blog and TILs, surfaced on the homepage, in date archives, and in site search. Search “lemur” and you get his 2019 Madagascar trip. The interesting part isn’t the feature; it’s that he wrote it on his phone, in Claude Code for Web, and merged it as PR 668 against simonwillisonblog.

That workflow is exactly what Anthropic has been building toward. VentureBeat documented February’s Claude Code “Remote” launch, which mirrors local CLI sessions to mobile and runs the agent in a cloud sandbox while the developer watches from a phone ¹. The web variant, per The New Stack, runs on Anthropic-managed instances tied directly to a GitHub repo, with parallel task execution and no local toolchain required ². Third-party tooling has already coined the “taxi-to-beach” pattern — kick off a refactor, walk away, approve the diff later ³. Willison’s PR is the cleanest public reference implementation of that loop to date: a non-trivial schema extension, an external API integration, and a 200+ row historical backfill, all driven from a smartphone.

The part Willison doesn’t dwell on

The broader Claude Code conversation in 2026 is significantly less cheerful. Forbes, citing a Veracode study, reports that 52% of tasks completed by Claude Opus 4.7 contained at least one security vulnerability, and quotes critics warning that mobile “vibe coding” risks producing “beautiful facades over broken foundations” ⁴. The Hacker News flagged two CVEs — CVE-2025-59536 and CVE-2026-21852 — under which simply opening an untrusted repository in Claude Code could trigger remote code execution or exfiltrate API keys ⁵.

Critics warn mobile “vibe coding” risks creating beautiful facades over broken foundations. ⁴

A personal blog feature isn’t where these failure modes bite hardest — Willison reviews his own diffs, the blast radius is his own site, and “Sightings” is read-mostly glue code. But it’s worth being honest that the harness producing the lemur backfill is the same harness security researchers are warning enterprises about. The optimistic demo and the contested tool are the same tool.

Routing around iNaturalist’s structure

The second half of the story is quieter but real. iNaturalist’s own community has been asking for years for tighter integration between scientific observations and personal narrative content — the platform’s rigid taxonomy makes it a poor home for storytelling ⁶. Willison’s “beats” approach effectively concedes that and inverts it: keep iNaturalist as the diagnostic record of truth, treat the blog as the narrative layer, and let a syndication pipeline bridge them. That’s a concrete reference design for a feature request the platform itself has not delivered.

Takeaway

Two arcs intersect in one PR: Anthropic’s push to make Claude Code a multi-surface agent ¹²³, and a personal-publishing pattern that routes around a platform’s structural limits ⁶. Willison sits firmly on the optimistic side of the first arc. Readers should hold the Veracode and CVE numbers ⁴⁵ in the other hand while admiring the demo.

---

Wispr Flow eats 800MB idle; SuperWhisper runs local for $249

Source: techcrunch-ai · published 2026-05-02

TL;DR

• Wispr Flow’s Electron build consumes ~800MB RAM idle, contending with VS Code for CPU on dev machines.
• 12 named subprocessors sit behind Wispr, including OpenAI, Anthropic, and Cerebras.
• Zero-retention “Privacy Mode” ships off by default for non-HIPAA Pro users, who must opt in manually.
• SuperWhisper’s $249 lifetime license and on-device model are pulling privacy-sensitive buyers off $12–15/mo subscriptions.
• Voice-to-IDE dictation hits 150+ WPM vs 40–80 WPM typing, feeding Cursor’s Composer directly.

The roundup buries the actual fault line

TechCrunch’s 2025 dictation ranking reads like a consumer-software shootout, but the practitioner conversation has moved past “which app feels nicest.” The category has split into two architectures with very different cost structures, and the ranking format flattens that split into a star rating.

On one side: Wispr Flow, the polished cloud-formatted incumbent. On the other: SuperWhisper, MacWhisper, and other whisper.cpp wrappers that run the model locally. The trade isn’t taste — it’s resource cost, recurring revenue, and where your audio goes.

Wispr’s hidden bill

Independent benchmarking puts Wispr Flow’s Electron-based Windows build at roughly 800MB RAM while idle, with measurable CPU contention against IDEs like VS Code and Cursor ⁷. For a tool you leave running all day next to a 4GB language server, that’s not free.

The pricing model is the second friction point. Cancellation write-ups cite the $12–$15/month subscription as the trigger, with SuperWhisper’s $249 one-time license framed as the obvious alternative for anyone planning to dictate for more than ~18 months ⁸. Service journalism rarely surfaces lifetime-vs-subscription math; the Reddit and Medium thread economy does.

Privacy is the moat now

The harder issue is what Wispr does with your voice. Community audits enumerate 12 named subprocessors in the data path — OpenAI, Anthropic, and Cerebras among them — and note that the “Privacy Mode” toggle (zero data retention) is disabled by default for non-HIPAA Pro accounts ⁹. Users have to opt in.

That detail matters because legal, medical, and enterprise buyers are precisely the cohort defecting to local Whisper variants. Privacy has hardened from a checkbox into a competitive wedge, and a ranked list that scores “transcription accuracy” without scoring “where the audio goes” is measuring the wrong axis.

The M&A noise around Wispr

The category is also consolidating. Wispr acquired Yapify AI in December 2025 to bolt “inbox zero” voice agents onto its dictation core — a clear pivot from utility to workflow agent ¹⁰. A January 2026 Signalbase post alleged Apple had acquired Wispr, but the company’s own March 2026 blog announced a $30M Series A and UK expansion, and PitchBook still lists it as private and independent ¹¹. Treat the Apple rumor as unconfirmed.

The dev story the roundup misses

The most interesting use case isn’t email replies — it’s “vibe coding.” Developers dictate high-level intent into Wispr or SuperWhisper, then pipe the transcript straight into Cursor’s Composer or Claude Code. Practitioners report meaningful throughput gains because human speech runs 150+ WPM versus 40–80 WPM for typing, and tools like Wispr’s Command Mode handle technical tokens (useEffect, not “use effect”) without manual cleanup ¹².

That’s the story buried under the star ratings: dictation has quietly become an input layer for agentic IDEs, and the choice between cloud polish and local privacy is now an architecture decision, not a preference.

Footnotes

1. VentureBeat — Anthropic Remote Control launch — https://venturebeat.com/orchestration/anthropic-just-released-a-mobile-version-of-claude-code-called-remote

   Anthropic just released a mobile version of Claude Code called Remote… letting developers initiate, monitor and steer long-running coding tasks from a smartphone while the agent executes in cloud sandboxes.

   ↩ ↩²

2. The New Stack — Claude Code Comes to Web and Mobile — https://thenewstack.io/anthropics-claude-code-comes-to-web-and-mobile/

   The web version runs on Anthropic-managed cloud instances, enabling users to point the agent at a GitHub repository and assign multiple tasks to run in parallel without local hardware constraints.

   ↩ ↩²

3. Nimbalyst — Best Mobile Apps for Claude Code 2026 — https://nimbalyst.com/blog/best-mobile-apps-for-claude-code-2026/

   The ‘taxi-to-beach’ workflow allows engineers to start a task, walk away, and later review visual diffs or approve small commits via their phones.

   ↩ ↩²

4. Forbes — Anthropic’s Claude Is Pumping Out Vulnerable Code — https://www.forbes.com/sites/the-wiretap/2026/04/22/anthropics-claude-is-pumping-out-vulnerable-code-cyber-experts-warn/

   A Veracode study found 52% of tasks completed by Claude Opus 4.7 included at least one security vulnerability… critics warn mobile ‘vibe coding’ risks creating beautiful facades over broken foundations.

   ↩ ↩² ↩³

5. The Hacker News — Claude Code Flaws Allow Remote Code Execution — https://thehackernews.com/2026/02/claude-code-flaws-allow-remote-code.html

   CVE-2025-59536 and CVE-2026-21852 previously allowed remote code execution and API key exfiltration when a user simply opened an untrusted repository containing malicious settings.

   ↩ ↩²

6. iNaturalist forum — Better Integration of Observations and Journal Posts — https://forum.inaturalist.org/t/better-integration-of-observations-and-journal-posts/1267

   Members have long requested tighter ties between observations and personal narrative posts; current platform structure forces photographers to choose between scientific records and storytelling.

   ↩ ↩²

7. Zack Proser — WisprFlow vs SuperWhisper — https://zackproser.com/blog/wisprflow-vs-superwhisper

   The Electron-based app can consume upwards of 800MB of RAM and significant CPU even when idle… it competes with IDEs like VS Code for system power.

   ↩

8. Ryan Shrott (Medium) — Why I cancelled my Wispr Flow subscription — https://medium.com/@ryanshrott/why-i-cancelled-my-wispr-flow-subscription-and-what-im-using-instead-d783433f4411

   Dissenting voices on Reddit note that while Wispr Flow offers the best ‘out-of-the-box’ experience, its subscription model ($12–$15/mo) is a point of contention compared to SuperWhisper’s $249 lifetime license.

   ↩

9. r/AIToolsTipsNews — Wispr Flow privacy setup 2026 — https://www.reddit.com/r/AIToolsTipsNews/comments/1sx9qmm/wispr_flows_privacy_setup_in_2026_12/

   Wispr Flow relies on twelve named subprocessors, including OpenAI, Anthropic, and Cerebras… default ‘Privacy Mode’ (zero data retention) is disabled for non-HIPAA accounts.

   ↩

10. Wispr Flow blog — Acquires Yapify AI — https://wisprflow.ai/post/wispr-flow-acquires-yapify

    Wispr aggressively expanded its functional footprint by acquiring Yapify AI in December 2025, integrating ‘inbox zero’ voice agents for context-aware email drafting.

    ↩

11. Signalbase M&A tracker — https://www.trysignalbase.com/news/acquisitions/wispr-flow-acquired-by-apple-acquisition

    A single report from Signalbase in January 2026 alleged that Apple had purchased Wispr Flow… however, in March 2026 the company’s official blog detailed a $30M Series A and UK expansion, and PitchBook continued to list Wispr as ‘Private.’

    ↩

12. Carl Rannaberg (Medium) — My current AI coding workflow — https://carlrannaberg.medium.com/my-current-ai-coding-workflow-f6bdc449df7f

    Developers verbally describe high-level requirements into WisprFlow or Super Whisper, then feed transcripts into Cursor’s Composer mode… human speech reaches 150+ WPM vs typing’s 40–80 WPM.

    ↩