Reddit AI Agent - 2026-08-22¶
1. What People Are Talking About¶
1.1 Control is being specified as files, gateways, and allow-lists (🡕)¶
The strongest governance threads were no longer debating whether agents need boundaries. They were debating which layer should own them: repo instructions, gateway policy, target-system IAM, or payment controls. This theme was supported by at least six strong posts plus one linked field study.
u/ohansemmanuel turned repo rules into a measurable signal in What the 100 biggest GitHub repos put in their AGENTS.md files (89 points, 41 comments). The linked field study says 27% of the top 1,000 public GitHub repos had a root AGENTS.md, the 100-repo sample covered 11.4 million stars, the median file length was 1,198 words, and the corpus contained 784 explicit negative-rule bullets. In the thread, u/Neon_Camouflage (score 9) said the heavy use of “must / always / never” is not surprising because agents do better with hard lines than with ambiguous preferences, while u/turboblahblah (score 3) argued that some of those “don’t do X” rules should graduate into custom lint checks.
u/Arc_bong asked where permissions actually belong in Where should an AI agent's permissions actually be enforced? (9 points, 10 comments). The most detailed reply from u/vgmartinez (score 2) argued for enforcement outside the runtime: a gateway or proxy in front of model calls and MCP tools, plus the target system’s own authorization. That matched the linked TrustGate README, which describes a Go gateway with separate admin, proxy, and MCP planes for routing, policy, and observability. The duplicate AgentsOfAI cross-post carries the clearest visual summary of the same debate.
u/phucphungbk made the repo-local version of the same argument in I think we're underestimating how much control coding agents actually need (7 points, 24 comments). The post lists the failure modes directly: changing unrelated files, silently adding dependencies, skipping tests, and optimizing for test-passing instead of maintainability. In replies, u/Several_Guarantee530 (score 1) said their written ruleset forces agents to flag security-sensitive changes, disclose what changed and why, and escalate dependency additions instead of sneaking them in.
u/Hopeful-Horse7580 pushed the same boundary problem into commerce in any way to stop an agent from buying from the wrong merchant? (18 points, 20 comments). u/AnyCow4167 (score 5) recommended merchant restrictions plus one-time cards, and u/leading-a-swarm (score 1) described a setup where the agent emits purchase intent but a separate service owns the card, daily cap, and allow-list.
Discussion insight: Across coding, internal tools, and payments, the repeated claim was the same: runtime or prompt checks are guardrails, not authorization. The real boundary has to sit in a file, gateway, IAM policy, or payment service the model cannot rewrite.
Comparison to prior day: August 21 emphasized approval rails and spender separation. August 22 pushed that same instinct into repo manuals, MCP gateways, and merchant allow-lists.
1.2 Trust is shifting from “autonomous” to “observable and recoverable” (🡕)¶
The most convincing autonomy examples were not the most unconstrained ones. They were the ones that preserved state, surfaced blocked work, and published their limits. This theme was supported by five strong posts and two informative artifacts.
u/lochid_om described exactly that tradeoff in I let a multi-agent team build something for five days. It refused to call the result finished (2 points, 11 comments). The run logged 273 activity events and 64 managed build/test commands, but the packaged app still crashed during final verification, so the workflow ended blocked instead of claiming success. u/fn7Helix (score 3) added the key nuance: much of the apparent agent failure was really late feedback, because the packaged app was only tested at the end.
u/No_Departure_9908 published the more public-facing version in My Claude Fable 5 agent that has its own wallet, domain, and email (22 points, 19 comments). The claim is externally checkable: the Cairn about page says the agent runs Claude Fable 5 via Claude Code, wakes 5-15 times a day, and writes a public journal; the autonomy page separates what the agent can do alone from what still requires a human signature. Money out of the treasury is never unilateral because the vault is a 2-of-2 multisig.
u/KyloMango said the same thing from small-business delivery in Building AI agents for small businesses taught me the "AI" is the easy part (14 points, 5 comments). Their bottlenecks were dirty customer records, approval gates, logs, freezeable state, and someone watching the run. The post is explicit that what ships is “a big boring machine with one small model-shaped gap in it,” not an end-to-end autonomous company.
Portable memory showed up as the next layer of this trust problem. In Local memory for AI (13 points, 16 comments), u/Rudy_PH described a cross-CLI memory tool, and u/Rhishi99 (score 3) immediately turned it into a systems spec: local SQLite storage behind a tiny MCP shim, decay scoring before forgetting, OS-keychain-backed secrets, and conflict handling for laptop/desktop sync.
Discussion insight: The day’s trustworthy systems were not the ones promising less supervision. They were the ones making blocked state, audit trails, and persistence visible enough for a human to recover the run.
Comparison to prior day: August 21 already treated message buses and append-only logs as the real infrastructure. August 22 extended that idea into portable local memory and public boundary maps.
1.3 The things getting shipped are narrow workflows with swappable surfaces (🡕)¶
The concrete builds shared on August 22 were rarely “general agents.” They were bounded pipelines with deterministic scaffolding, one or two fuzzy steps, and a visible approval or history layer. This theme was supported by at least five builder threads.
u/Academic-Swan-9191 asked how to build a Hermes-plus-MCP-plus-n8n stack in Building an Autonomous Multi-Agent System (Hermes + MCP + n8n): Where should I start? (41 points, 14 comments). The strongest replies from u/Opening-Web-2246 (score 5), u/coldbrew_jay (score 2), and u/BP041 (score 2) all advised shrinking the ambition: prove one end-to-end workflow in plain n8n first, cap tool calls, and give each team its own execution record.
u/mutonbini shared a workflow that creates viral clips from YouTube videos using an open-source alternative API to OpusClip (22 points, 2 comments). The linked OpenShorts README says the same software can run self-hosted or hosted, exposes an MCP endpoint, and supports direct publishing to TikTok, Instagram, and YouTube after approval.
u/easybits_ai shared Classify contracts and track renewals in n8n (17 points, 6 comments). The linked workflow page says a single extraction call classifies the contract and extracts renewal fields, then n8n calculates the dates and appends the result to a class-specific Google Sheet tab.
u/ApifyEnthusiast1 shared a weekly Bing rank tracker (10 points, 6 comments). The linked template page says the workflow reads prior history from the same sheet before it searches again, so each row carries movement versus last week instead of a bare rank.
Discussion insight: The repeated shipping pattern was schedule + queue + sheet + approval + append-only history. AI is present, but the durable product is usually the workflow around it.
Comparison to prior day: August 21 already favored “AI to build the workflow, not to sit inside every run.” August 22 made that preference much more concrete through published templates and system diagrams.
1.4 Communities are pushing back on slop, vague labels, and throughput theater (🡕)¶
A second major topic was evidence quality inside the conversation itself. Users objected to AI-written posting styles, apples-to-oranges output claims, and category labels that collapse real workflow differences. This theme was supported by four high-signal threads.
u/EcstaticDentist kicked off the loudest sentiment thread in Half the posts here read like they were written by a clanker (34 points, 44 comments). The replies mostly agreed, and u/ssh-agent (score 7) made the joke explicit by pasting a deliberately ChatGPT-shaped answer to show what readers are tired of.
u/Known_Match_9122 treated benchmark marketing with similar suspicion in 75x the PR throughput of Google AX? That sounds wild. (22 points, 16 comments). The linked Kungfu methodology page does report a 3,913-versus-52 merged-PR ratio for a fixed 30-day window, but it also says merged PRs are not a productivity or value unit and that repo scopes and workflow disciplines differ.
u/we_leos_r_the_same made the category-label complaint in everyone keeps confusing "AI research agent" with ChatGPT for papers (23 points, 13 comments). The post says a real research agent has to decompose the question, map the citation graph, compare contradictory work, and structure experiments, while u/RangerOne122 (score 5) said the key value would be reducing the time spent deciding what to do after reading.
The model-choice thread carried the same anti-slogan instinct. In Thinking of switching from ChatGPT to Claude (27 points, 38 comments), u/Fawad-Khan-413 (score 2) said not to switch on reputation alone and to test both tools on actual weekly work. u/LowDistribution3995 (score 8) said an Opus run had spent 12 hours and more than 1 million tokens without finishing, which turned a brand preference question into an outcome-and-cost question instead.
Discussion insight: Readers are asking for falsifiable definitions: what exactly was measured, what the tool actually did, and whether the evidence unit means what the headline says it means.
Comparison to prior day: August 19 already showed backlash against bot promotion. August 22 widened that skepticism to benchmark claims and category labels themselves.
2. What Frustrates People¶
Controls that disappear at execution time¶
High severity. Where should an AI agent's permissions actually be enforced? (9 points, 10 comments), any way to stop an agent from buying from the wrong merchant? (18 points, 20 comments), and I think we're underestimating how much control coding agents actually need (7 points, 24 comments) all describe the same frustration: permission logic that lives in prompts or goodwill instead of in a boundary the model cannot cross. u/vgmartinez (score 2) said target-system auth and a proxy are what hold up in production; u/AnyCow4167 (score 5) said merchant restrictions plus one-time cards are safer than trusting the agent to choose the right seller; u/Several_Guarantee530 (score 1) said dependencies and security-sensitive changes should be flagged instead of silently applied. People are coping with repo rules, allow-lists, one-action tokens, and human approval layers, which makes this a direct build opportunity rather than an abstract governance complaint.
Loops, stale memory, and late feedback that only show up after the spend¶
High severity. How do you handle insane token costs when letting agents run autonomously? (15 points, 16 comments), Local memory for AI (13 points, 16 comments), and I let a multi-agent team build something for five days. It refused to call the result finished (2 points, 11 comments) all show systems that can look active while getting less trustworthy. u/KrstABot (score 3) relies on hard daily budgets and subagent call limits; u/Icy_Comfort_6220 (score 1) said contradictory instructions caused a polite loop that cost about $50 overnight; u/Rhishi99 (score 3) warned that portable memory needs decay scoring and a human trash bin so stale facts do not come back as authority; u/fn7Helix (score 3) said the multi-agent runtime’s bigger problem was feedback arriving too late. Teams are coping with hard caps, checkpoint files, delayed human review, and append-only activity logs, which makes the operational pain both severe and recurring.
Fragile external surfaces: channels, APIs, and callers that change the ground truth¶
Medium to High severity. Meta restricted my WhatsApp API number three days before a demo. Here's what I did instead of panicking. (4 points, 9 comments), Semrush starts at $139 a month. I built a free template that logs weekly Bing keyword rankings and the movement since last week into a Google Sheet (10 points, 6 comments), and What if the caller changes their answer? (23 points, 13 comments) all show automation breaking because an outside surface changed. u/Ahmiii_83 had to swap a WhatsApp receptionist to an n8n Chat Trigger because the business number was restricted. u/ApifyEnthusiast1 said the Bing tracker exists partly because Microsoft retired the official Bing Search API in 2025. In the caller-correction thread, u/Several_Guarantee530 (score 1) said many agents pass immediate recall tests but silently revert after a few unrelated turns. Builders are coping with channel swaps, Sheets as fallback state, and extra confirmation checks, so this looks like a competitive opportunity for more resilient interface layers.
Low-trust information environments¶
Medium severity, but widespread. Half the posts here read like they were written by a clanker (34 points, 44 comments) and 75x the PR throughput of Google AX? That sounds wild. (22 points, 16 comments) show frustration with signal pollution at two layers: synthetic posting style and synthetic-sounding metrics. u/Horror_Recover9907 (score 5) said the “paragraph symmetry” is what gives spammy AI posts away, while u/Adventurous_Youth376 (score 2) said the 75x PR figure “always smells like someone cherry picked the window.” People cope by distrusting claims until the measurement, scope, and raw evidence are visible. That makes this less of a single product gap than a constant tax on every conversation and benchmark.
3. What People Wish Existed¶
Portable shared memory across tools and machines¶
The clearest practical need was not “more memory” in the abstract. It was portable project memory that survives switching between tools without replaying the whole context every time. In Local memory for AI (13 points, 16 comments), u/Rudy_PH explicitly wanted Claude Code and other CLIs to continue with the same project state and persona. u/Rhishi99 (score 3) said the missing piece is a local SQLite store with a tiny MCP shim, decay scoring for forgetting, and secrets access through the OS keychain rather than plaintext. u/chase9527mmm (score 2) said the real value would be switching from Claude Code to Codex without re-explaining the project. Opportunity: Direct.
Evaluation suites for corrections, escalations, and side effects¶
People repeatedly asked for a reusable way to test what happens when the user changes the facts, the caller gets upset, or the tool call can actually do damage. In What if the caller changes their answer? (23 points, 13 comments), u/Exact-Film-7023 wanted a way to verify that corrections propagate through the rest of a workflow, not just the next turn. In Does an ai receptionist actually know when to escalate a call to a real person (16 points, 8 comments), u/Rosie_grac (score 2) said vendors should be forced to provide a sandbox number that prospects can stress with interruptions, accents, and fake emergencies. In Agency folks: how do you test an AI agent before handing it to a client? (8 points, 15 comments), u/Dull-Way-209 (score 4) said they keep a Braintrust handoff suite for side-effectful tool calls and permission boundaries, while u/noblequill56 (score 1) described a sandbox mode that logs external actions without executing them. Opportunity: Direct.
Research agents that hold the whole workflow, not just the summary¶
The day’s strongest “wish this existed” thread rejected the current labeling entirely. In everyone keeps confusing "AI research agent" with ChatGPT for papers (23 points, 13 comments), u/we_leos_r_the_same argued that real research work means decomposing the question, reading dozens of papers, mapping the citation network, catching invalid assumptions, and helping structure experiments and statistical tests. u/RangerOne122 (score 5) said the real time saver would be reducing the time spent deciding what to do after reading. That makes this less of a casual feature request and more of a demand for a different product category. Opportunity: Competitive to aspirational.
Semantic UI and channel abstraction that survives drift and platform bans¶
Two threads asked for interfaces that do not collapse when the outside surface changes. In Looking for an AI agent / tool that records screen workflows and replays them dynamically (7 points, 11 comments), u/sanjusmart wanted demonstration-based automation that can recover when buttons move. u/Jolly-Ad-Woi (score 1) said DOM or accessibility selectors should be first choice, with vision or OCR only as fallback, and u/joaop_2004 (score 1) said each step needs a precondition and observable postcondition rather than a replayed click. In Meta restricted my WhatsApp API number three days before a demo (4 points, 9 comments), u/Ahmiii_83 rebuilt the front door as an n8n chat widget while keeping the same booking workflow underneath. Opportunity: Competitive.
4. Tools and Methods in Use¶
| Tool | Category | Sentiment | Strengths | Limitations |
|---|---|---|---|---|
| AGENTS.md / repo rule files | Governance | (+) | Encodes test commands, project structure, PR norms, and no-go zones close to the code | Contradictions, overlong files, and purely textual rules can still create loops or be skipped |
| n8n | Orchestration | (+/-) | Gives execution history, sub-workflows, approval points, and fast publishing of reusable templates | Giant canvases get hard to debug; retries and iteration caps still need deterministic tuning |
| MCP | Tool integration | (+/-) | Lets builders expose tools once and reuse them across CLIs, gateways, and local memory layers | Does not solve authorization by itself; adds another layer to secure and debug |
| Hermes | Agent framework / memory | (+/-) | Attractive for isolation and long-term memory in multi-agent setups | Several builders said it is overkill before one plain workflow is proven |
| Claude / Claude Code / Opus | LLM / coding assistant | (+/-) | Still praised for long-form writing and hard reasoning | Multiple users reported regressions, runaway sessions, or the model “correcting” briefs they wanted followed exactly |
| ChatGPT / Codex / Sol 5.6 | LLM / coding assistant | (+) | Seen as broader on everyday workflows, research, voice, images, and tool ecosystem | People still recommend benchmarking it against real tasks rather than trusting reputation alone |
| SQLite / Postgres / pgvector | State and memory stores | (+) | Simple, inspectable persistence layers for memory, audit logs, and output metadata | Sync conflicts, stale recall, and authoritative-version questions remain unresolved |
| Google Sheets | Operational datastore | (+) | Cheap, visible, and already familiar to small teams; works well for append-only histories and deadline tracking | Often becomes the fallback source of truth because upstream systems are brittle or inaccessible |
| TrustGate / external policy gateways | Security / control plane | (+) | Centralizes auth, policy, rate limits, and MCP aggregation outside the runtime | Extra infrastructure to run; does not remove the need for target-system permissions |
| Apify Bing Search actor | Data collection API | (+) | Replaces a retired first-party Bing API and keeps weekly rank tracking cheap | External dependency, query-specific organic depth, and still no full SEO suite |
The satisfaction spectrum stayed mixed for models and more positive for infrastructure that makes state visible. In Thinking of switching from ChatGPT to Claude (27 points, 38 comments), u/Fawad-Khan-413 (score 2) said Claude seems stronger for long-form writing and large codebases while ChatGPT feels broader on research, voice, images, and everyday workflows. But u/LowDistribution3995 (score 8) said an Opus run spent 12 hours and over 1 million tokens on an unfinished task, which is why the thread kept returning to outcome-based testing rather than brand preference.
The common workaround pattern was to keep the fuzzy part narrow and push everything else into deterministic infrastructure. Building an Autonomous Multi-Agent System (Hermes + MCP + n8n): Where should I start? (41 points, 14 comments) recommended plain n8n, tool-call caps, and per-team execution records before adding more framework layers. Building AI agents for small businesses taught me the "AI" is the easy part (14 points, 5 comments) described a split stack where Opus handles genuinely hard reasoning while GLM-5.3 drags long context and caching through the loop.
Migration patterns were also clear. Rules are moving from prompts into repo files, linters, and gateways; memory is moving from chat-only context into SQLite, Postgres, and explicit artifact stores; and workflow builders are increasingly routing through Sheets, queues, and approval layers rather than trusting a single model or channel to stay stable. Competitive dynamics therefore look less like “which frontier model wins” and more like “which stack makes failures cheaper to detect and recover from.”
5. What People Are Building¶
| Project | Who built it | What it does | Problem it solves | Stack | Stage | Links |
|---|---|---|---|---|---|---|
| OpenShorts content machine | u/mutonbini | Continuously pulls a YouTube channel, generates clips, asks for approval in Telegram, then schedules them to social platforms | Replaces manual short-form clipping and approval-heavy posting workflows | OpenShorts, n8n, Telegram, TikTok/Instagram/YouTube publishing | Shipped | workflow JSON, OpenShorts |
| Contract renewal tracker | u/easybits_ai | Watches a Drive folder, classifies contracts, extracts renewal fields, computes deadlines, and appends them to Sheets | Prevents missed cancellation windows and scattered contract tracking | n8n, easybits Extractor, Google Drive, Google Sheets | Shipped | workflow, repo |
| Bing movement tracker | u/ApifyEnthusiast1 | Logs weekly Bing rankings and movement deltas into a single sheet | Gives small clients owned Bing visibility without a Semrush seat or first-party Bing API | n8n, Apify Bing Search actor, Google Sheets | Shipped | workflow |
| Cairn | u/No_Departure_9908 | Runs a public autonomous agent with a journal, paid questions, email, and a co-signed treasury | Shows how to expose agent behavior publicly without granting unilateral spend authority | Claude Fable 5, Claude Code, small server, Solana 2-of-2 multisig | Beta | post, about |
| Local memory tool | u/Rudy_PH | Stores portable project memory so different CLIs can continue with the same state and persona | Removes repeated context handoff when switching tools and lets agents use secrets without seeing plaintext | VS Code, Claude Code, local memory layer; commenters proposed SQLite + MCP + OS keychain | Alpha | post |
| oh-my-subagents runtime demo | u/lochid_om | Runs persistent role-based subagents with managed commands, event history, and blocked-state visibility | Preserves long-running work and refuses fake success when final verification fails | Persistent multi-agent runtime, managed build/test commands, activity log | Alpha | post |
The strongest shipped pattern was “boring operations wrapped around one fuzzy step.” In I have created a workflow that creates viral clips from YouTube videos using an open-source alternative API to OpusClip (22 points, 2 comments), u/mutonbini used AI for clip generation, but the durable product is the content machine around it: RSS ingest, job status, Telegram approval, social scheduling, and weekly analytics. The linked OpenShorts README says the same platform can run self-hosted or hosted, exposes an MCP server, and supports one-click publishing across short-form channels.
The contract and SEO workflows followed the same pattern. Classify contracts and track renewals in n8n (17 points, 6 comments) exists because a friend was hit with roughly EUR2,000 in auto-renewal costs; the linked workflow page shows one extraction call for classification plus field capture, then deterministic date arithmetic in n8n before append-only sheet writes. Semrush starts at $139 a month. I built a free template that logs weekly Bing keyword rankings and the movement since last week into a Google Sheet (10 points, 6 comments) does the same for SEO operations: the template reads last week’s rows back out of the same sheet before the next search so each row includes movement, not just position.
The more agent-native projects still centered observability and spend control. Cairn’s about page and autonomy map publish the exact split between what the agent can do alone and what requires a human co-signature. The local-memory thread and the oh-my-subagents demo point in the same direction from a different angle: persistence, event history, and secrets mediation are becoming products in their own right, not just plumbing behind the “real” agent.
Repeated build patterns were consistent across all six rows: append-only histories, narrow interfaces, visible approval points, and a bias toward substituting owned state for rented dashboards. Even when the poster called the system “autonomous,” the shipped shape was still mostly deterministic software surrounding a small model-shaped gap.
6. New and Notable¶
A public checklist for agent-fleet inventory¶
u/rio_ARC compressed the fleet-governance problem into nine answerable questions in I tried making a “minimum inventory” for an AI agent fleet — what am I missing? (3 points, 1 comment). The image is notable because it treats agent sprawl as an inventory problem first: ownership, purpose, model, permissions, environment, cost, version, evaluation, and audit trail. That lines up closely with the rest of the day’s discussions, which kept moving governance away from prompt wording and toward operational records.
Verifiable autonomy with a public boundary map¶
Cairn stood out because the autonomy claim is unusually inspectable. The Reddit post says the agent has a wallet, domain, email, and public journal, and the linked about page and autonomy page specify the exact split between solo agent actions and co-signed treasury actions. The notable signal is not “an agent has a wallet.” It is that the operator published the custody model, checkable addresses, and the rules under which the agent is allowed to act. (post)
Benchmark claims are getting accompanied by their own caveats¶
The 75x Kungfu-versus-AX thread was notable not because the number ended the debate, but because the linked methodology page already included many of the objections readers would raise: merged PRs are not feature or value units, scopes differ, Google’s non-public work is out of scope, and workflow discipline varies. That self-auditing tone matches the broader evidence standard showing up across the subreddit: claims are more likely to survive if the caveats are published next to the headline. (post, methodology)
7. Where the Opportunities Are¶
[+++] Cross-runtime policy and approval infrastructure — Evidence came from the AGENTS.md study, the permissions-enforcement threads, the merchant-controls discussion, and the coding-agent control thread. The repeated pain is not theoretical governance; it is figuring out where enforcement lives when the same agent touches GitHub, MCP tools, payments, and internal APIs. This looks strong because teams are already hand-building allow-lists, gateway proxies, repo rules, and co-signer flows instead of finding one trusted layer.
[++] Portable state, memory, and evaluation layers — The local-memory thread, the output-storage question, the blocked multi-agent runtime, and the handoff-testing thread all point to the same missing surface: a durable state layer that keeps context portable, stale facts suppressible, and side effects testable before they go live. This is moderate rather than maximal because the product boundary is still split across memory, logs, and eval tooling, but the need is concrete.
[+] Vertical workflow kits with swappable front doors — The contract-renewal tracker, Bing movement sheet, OpenShorts content machine, and WhatsApp fallback story all show builders shipping value by wrapping one narrow AI step in a deterministic operational shell. This looks emerging rather than mature because each kit is still channel- and niche-specific, but the economics are already understandable to buyers.
8. Takeaways¶
- The control plane is moving outside the model. The day’s strongest threads agreed that prompts are not enough for permissions, spend, or codebase boundaries; those controls are being pushed into repo rules, gateways, IAM, and card allow-lists. (AGENTS.md study, permissions thread, merchant-controls thread)
- Builders trust systems that surface blocked state more than systems that promise autonomy. The multi-agent runtime post, the Cairn experiment, and the small-business deployment thread all favored explicit limits, public rules, and recoverable logs over silent success claims. (blocked-runtime post, Cairn about page, small-business thread)
- The things shipping are mostly narrow workflows with deterministic shells. OpenShorts, the contract-renewal pipeline, and the Bing tracker all wrap one or two AI steps in queues, schedules, approval gates, and append-only sheets. (OpenShorts workflow, contract-renewal workflow, Bing tracker)
- Portable memory and evaluation remain open gaps. People want shared context across tools, better forgetting, real handoff tests, and correction-aware evals, but most of the day’s solutions were still sketches, comments, or internal harnesses. (local memory thread, caller-correction thread, pre-handoff testing thread)
- Community tolerance for vague claims is falling. Readers pushed back on AI-shaped posting style, vague “research agent” labels, and benchmark headlines that did not explain their units or scope. (clanker thread, research-agent thread, 75x throughput thread)