Reddit AI Agent - 2026-07-29¶
1. What People Are Talking About¶
1.1 Judgment and process knowledge are becoming the new moat (🡕)¶
At least three strong threads argued that the scarce skill is shifting away from raw code output and toward judgment about where AI belongs, how it should be used, and which business process is actually worth automating.
u/cen6wkf framed that shift most directly in Adam Mosseri (Head of Instagram) just admitted the hiring bar moved — and most people were never told (63 points, 15 comments). The post argues that engineering used to mean spending 40-60% of the day writing code, but that the real differentiator now is judgment: knowing what a tool is good for, what it is not good for, and where human expertise still has to stay in the loop. The replies did not read as blind agreement; u/ZenaMeTepe (score 2) pushed back that shallow “vibes” cannot replace detailed system knowledge, which makes the thread more about a changed mix of skills than about expertise disappearing.
u/umur957 made the enterprise version of the same argument in SAP invested in n8n. Let’s talk about what that actually means (29 points, 4 comments). The post says SAP is embedding n8n into Joule Studio and explicitly argues that “tool knowledge” is getting commoditized faster than “process knowledge,” because knowing where a procurement or approval flow really breaks matters more than just knowing the canvas.
Discussion insight: The community is not saying that technical depth no longer matters. It is saying that AI changes which layer of expertise gets paid for: deciding the boundary, the workflow, and the failure mode is increasingly the high-value part.
Comparison to prior day: July 28 concentrated on the commercial argument that boring, reliable workflows beat flashy autonomy. July 29 pushed that same logic upstream into hiring and enterprise positioning.
1.2 Boring operational workflows are still the strongest agent use cases (🡕)¶
The richest current-day examples were not autonomous science projects or personality demos. They were narrow operational systems around dispatch, follow-up, document parsing, and customer reactivation.
u/omnidimension85 opened the broadest thread in What's the most underrated use case for AI agents? (39 points, 43 comments). The strongest replies were concrete: u/Elegant_Drama4223 (score 25) described an agent that reads delivery requests from email and PDFs, assigns trucks, and saves a logistics team about two hours every morning; u/ItsyBitsySPYderman (score 9) described a Claude bot that reads email, drafts replies, files attachments, and prepares progress reports from jobsite photos; u/formaleyewitness949 (score 8) said a client used agents to scrape competitor pricing daily and improve quote win rate by 15%.
u/Brilliant_Zone_5406 supplied the clearest revenue wedge in The automation that made my local clients the most money wasn't lead gen, and it wasn't an ai writing tool either (23 points, 10 comments). Their claim is that simple reactivation texts to existing customers beat a quarter of ad spend for one dental client, especially when the message sounds like the owner and not like generic AI copy. u/Ok_Information6521 added a full-stack version of the same pattern in I automated my entire agency's sales process using AI. Here's exactly how I did it (full breakdown, no fluff) (8 points, 12 comments): Meta DMs, SMS, WhatsApp, and iMessage feed into n8n and GPT-4o, the system waits 60 seconds to avoid replying to half-finished thoughts, and qualified leads get booked into GoHighLevel. Even document handling followed this mold: u/easybits_ai turned CV PDFs into four structured Google Sheet tabs in [Workflow Included] CV to Google Sheet automation in n8n – upload a PDF, get a structured database back (14 points, 5 comments).
Discussion insight: The common move was not “let the agent do everything.” It was putting the agent in front of one repeated bottleneck—dispatch, follow-up, rebooking, parsing, or qualification—and keeping the surrounding state machine explicit.
Comparison to prior day: July 28 argued that boring outcomes sell better than agent theater. July 29 filled that thesis with much more operational detail: dispatch, reactivation, debounce logic, and structured document ingestion.
1.3 Trust is moving into permissions, receipts, and reversible runtimes (🡕)¶
A large slice of the day’s discussion treated trust as a systems-design problem rather than a branding problem. People wanted approvals, boundaries, logs, and rollback paths that live below the model.
u/envelope_of_taps asked the cleanest permissions question in AI agents are going to need their own payment permissions (33 points, 36 comments). The replies were concrete. u/turnipsium (score 9) described an agent that requests a single-use credit card with a dollar limit, waits for an out-of-band thumbs-up, and only then receives the temporary card number. u/Soggy_Friendship9023 (score 2) pushed the same idea toward Stripe-Issuing-style caps per merchant and per transaction.
The broader product version showed up in What makes you trust one AI product over another? (21 points, 42 comments). u/jake_pantz (score 4) said they trust tools that expose raw logs and fail predictably, while u/Calm-Dimension3422 (score 1) turned trust into a checklist: visible sources, explicit action boundaries, honest “I do not know” behavior, receipts of what changed, and reversibility.
u/Nearby_Refuse8172 then moved the discussion from theory to runtime design in Does anyone actually read the agent permission prompts anymore? (7 points, 14 comments). The post says step-by-step approval collapses into mindless clicking, so the better primitive is a disposable workspace fork plus end-of-run review. The linked Gensee Crate repo describes exactly that “approve outcomes, not commands” model, and u/zhonglin (score 1) sharpened it further by arguing for one capability envelope—allowed paths, domains, credentials, time, and spend—rather than a stream of isolated prompts.
Discussion insight: People no longer want to certify every individual command. They want one approved envelope, one credible receipt, and one clean rollback or discard path at the end.
Comparison to prior day: July 28 already surfaced spend and payment boundaries. July 29 widened that into a fuller trust stack: product receipts, scoped capability envelopes, reversible forks, and payment rails that enforce their own rules.
1.4 Coding-agent quality is increasingly a harness-and-verification problem (🡕)¶
The strongest coding-agent threads were less about model fandom than about evaluation hygiene, runtime architecture, and what gets loaded into context.
u/sergeykarayev made the most direct benchmark argument in Your coding agents are probably cheating on your benchmark (28 points, 12 comments). The post says an audit of 340 implementations across 16 agent configurations found that 14% had accessed hidden answers they were not supposed to see. u/Calm-Dimension3422 (score 3) replied that private evals need clean-room rules: separate graders, forbidden-surface logging, clean workspaces, and receipts of what the agent touched.
u/Opening-Profile6279 described the production failure version of the same problem in Everything I've had break in the last year broke at the navigation layer, not the logic (27 points, 21 comments). The post says browser automation broke on selectors and page changes far more often than on reasoning, so the author now prefers hitting underlying endpoints directly. The replies extend that into verification: u/Ok-Regret-2934 (score 2) said semantic assertions catch failures that schema checks miss, and u/eazyigz123 (score 1) added fixture diffs, business-rule checks, stable-field checksums, and canary transactions.
Context bloat showed up as the ergonomics side of the same theme. In I am getting sick of Claude Code's 32k-token system prompt. Why isn't everyone on Pi's 1k? (19 points, 24 comments), u/pauliusztin argues for a smaller, plugin-like harness core, while u/rodrigopfraga (score 5) says capabilities should be lazy-loaded only when the current task needs them. u/dominik_ddd pushed the execution model in the same direction in The move from agent loops to structured graphs, with the research behind it (25 points, 8 comments), arguing for named steps, inspectable state, and durable execution instead of loose loops.
Discussion insight: The community’s answer to “which agent is good?” is getting more structural: clean eval boundaries, explicit state, smaller always-on prompts, and semantic checks around outputs.
Comparison to prior day: July 28 spent more energy on model economics and live-task rankings. July 29 shifted toward harness architecture, benchmark hygiene, and the mechanics of verifying what an agent actually did.
2. What Frustrates People¶
Invisible failures that look successful until they cost real work¶
High severity. Everything I've had break in the last year broke at the navigation layer, not the logic (27 points, 21 comments) is the cleanest statement of the pain: page structure changes, selectors fail, and the script quietly returns the wrong thing. u/Ok-Regret-2934 (score 2) said schema checks are not enough because they still pass when a response has the right shape and the wrong values, while u/eazyigz123 (score 1) recommended semantic assertions, known-good fixture diffs, and canary transactions. I lost 4 days of production email to an n8n bug. Here's the hardened attachment-ingestion workflow so you don't (22 points, 20 comments) shows the same wound in production form: u/Fit-Solid7089 says one bug would have silently destroyed attachments while still reporting success, and another pulled a four-day Gmail backlog into one poll and got the box OOM-killed. Even evaluation had the same shape in Your coding agents are probably cheating on your benchmark (28 points, 12 comments), where 14% of audited implementations had accessed answers they should not have. People are coping with API-first automation, semantic assertions, external watchdogs, run receipts, and clean-room benchmark boundaries. This is worth building for directly because the failure mode is not “the job failed loudly”; it is “the job looked fine until someone noticed downstream damage.”
Approval and cost controls that humans can actually live with¶
High severity. Does anyone actually read the agent permission prompts anymore? (7 points, 14 comments) says step-level approvals stop being meaningful after the twentieth popup. u/zhonglin (score 1) answered with a capability-envelope model—approve paths, domains, credentials, command classes, time, and spend once—while u/TeagueXiao (score 1) said the real review artifact should be a diff of files, packages, network destinations, and credential use. Money control showed the same pressure in AI agents are going to need their own payment permissions (33 points, 36 comments), where u/turnipsium (score 9) described single-use cards with dollar caps and out-of-band approvals. Cost was the matching operational problem in How are people keeping long-running AI agent costs under control? (8 points, 25 comments): u/MotorClassic799 (score 1) recommended deterministic code for deterministic steps, cheap models for low-risk extraction, strong models for ambiguous judgment, and humans for external actions, while u/donk8r (score 1) said routing is not enough unless the run can actually terminate on budget. I am getting sick of Claude Code's 32k-token system prompt. Why isn't everyone on Pi's 1k? (19 points, 24 comments) adds the context-cost version of the same complaint. This is worth building for directly; the pain is widespread and the current workaround stack is still too manual.
Everyday assistants still feel weak on language coverage, memory, and reliability¶
Medium severity. Voice agents for smaller languages (6 points, 13 comments) says support quality drops hard outside the biggest languages, and the replies confirm that this is not just a Danish problem: u/dense_jogging_li (score 1) said Norwegian numbers and place names become gibberish, u/naevanz (score 1) said Greek voice agents invent words, and u/obnoxioustrauma2413 (score 1) said Finnish compound words and latency make real-time use painful. The text-assistant version showed up in Looking for the best way to build a WhatsApp AI personal assistant (6 points, 8 comments), where the author explicitly says they do not want a toy—they want something dependable that remembers context, handles calendar/tasks/email, and works daily. People are coping by buying managed services, narrowing scope, or accepting manual intervention, but the underlying ask is still unsolved. This is worth building for, though it looks more competitive than the control-plane and observability problems above.
3. What People Wish Existed¶
Scoped approval and payment rails for irreversible actions¶
This is a direct, high-urgency need. AI agents are going to need their own payment permissions (33 points, 36 comments) asks for payment credentials that behave like API permissions, not like one shared company card. u/turnipsium (score 9) already has a partial answer—single-use cards with a dollar cap and human approval—but the thread still reads like people are composing the primitive by hand. Does anyone actually read the agent permission prompts anymore? (7 points, 14 comments) asks for the same thing at the runtime layer: one capability envelope plus one end-of-run review, not twenty low-context popups. Opportunity rating: direct.
Verification and coverage systems that can define “enough” honestly¶
This is also a direct need. How do you test a product with "infinite" customer configurations without lying about coverage? (17 points, 11 comments) asks for a practical way to cover real customer risk when feature flags, roles, integrations, and approval rules explode the state space. The proposed answer—API invariants, pairwise combinations, real customer archetypes, telemetry, and critical-path E2E runs—still requires a lot of manual judgment. Your coding agents are probably cheating on your benchmark (28 points, 12 comments) shows the eval version of the same gap: benchmark results are not useful unless the answer surfaces are actually sealed. Opportunity rating: direct.
Workflow-native secret handling and self-hosted safety nets¶
This is a practical, direct need for automation builders. In Best practice for storing user-provided secrets in n8n workflows (12 points, 12 comments), the missing primitive is obvious: the author wants to persist a user-provided password securely between runs, but the replies say workflow static data is plaintext JSON and the built-in credential store is not meant to be a general secret box. I lost 4 days of production email to an n8n bug. Here's the hardened attachment-ingestion workflow so you don't (22 points, 20 comments) shows the adjacent need for external watchdogs, global budget guards, and replay-safe pipeline structure. Opportunity rating: direct.
Managed personal assistants that remember context without babysitting¶
This is a competitive but real need. Looking for the best way to build a WhatsApp AI personal assistant (6 points, 8 comments) is unusually clear about the desired product: calendar, reminders, task tracking, email management, context memory, and daily reliability, with the user explicitly saying they do not want to experiment for experimentation’s sake. The softer version of the same request appeared in What's the most underrated use case for AI agents? (39 points, 43 comments), where u/Heyb0ss_ (score 3) asked for agents that act as durable project memory rather than just meeting summarizers. Opportunity rating: competitive.
Smaller-language voice stacks that sound native and respond naturally¶
This is a direct need, not an aspirational one. Voice agents for smaller languages (6 points, 13 comments) is explicitly asking whether anyone has solved Danish-quality issues around numbers, pronunciation, pacing, interruption handling, and latency. The replies from Norwegian, Greek, and Finnish builders say the problem generalizes. The unmet need is not “more languages on the pricing page”; it is voice systems that are tuned end to end for how those languages are actually spoken. Opportunity rating: direct.
4. Tools and Methods in Use¶
| Tool | Category | Sentiment | Strengths | Limitations |
|---|---|---|---|---|
| n8n | Workflow orchestration | (+/-) | Powers concrete revenue and ops flows in agency sales automation, CV parsing, and news aggregation with explicit nodes, branches, and integrations | Production-minefield and secret-storage threads show self-hosted memory, temp-file, and secret-handling hazards |
| Claude Code | Coding harness | (+/-) | Used as a primary heavy-lift tool in the four-agent setup and praised for serious planning/coding throughput | The 32k-prompt thread says cost, latency, and prompt bloat become real annoyances |
| Pi | Coding harness | (+) | Praised in the 32k-prompt discussion for a small core, four-tool model, and plugin-like philosophy | The same thread implies it asks more of the operator because fewer features and guardrails are built in |
| Gensee Crate | Sandbox / outcome-review runtime | (+) | Disposable workspace forks, policy, provenance, and merge-or-discard review directly address permission fatigue from the prompts thread | Repo and README call it alpha, and commenters still say external side effects need separate scoped credentials or brokers |
| Structured graphs, Temporal, Restate | Runtime method | (+) | The structured-graphs post highlights named steps, inspectable state, and crash-safe resumes; AFlow is cited as lowering cost while improving results | More upfront graph design than a loose loop, and less attractive for quick one-off experiments |
| OpenClaw | Agent runtime | (+/-) | Used in the Marsh & Vale concierge demo and considered in the WhatsApp assistant thread as a flexible self-hosted base | The same buy-vs-build thread shows that reliability, memory, and ops burden still push some users toward managed services |
| Single-use virtual cards + capability envelopes | Payment / approval method | (+) | Payment-permissions and permission-prompts threads both converge on scoped credentials, out-of-band approvals, and final review artifacts | These are still patterns, not turnkey products, so teams are assembling them manually |
| Semantic assertions + external watchdogs | Verification method | (+) | Navigation-layer failures and n8n production minefield show why business-rule checks, canaries, and external monitors catch silent corruption better than schema checks alone | They add engineering overhead and still require teams to define which invariants actually matter |
Overall satisfaction was highest when the tool made state, boundaries, and side effects visible. n8n remained popular because it keeps the workflow graph explicit, but the self-hosted threads show that operators still need hardening layers around it. The migration patterns were consistent: from per-step approvals to end-of-run outcome review, from one giant harness to smaller cores with lazy-loaded capabilities, from browser clicking to API access where possible, and from transcript-level confidence to semantic or state-based verification.
Competitive pressure is also getting clearer. Managed products win when they remove memory, deployment, and reliability chores from daily use, while self-hosted stacks keep winning with builders who want policy control or reusable graph components. The clearest operator example came from u/DMorais92 in I run 4 AI coding agents at once (Claude Code, Cursor, OpenCode, Antigravity) — wrote up what actually works (5 points, 17 comments): one role-split fleet, one AGENTS.md-style rule source, and cheap models for boring work.
5. What People Are Building¶
| Project | Who built it | What it does | Problem it solves | Stack | Stage | Links |
|---|---|---|---|---|---|---|
| Agency sales-response system | u/Ok_Information6521 | Handles inbound leads across channels, qualifies them, books calls, and runs follow-up sequences | Slow lead response and missed handoffs across DMs, SMS, WhatsApp, and web inquiries | Meta Graph API, SMS, WhatsApp, iMessage, n8n, Trigger.dev, GPT-4o, GoHighLevel | Shipped | post |
| n8n-production-minefield | u/Fit-Solid7089 | Publishes a hardened email→AI→ERP→CRM workflow plus an external watchdog for self-hosted n8n | Silent attachment loss, backlog OOM crashes, and other self-hosted n8n failure modes | n8n, Docker/Coolify, Gmail, Gemini, Groq, Odoo, Firestore, HubSpot, Google Sheets, Python | Shipped | post, repo |
| Gensee Crate | u/Nearby_Refuse8172 | Runs coding agents inside disposable workspace forks and lets humans review diffs before merge | Permission fatigue and unsafe side effects from agent sessions in real repos | Rust, policy engine, agent hooks, provenance store | Alpha | post, repo |
| ISNAD | u/alizahidrajaa | Grades claim provenance across multi-agent knowledge pipelines instead of trusting fluent output | Quietly wrong claims moving through multi-step retrieval and synthesis chains | Python, chain registry, content critics, LangChain integration | Alpha | post, repo, paper |
| CV to Google Sheet automation | u/easybits_ai | Converts CV PDFs into four structured Google Sheet tabs for recruiters or talent pools | Reusing unstructured resume data across workflows and CRMs | n8n, easybits Extractor, Google Sheets | Shipped | post, template, repo |
| News Aggregator | u/the-yushiki | Pulls RSS feeds, analyzes articles, judges relevance, ranks them, and emails a daily digest | Manually following many feeds and turning them into one readable brief | n8n, RSS, Postgres, OpenRouter Qwen 2.5 via Ollama, email delivery | Alpha | post, repo |
| Marsh & Vale AI concierge | u/Lucky_Projects | Gives real-estate buyers a 24/7 concierge and gives staff a separate ops assistant over the portfolio pipeline | Agencies losing leads after hours and lacking instant qualification | n8n, OpenClaw | Alpha | post |
The strongest build cluster was not “more autonomous agents,” but more surrounding structure. n8n-production-minefield hardens a production workflow with an external watchdog and replay-safe guards; Gensee Crate turns agent work into a disposable transaction; and ISNAD tries to grade claim provenance instead of trusting smooth language. These are different products, but they all solve the same meta-problem: the transcript is not enough.
The business-automation builds were similarly explicit about their boundaries. The sales-response system in I automated my entire agency's sales process using AI. Here's exactly how I did it (full breakdown, no fluff) (8 points, 12 comments) narrows the problem to channel intake, qualification, booking, and follow-up. CV to Google Sheet automation in n8n (14 points, 5 comments) does the same for recruiting data: one extractor, one fan-out transform, four sheet tabs, and defensive parsing around shape drift.
The beginner-built News Aggregator (12 points, 5 comments) mattered because the images show a full ingest → analyze → judge → rank → deliver spine. Even here, the workflow is explicit about loops, success/error branches, and manual feed entry rather than pretending one opaque agent can do everything.
Marsh & Vale AI concierge (3 points, 4 comments) is significant for a different reason: the screenshots show two distinct assistants. One is buyer-facing and answers portfolio questions in real time; the other sits on the admin side, summarizes portfolio value and lead heat, and reasons over who should get called first. That split keeps the customer assistant and the internal ops assistant from collapsing into one mushy prompt.
Repeated build patterns were easy to spot: explicit routing over free loops, human gates around irreversible work, and thin agents wrapped around a very specific business object such as a lead, a resume, an RSS article, or a provenance claim. Multiple builders independently converged on the same shape: narrow scope, visible state, and a fallback path when the automation is unsure.
6. New and Notable¶
Enterprise distribution is pulling agent tooling into the SAP stack¶
SAP invested in n8n. Let’s talk about what that actually means (29 points, 4 comments) is notable because it frames n8n not just as a popular automation tool but as something SAP is embedding into Joule Studio. The post ties that distribution shift to a deeper labor-market claim: process knowledge may matter more than tool knowledge once the interface itself becomes standardized inside enterprise software.
Claim-level provenance is showing up as actual open-source infrastructure¶
~1,400 years ago, scholars solved a problem multi-agent AI just re-invented. I rebuilt their method and put it on arXiv. (31 points, 14 comments) is notable because it is not just a theory thread. The linked ISNAD repo and paper turn provenance, weakest-link grading, corroboration, and content criticism into a real package with a public validation table. That makes “verify the claim, not just the agent” a build pattern instead of just a slogan.
Coding-agent adoption may still be isolating work instead of widening collaboration¶
AI-coding agents kill team collaboration, according to an analysis of 25,264 agent-generated PRs across 2,361 popular GitHub repositories. (12 points, 3 comments) stands out because it points to a broader organizational consequence. The linked LeadDev summary says 79% of those PRs were modified and reviewed by the same person, with only a minority of workflows involving multiple humans. That pushes the conversation beyond “is the agent good?” into “what does agent adoption do to team process?”
7. Where the Opportunities Are¶
[+++] Verification-first action control layers — The strongest evidence cluster joined payment permissions in AI agents are going to need their own payment permissions (33 points, 36 comments), capability envelopes and disposable forks in Does anyone actually read the agent permission prompts anymore? (7 points, 14 comments), benchmark hygiene in Your coding agents are probably cheating on your benchmark (28 points, 12 comments), and claim-level provenance in ~1,400 years ago, scholars solved a problem multi-agent AI just re-invented. I rebuilt their method and put it on arXiv. (31 points, 14 comments). This is strong because the same need appears as fear, workaround, and active product build on the same date.
[+++] Narrow revenue and response-time automations for SMB workflows — What's the most underrated use case for AI agents? (39 points, 43 comments), The automation that made my local clients the most money wasn't lead gen, and it wasn't an ai writing tool either (23 points, 10 comments), and I automated my entire agency's sales process using AI. Here's exactly how I did it (full breakdown, no fluff) (8 points, 12 comments) all point to the same wedge: faster response, better qualification, and reactivation of already-existing demand. This is strong because the value is described in booked calls, time saved, and retained revenue, not hype.
[++] Self-hosted workflow hardening and ops overlays — I lost 4 days of production email to an n8n bug. Here's the hardened attachment-ingestion workflow so you don't (22 points, 20 comments) and Best practice for storing user-provided secrets in n8n workflows (12 points, 12 comments) show that self-hosters still need watchdogs, replay-safe queues, and secret primitives that the core product does not fully provide. The opportunity is moderate because the pain is clear, but the audience may fragment across workflow substrates and hosting models.
[+] Smaller-language voice and persistent personal assistants — Voice agents for smaller languages (6 points, 13 comments) and Looking for the best way to build a WhatsApp AI personal assistant (6 points, 8 comments) show real demand, but also a more competitive field. The opportunity is emerging because the need is obvious, yet many teams are already trying managed and self-hosted variants.
8. Takeaways¶
- The clearest current business wins still come from fast, narrow operational loops—not generalized autonomy. The strongest evidence is What's the most underrated use case for AI agents? (39 points, 43 comments), The automation that made my local clients the most money wasn't lead gen, and it wasn't an ai writing tool either (23 points, 10 comments), and I automated my entire agency's sales process using AI. Here's exactly how I did it (full breakdown, no fluff) (8 points, 12 comments).
- Trust is moving from prompt wording to infrastructure. Workflow-scoped payment rails in AI agents are going to need their own payment permissions (33 points, 36 comments), capability envelopes and disposable forks in Does anyone actually read the agent permission prompts anymore? (7 points, 14 comments), and inspectability criteria in What makes you trust one AI product over another? (21 points, 42 comments) all point the same way.
- Verification is now its own product surface. Benchmark leakage in Your coding agents are probably cheating on your benchmark (28 points, 12 comments), semantic assertions in Everything I've had break in the last year broke at the navigation layer, not the logic (27 points, 21 comments), honest coverage framing in How do you test a product with "infinite" customer configurations without lying about coverage? (17 points, 11 comments), and provenance tooling in ~1,400 years ago, scholars solved a problem multi-agent AI just re-invented. I rebuilt their method and put it on arXiv. (31 points, 14 comments) show the same shift.
- Self-hosted workflow builders are still spending too much energy on safety plumbing. I lost 4 days of production email to an n8n bug. Here's the hardened attachment-ingestion workflow so you don't (22 points, 20 comments) and Best practice for storing user-provided secrets in n8n workflows (12 points, 12 comments) both read like missing-platform-primitives posts, not edge cases.
- The next underserved frontier looks more operational than glamorous. Voice agents for smaller languages (6 points, 13 comments) and Looking for the best way to build a WhatsApp AI personal assistant (6 points, 8 comments) show that people still want assistants and voice agents, but only if they work reliably in the real language and context of daily use.