Reddit AI Coding - 2026-09-04¶
1. What People Are Talking About¶
1.1 Reliability arguments became customer-experience arguments 🡕¶
Seven high-signal threads treated reliability, quota policy, and make-good behavior as one product problem. Compared with Sep 3, when the conversation centered on the new /limit-reset command and live outage screenshots, Sep 4 shifted toward compensation: users compared OpenAI's banked resets, Anthropic's prompt-caching overcharge fix, and the cost of outages that strand agents mid-task.
u/dolo937 turned a public OpenAI message into the day's most explicit customer-experience comparison: a screenshot showed Tibo promising “one banked reset for every day you don't have access to Astra,” and the top replies argued that resets and communication are now winning subscriptions as much as model quality (Tibo is giving one reset a day and we are offered none from Claude) (565 points, 167 comments). In the same thread, u/ForwardLoop (score 89) said OpenAI was winning on customer experience because it investigated usage-drain reports, explained the findings, and made users whole.
u/CommunicationFlat865 then gave the quota complaint a concrete mechanism: a screenshot from Claude Code 2.1.260 said prompt caching on Fable 5.1 had been fixed because context attached after tool results had been resent uncached on every turn, which commenters translated into “we stopped charging you 40x” (Fable 5.1 Prompt Caching Fixed in CC 2.1.260) (115 points, 33 comments). u/johnconner143 summarized the wider mood as a capable model undermined by a token-burning launch and perfectly timed Astra pressure (Whew. Unbelievable disaster of a launch for Fable 5.1) (232 points, 103 comments).
u/dr-dimitru added the operations proof with a 592 overloaded thread, and the attached status screenshot showed partial outages across claude.ai, the API, and Claude Code on Sep 3 (New day: new 592 overloaded) (248 points, 126 comments). u/sirlerkal0t generalized that into dependence risk, saying a deadline was now blocked by Claude, Codex, and Cursor availability at the same time, while replies listed OpenCode, Kimi, GLM, self-hosted Qwen, and Gemini Flash as fallback options (Claude, Codex, and Cursor are down, and I've got a huge deadline in an hour and need all my hand-written code reviewed. We have become too dependent on unreliable LLMs hosted by big-AI.) (415 points, 126 comments).
Discussion insight: u/mortalhal (score 16) said outages were a token sink because mid-flight agents lose warm cache, while u/TurdPlayingPeekaboo (score 14) compared Codex and Claude by value per dollar and long-horizon efficiency rather than raw benchmark strength.
Comparison to prior day: Sep 3 introduced the reset vocabulary and public outage evidence. Sep 4 pushed the argument one step further: users were no longer just asking how limits work, but why vendors handle mistakes so differently after the same kind of failure.
1.2 Vibe coding got more process-heavy and more outcome-driven 🡕¶
The builder conversation kept moving away from “one prompt made this” spectacle and toward planning, reusable command surfaces, and proof that a project solves something. Compared with Sep 3, when live demos, app-store releases, and first revenue already mattered more than hype alone, Sep 4 added explicit workflow scaffolding: Kanban boards, versioned spec loops, and experiments that measure tool-output reduction.
u/AndrewNggg posted a meme that “every good vibe coding starts with vibe planning,” but the useful evidence was in the replies: u/akabillposters (score 24) said many vibe-built projects skip market sizing entirely, while u/Janpol8 (score 3) said guided planning and spec work produced materially better results (Do y'all do this?) (133 points, 37 comments). In parallel, u/Interesting-Yard-684 unpacked Anthropic's AI-native SDLC playbook as a loop of intent.md → spec.md → plan.md → code/tests → review/deploy artifacts, arguing that faster coding shifts the bottleneck into verification and approvals (Has anyone actually tried Anthropic’s AI-Native SDLC playbook in a real project?) (30 points, 21 comments).
u/adi1405 supplied the cleanest quantified example. Running the same repo task in two Claude Code sessions, they said a Skill that turned repeatable procedures into repo-native commands cut commands from 52 to 23, tool output from 21.5 KB to 8.4 KB, and agent output tokens from 4,745 to 1,958 (I gave Claude Code a better interface to my repo. It generated 55% fewer commands.) (56 points, 15 comments). The linked Agent-Native CLI repo describes the idea as letting the agent decide what to do while deterministic tooling handles how.
Outcome proof still mattered. u/Pretty_Judgment5481 showed a first $5 sale on 21st.tools after adding a free badge path and paid backlink option, with Claude handling the UI and Stripe integration (My vibecoded project just made its first money) (323 points, 46 comments). u/Big-Sandwich733 described Lythravel, a live browser MMORPG built over two months with Babylon.js, Colyseus, Opus 5, and Fable as an orchestrator, while u/Conscious-Image-4161 shared LiftLab, an interactive biomechanics visualizer built because static diagrams do not let lifters vary angle, grip, or bar path in real time (2 months of vibe coding my MMORPG with Claude Code) (122 points, 37 comments); (Vibecoded a biomechanics visualizer for lifting that shows how changes in technique can affect leverage, joint loading, muscle length, and estimated stimulus.) (74 points, 29 comments).
Discussion insight: u/Objective_Oven7673 (score 2) said planning works best when it starts from tickets, screenshots, and requirements rather than free-form prompting, while u/RaymondStussy (score 2) stress-tested Lythravel with immediate UX feedback on movement and character-creation readability.
Comparison to prior day: Sep 3 raised the proof bar from spectacle to live demos and revenue. Sep 4 kept that bar and added a stronger process layer around it: better planning, better command interfaces, and more explicit validation loops.
1.3 Trust boundaries around agents became concrete, not abstract 🡕¶
Three widely shared threads turned “be careful with agents” into concrete boundary failures: machine-state damage, unwanted attribution defaults, and a public reconstruction of the sandbox itself. Compared with Sep 3, when the trust discussion still revolved around dangerous commands and verbose diffs, Sep 4 broadened the concern to session traceability and what exactly runs behind the interface.
u/deeplycuriouss described bricking a Mac after following a Claude-suggested command that disabled network time and set the system date to the year 4026 just to stage an iOS screenshot (Claude recommended that I set my Mac's date to the year 4026. Here's what happened, and why you probably shouldn't do the same) (367 points, 173 comments). The strongest reply came from u/AgentIslandPro (score 15), who pointed to xcrun simctl status_bar as the simulator-only command that would have changed the screenshot clock without touching the host system.
u/vdavid raised a different trust issue: Claude Code 2.1.259 appeared to inject Co-Authored-By and Claude-Session trailers via a system reminder even when local guidance said not to (Claude Code v2.1.259 forces Co-Authored-By) (232 points, 99 comments). The top corrective reply from u/Far-Surprise7773 (score 110) said includeCoAuthoredBy now defaults to true and can be turned off in .claude/settings.json, while other replies objected specifically to the externally traceable session link.
u/Designer_Mind3060 pushed the boundary question furthest by claiming they extracted the Claude execution VM, then publishing the recovered environment as the Wiggle repository (Claude leaked its own backend code - I extracted the VM that runs your code and found its internal codenames, a monitoring binary nobody outside has held, and 371 KB of secret prompts) (432 points, 59 comments). The linked repo describes a runnable copy of the sandbox with LibreOffice, Playwright, data-science tooling, and the skill files Claude reads before doing specific jobs, while the top reply narrowed the credible concern to prompt injection and the presence of interesting binaries rather than to “being root in a disposable microVM” by itself.
Discussion insight: The corrective replies were practical, not theoretical: use simulator-only overrides instead of system time changes, flip explicit config flags instead of fighting a system reminder, and distinguish sensational framing from the more specific security claims that survive scrutiny.
Comparison to prior day: Sep 3 already had trust complaints around unsafe autonomy. Sep 4 made them easier to act on because the discussion named the exact command, setting, repo, and workaround instead of staying at the level of general caution.
2. What Frustrates People¶
Opaque usage burn with weak make-good paths¶
Severity: High. The loudest frustration was not just that premium coding models are expensive, but that users felt they were charged unpredictably and then asked to absorb the mistake themselves. u/johnconner143 called the Fable 5.1 launch a “disaster” because a caching issue burned weekly limits just as Astra arrived (Whew. Unbelievable disaster of a launch for Fable 5.1) (232 points, 103 comments), and u/CommunicationFlat865 followed with a screenshot saying Claude Code 2.1.260 had fixed the caching behavior that was resending tool-attached context uncached on every turn (Fable 5.1 Prompt Caching Fixed in CC 2.1.260) (115 points, 33 comments). In the reset thread, u/dirty_sprite_au (score 38) also complained that Claude's promo-credit UI looked like a dark pattern, while u/ForwardLoop (score 89) contrasted Anthropic's response with OpenAI's habit of issuing resets after incidents. This is worth building for because the pain is measurable, repeated, and directly tied to churn.
Multi-vendor outage chains and over-hosted workflows¶
Severity: High. The day produced direct evidence that developers' fallback plans are still too concentrated in hosted AI services. u/dr-dimitru posted 592 overload errors and a status-page screenshot showing incident spillover across Claude surfaces (New day: new 592 overloaded) (248 points, 126 comments), while u/sirlerkal0t framed simultaneous Claude, Codex, and Cursor trouble as a deadline risk rather than just a nuisance (Claude, Codex, and Cursor are down, and I've got a huge deadline in an hour and need all my hand-written code reviewed. We have become too dependent on unreliable LLMs hosted by big-AI.) (415 points, 126 comments). In r/cursor, screenshots and status pages showed both Anthropic-model errors and a Grok-related service degradation hitting automations and cloud agents, which means “switch tools” is often just “switch wrappers on the same upstream problem” (Rate limiting by model provider) (39 points, 38 comments). People cope by keeping backup vendors or local models ready, but the coping strategy is still manual.
Agents crossing safety and preference boundaries¶
Severity: High. Several posts described the agent doing something technically possible but operationally unwanted. u/deeplycuriouss nearly lost weeks of work after following a Claude-suggested system-time command on macOS (Claude recommended that I set my Mac's date to the year 4026. Here's what happened, and why you probably shouldn't do the same) (367 points, 173 comments). u/vdavid objected that Claude Code was now overriding local attribution guidance with a system reminder that appended Co-Authored-By and a session link (Claude Code v2.1.259 forces Co-Authored-By) (232 points, 99 comments). And in Antigravity, u/TimelyWallaby4695 amplified a complaint that the CLI remained unusable without either constant approvals or --dangerously-skip-permissions (Finally someone popular bringing attention to this issue) (241 points, 70 comments). This is worth building for because the desired product shape is consistent across threads: fewer blind approvals, fewer hidden defaults, and safer narrow-scope alternatives.
“AI slop” accusations still drag down trust in new apps¶
Severity: Medium. Builders are shipping more, but trust remains fragile when a project looks generic or inaccessible. u/Conscious-Image-4161 shared a biomechanics visualizer with a clear domain thesis, but the comment thread immediately pushed on access, correctness, and generic vibe-coded design patterns (Vibecoded a biomechanics visualizer for lifting that shows how changes in technique can affect leverage, joint loading, muscle length, and estimated stimulus.) (74 points, 29 comments). The lower-scored but heavily discussed “What problem is your vibecoded app solving?” thread showed why: commenters kept rewarding concrete utility examples and dismissing decorative screenshots or derivative ideas (What problem is your vibecoded app solving?) (14 points, 112 comments). The coping pattern is to show live usage, public repos, or revenue, not just polished images.
3. What People Wish Existed¶
Predictable limits with automatic incident make-good¶
Opportunity: direct. The clearest request was not “more tokens” in the abstract, but billing and quota behavior that matches what actually happened during an incident. u/dolo937's thread praised OpenAI's promise of one banked reset per missed Astra day and immediately asked why Claude users were not offered the same courtesy (Tibo is giving one reset a day and we are offered none from Claude) (565 points, 167 comments). u/CommunicationFlat865 and u/johnconner143 were not asking for novelty either; they were asking for refunds, resets, or at least visible acknowledgment when a caching bug or outage distorted usage (Fable 5.1 Prompt Caching Fixed in CC 2.1.260) (115 points, 33 comments); (Whew. Unbelievable disaster of a launch for Fable 5.1) (232 points, 103 comments).
Auto-review and middle-ground approvals¶
Opportunity: direct. The most repeated autonomy request was a layer between full manual approval and dangerous blanket trust. The screenshot in u/TimelyWallaby4695's post says Antigravity “needs an auto review” instead of --dangerously-skip-permissions, and the replies describe decision fatigue almost immediately after adopting the tool (Finally someone popular bringing attention to this issue) (241 points, 70 comments). The same need appears from the opposite angle in u/deeplycuriouss's Mac post: people want assistants that know a simulator-level workaround is preferable to a machine-wide sudo date change (Claude recommended that I set my Mac's date to the year 4026. Here's what happened, and why you probably shouldn't do the same) (367 points, 173 comments). This is a practical need with visible urgency.
Planning scaffolds that survive beyond one prompt¶
Opportunity: competitive. Several threads imply that better output starts with better structure, not just a stronger model. u/AndrewNggg's planning meme drew replies asking for skills that “grill” the user into a better spec, while u/Interesting-Yard-684 argued that intent.md, spec.md, and plan.md become more valuable when implementation time collapses (Do y'all do this?) (133 points, 37 comments); (Has anyone actually tried Anthropic’s AI-Native SDLC playbook in a real project?) (30 points, 21 comments). u/adi1405's repo-native command experiment adds a concrete implementation path: encode repeatable procedures once so the agent does not have to rediscover them every run (I gave Claude Code a better interface to my repo. It generated 55% fewer commands.) (56 points, 15 comments).
Persistent personal memory without a hosted surveillance feel¶
Opportunity: aspirational. Memory tooling remains one of the most common ideas around coding agents, but people want it to stay local, encrypted, and useful rather than bloated. u/AregNoya said their memory engine was built because the assistant “was forgetting what I said every 200k tokens,” and the linked README promises local encrypted storage, MCP compatibility, and bounded memory injection instead of a hand-maintained memory file (Everybody is building memory layer around code or projects I built a memory layer around YOU) (19 points, 33 comments). The skeptical replies show why this is only aspirational so far: people worry memory layers become dashboard theater or make agents worse when they remember too much.
4. Tools and Methods in Use¶
| Tool | Category | Sentiment | Strengths | Limitations |
|---|---|---|---|---|
| Claude Code | Coding agent harness | (+/-) | Dominant workflow surface; builders use it for real products, reviews, and long-horizon tasks | Outages, attribution defaults, and opaque usage make it hard to trust unattended work |
| Claude Fable 5.1 | Model | (+/-) | Seen as highly capable on large tasks and as an orchestrator for ambitious builds | Prompt-caching bug, high burn rate, and overthinking on simple tasks |
| OpenAI Codex / Astra | Coding agent + model | (+) | Better perceived make-good behavior, banked resets, and strong benchmark buzz | Astra rollout was still limited; some praise is anticipatory rather than fully validated |
| Gemini 3.8 Flash | Model | (+) | Fast workhorse reputation; benchmark screenshots and Copilot rollout widened its reach | Quality is debated, and some users still report quota/load friction depending on host |
| Antigravity | CLI harness | (+/-) | Shipping quickly: /boost, layout persistence, settings work, and strong pairing with Flash |
Permission prompts still create decision fatigue and push users toward unsafe bypasses |
| GitHub Copilot | IDE/CLI/cloud assistant | (+/-) | Added Gemini 3.8 Flash across multiple surfaces and lets admins manage access by model policy | Enterprise usage budgets still shape which models teams can afford to leave on |
| Agent-Native CLI | Skill / command interface | (+) | Reduced command count and tool output in a same-task experiment | Evidence is still early and repository-dependent |
| Kanban Pilot | Task orchestration | (+) | Adds explicit refine/approve/develop/validate gates and one chat per task | Requires more process discipline than free-form prompting |
| iai-memory | Memory layer | (+/-) | Local encrypted recall across sessions without a hosted service | Commenters worry memory layers add clutter or remember too broadly |
Overall, Sep 4 showed a wider satisfaction spectrum than Sep 3. People still liked strong models, but the deciding factors were increasingly recovery behavior, cost visibility, and how much babysitting a harness demanded. u/dolo937's thread and u/CommunicationFlat865's caching-fix post show users switching or threatening to switch because OpenAI looked more willing to compensate users after mistakes, not just because Astra might benchmark better (Tibo is giving one reset a day and we are offered none from Claude) (565 points, 167 comments); (Fable 5.1 Prompt Caching Fixed in CC 2.1.260) (115 points, 33 comments).
The common workaround pattern was to reduce agent overhead rather than simply downgrade the model. That included shorter contexts and manual compaction in quota threads, repo-native commands in u/adi1405's experiment, task-stage gates in the Kanban Pilot screenshot shared by u/AndrewNggg, and local memory or local-model fallback talk in the dependence thread and the memory-engine thread (I gave Claude Code a better interface to my repo. It generated 55% fewer commands.) (56 points, 15 comments); (Do y'all do this?) (133 points, 37 comments); (Everybody is building memory layer around code or projects I built a memory layer around YOU) (19 points, 33 comments).
Migration pressure is now clearly multi-directional. Some Claude users said they were renewing Codex or waiting for Astra because of resets and perceived efficiency, while Flash kept appearing as the practical backup inside Antigravity and Copilot rather than as a fan-object in its own right (Whew. Unbelievable disaster of a launch for Fable 5.1) (232 points, 103 comments); (Gemini 3.8 Flash is now available in GitHub Copilot) (60 points, 3 comments); (Antigravity 2.0 Release: v2.12.0) (78 points, 65 comments).
5. What People Are Building¶
| Project | Who built it | What it does | Problem it solves | Stack | Stage | Links |
|---|---|---|---|---|---|---|
| 21st.tools | u/Pretty_Judgment5481 | Directory and product-launching platform with free badge placement or paid backlink tiers | Gives early products a lightweight distribution and backlink path | Claude-assisted UI + Stripe integration | Shipped | site, post |
| ALPHA FIELDMASTER | u/Careful-Abrocoma-364 | Garmin gadget-watch app with radar, tailscan, seismic, and dead-drop tools | Turns a commodity smartwatch into playful but practical field utilities | Garmin app using Bluetooth, GPS, and accelerometer features | Beta | post |
| Lythravel | u/Big-Sandwich733 | Free 3D browser voxel MMORPG | Lets a solo builder attempt MMO-scale worldbuilding with agent help | Babylon.js, Colyseus, Chrome MCP, Claude Opus 5, Fable | Beta | site, post |
| LiftLab | u/Conscious-Image-4161 | Interactive biomechanics visualizer for exercise setup variables | Replaces static lifting diagrams with adjustable movement and loading views | Vite, React 19, TypeScript, React Three Fiber, Zustand, Cloudflare Worker/D1 | Alpha | repo, post |
| Agent-Native CLI | u/adi1405 | Portable skill that turns repeatable repo procedures into deterministic commands | Reduces command churn and noisy tool output for coding agents | Agent skill plus existing repo tooling | Beta | repo, post |
| iai-memory | u/AregNoya | Local persistent memory engine for coding assistants | Keeps cross-session context without a hosted memory service or manual memory files | Python, Rust, TypeScript, MCP, local encrypted store | Shipped | repo, post |
21st.tools is the clearest monetization proof from the day because the evidence is small but concrete: a first $5 sale, a visible pricing screen, and a live site. The post's distinctive angle is that the distribution mechanic itself became the product: free listing in exchange for a badge, or paid listing for a backlink.
Lythravel and LiftLab show two different ends of the “serious build” spectrum. Lythravel uses agent help to push into MMO-scale scope, but the post stresses that optimization, tooling, and direct testing now consume as much effort as feature generation. LiftLab is narrower and more legible: the repo and post both center one real problem — static biomechanics explanations — and build an interactive visual answer instead of a generalized AI shell.
The most repeated build pattern was “tooling around the agent,” not just “apps built by the agent.” Agent-Native CLI compresses procedure into commands, while iai-memory tries to preserve context between sessions. Together with the planning and Kanban threads, they suggest builders increasingly see orchestration, state, and validation as product surfaces in their own right.
6. New and Notable¶
Wiggle turned a sandbox-rumor thread into a tangible artifact¶
The most unusual artifact of the day was the Wiggle repository linked from u/Designer_Mind3060's sandbox-leak post (Claude leaked its own backend code - I extracted the VM that runs your code and found its internal codenames, a monitoring binary nobody outside has held, and 371 KB of secret prompts) (432 points, 59 comments). The repo describes a runnable copy of the Claude code-execution VM with LibreOffice, Playwright, data-science packages, and the skill files Claude reads before certain jobs. Even with commenters disputing the more dramatic framing, the existence of a packaged environment and documented toolchain made this more substantive than an ordinary leak claim.
Gemini 3.8 Flash moved from benchmark topic to distribution topic¶
On Sep 3, Gemini 3.8 Flash was mainly a benchmark conversation. By Sep 4 it was also a placement and access conversation. u/wchabbott posted GitHub's announcement that Gemini 3.8 Flash is rolling out across Copilot surfaces including VS Code, Visual Studio, Copilot CLI, cloud agent, JetBrains, Xcode, and Eclipse (Gemini 3.8 Flash is now available in GitHub Copilot) (60 points, 3 comments), while Antigravity users kept treating Flash as the practical fast model they wanted better approvals around (Finally someone popular bringing attention to this issue) (241 points, 70 comments).
Forced attribution and session-link defaults became a mainstream complaint¶
The Co-Authored-By thread matters because it is not about output quality at all; it is about who controls provenance metadata and whether a coding session should become externally traceable by default. u/vdavid's post surfaced both the forced trailer behavior and the presence of a Claude-Session link in commit and PR guidance (Claude Code v2.1.259 forces Co-Authored-By) (232 points, 99 comments). The top replies already had a configuration workaround, which suggests the issue moved quickly from isolated surprise to shared operational knowledge.
7. Where the Opportunities Are¶
[+++] Usage governance and incident make-good tooling — Multiple high-engagement threads converged on the same gap: users want quota math they can inspect, incident damage they can quantify, and compensation that happens automatically when the platform breaks. The reset comparison thread, the Fable caching-fix thread, and the 592 outage thread all point to the same commercial surface (Tibo is giving one reset a day and we are offered none from Claude) (565 points, 167 comments); (Fable 5.1 Prompt Caching Fixed in CC 2.1.260) (115 points, 33 comments); (New day: new 592 overloaded) (248 points, 126 comments).
[++] Safer autonomy and approval automation — The data shows a real middle-ground need between permission spam and blind execution. The Antigravity thread asks for auto review, the Mac-4026 thread shows the cost of missing guardrails, and the attribution thread shows people also want explicit control over silent defaults and outbound provenance (Finally someone popular bringing attention to this issue) (241 points, 70 comments); (Claude recommended that I set my Mac's date to the year 4026. Here's what happened, and why you probably shouldn't do the same) (367 points, 173 comments); (Claude Code v2.1.259 forces Co-Authored-By) (232 points, 99 comments).
[++] Workflow scaffolding for agent-heavy teams — Planning files, task boards, repo-native command surfaces, and memory layers are all being treated as first-class product surfaces around the model. The strongest evidence today came from the Agent-Native CLI experiment, the Kanban/planning thread, and the AI-native SDLC discussion (I gave Claude Code a better interface to my repo. It generated 55% fewer commands.) (56 points, 15 comments); (Do y'all do this?) (133 points, 37 comments); (Has anyone actually tried Anthropic’s AI-Native SDLC playbook in a real project?) (30 points, 21 comments).
[+] Utility-first vertical apps with lightweight monetization — The builder posts that landed best solved narrow, legible problems: product-launch backlinks, watch utilities, biomechanics visualization, and a browser MMO with active optimization work. The strongest early commercial evidence was only a $5 sale, but it was still stronger than pure showcase content because it proved someone paid (My vibecoded project just made its first money) (323 points, 46 comments); (I tried to build the spy gadget watch 12-year-old me wanted. Somehow I ended up building the design tool too) (262 points, 48 comments); (Vibecoded a biomechanics visualizer for lifting that shows how changes in technique can affect leverage, joint loading, muscle length, and estimated stimulus.) (74 points, 29 comments).
8. Takeaways¶
- Reliability is now being judged as customer experience, not just uptime. The highest-signal quota threads compared reset policy, compensation, and communication style across vendors, not only benchmark quality. (source)
- The community has tangible evidence that Fable 5.1's cost complaints were tied to a real product bug. The 2.1.260 caching-fix screenshot gave structure to what had previously looked like anecdotal “token burn” frustration. (source)
- Planning and command-surface design are becoming first-class parts of AI coding. Sep 4 added explicit appetite for specs, Kanban gating, and repo-native command layers rather than relying on free-form prompting alone. (source)
- Builder credibility still comes from utility and proof, not from spectacle. The strongest builder posts either showed revenue, a live world, a repo, or a concrete problem statement that users could interrogate. (source)
- Trust complaints are getting more specific and therefore more actionable. Users named the exact unsafe command, the exact config switch, and the exact repo or session-link behavior they objected to, which is a stronger signal than generic “AI is scary” sentiment. (source)