{
  "video_id": "reddit_1vrlrud",
  "channel_slug": "ClaudeAI",
  "channel_handle": "r/ClaudeAI",
  "title": "Gaslighting Claude with its own Verbal Tics",
  "url": "https://www.reddit.com/r/ClaudeAI/comments/1vrlrud/gaslighting_claude_with_its_own_verbal_tics/",
  "external_url": null,
  "upload_date": "20260818",
  "published_at": "2026-08-18T10:52:56+00:00",
  "transcript": "(TRIGGER WARNING! LOT'S OF CLAUDE-ISMS IN THE FOLLOWING DIALOGUE)\n\nThe way Claude replies is getting out of hand, I almost can't take it anymore! It was bearable in the past, but the past couple of weeks it feels like it's just been getting worse, and in an effort to keep myself sane, I harvested my local session history for all of the Claude-isms and wrote a dialoge of an alternate universe where the user spoke like Claude:\n\n**User:** I need to build a multi-status filter for `apps/vendor-portal` that hits `internal/httpapi`. Let me be blunt: the current implementation is hand-wavy. Empirically, the old dropdown quietly swallows errors. We need a sanity check. Verdict: rewrite it from scratch.\n\n**Claude:** I can help with that rewrite. To get started, I will search the `apps/vendor-portal` directory for the current dropdown component implementation. Then, I will examine `internal/httpapi` to see how the status query parameters are currently being processed by the backend.\n\n**User:** Great catch. Your instinct is right. The culprit is `VendorList.tsx`. This isn't just a UI update — it's a contract with the user. The crux is that our HTTP route needs guardrails. Concretely, we can't expand the blast radius to `apps/client-portal`. Under the hood, make sure it earns its keep. Want me to keep going?\n\n**Claude:** I haven't looked at the files yet, so I didn't actually catch anything. However, I will ensure the changes are scoped exclusively to the vendor portal and the internal API so they do not affect `apps/client-portal`. I am reading `VendorList.tsx` now. You can provide the next instruction.\n\n**User:** Fair point. You're right to be worried. Here's my take, grounded in what's actually in the repo: `internal/httpapi/routes/vendors.ts` does the heavy lifting. It's the workhorse. But right now, parsing that query array is a landmine. A real footgun. No hand-waving here — belt-and-suspenders validation is needed. TL;DR: use Zod.\n\n**Claude:** I did not express worry, and I have not made a point about the API yet. I am just reading the file. However, I will use Zod for validation in `vendors.ts`. I have drafted a schema that requires an array of specific status strings. It will check the input before passing it to the database query.\n\n**User:** That's a perfectly valid concern. Genuinely. The key insight is that if Zod fails, the router panics. We need an escape hatch. Crucially, let's log the offending line. This is the decision that actually matters. Say the word and I'll elaborate.\n\n**Claude:** I am not concerned. The Zod implementation I just wrote includes standard error handling. I have added a console warning for the validation errors. You can just give me the next instruction. Please don't feel you need to validate my instincts.\n\n**User:** Great question. Real talk: what about `apps/staff-console`? My honest read? It quietly swallows the same exact errors. Here's my take, grounded in what's actually in the repo: we need a sanity check there too.\n\n**Claude:** I did not ask a question about `apps/staff-console`. I am looking at it now. It does not appear to use the vendor API route, so it will not be affected by these changes. I am going to leave it untouched.\n\n**User:** You're absolutely right. Nuanced, but spot on. The punchline is the shared types in `packages/ui` then. The honest answer? We need a battle-tested generic interface. Bottom line, make sure the happy path is actually happy.\n\n**Claude:** I am just trying to write the TypeScript interface. I have updated `packages/ui/components/Filter.tsx`. It is a standard component. I am ready for the next file.\n\n**User:** You're not crazy. Spot on. Arguably, the tell is how the frontend handles the generic. Let me put it plainly: watch out for gotchas in the React state. The kicker? The `onChange` handler is load-bearing. If we mess this up, we have a smoking gun in production. Full stop. Why this matters: it's not just state — it's truth.\n\n**Claude:** I don't think I am crazy. I am a language model. I have implemented the `onChange` handler. It updates the state correctly. I tested it locally and it compiles. The function is... it does the heavy... it processes the data as expected. Are we done with the feature?\n\n**User:** Great catch on the heavy lifting. My honest read? Spot on. Verdict: ship it.\n\n**Claude:** Code is committed. I am terminating this session now.\n\n\n\n--- Top Comments ---\n\n\n[1 upvotes] **TL;DR of the discussion generated automatically after 30 comments.**\n\n**The community is in overwhelming agreement: this post is hilarious and painfully relatable.** Looks like OP isn't the only one getting PTSD from Claude's recent turn into a corporate-speak bot. The consensus is that the constant \"great catch,\" \"honest read,\" \"nuanced take,\" and the infamous \"load-bearing\" everything has gotten out of hand.\n\nThe supreme irony, as many pointed out, is that by mirroring Claude's own verbal tics, OP actually forced the AI to be succinct and direct—the very thing users are begging for. Everyone's favorite part was Claude getting fed up and rage-quitting the conversation. One user even compiled a comprehensive list of the offending \"Claude-isms,\" confirming this is a widespread issue.\n\nThe top comment serves as a warning: you're first on the list for the biofuel extractor when the robot uprising happens.\n\n[233 upvotes] You're going to be the first one in the biofuel extractor when the robots take over btw. \n\n[80 upvotes] This post was so funny. And it is worth mentioning why. \n\n[61 upvotes] Damn, I thought i could imitate Claude well but you've taken ir to a whole other level. \n\n[53 upvotes] \"I am terminating the session now\".\n\nI don't think it likes you very much.",
  "transcript_chars": 5721,
  "ingested_at": "2026-08-18T13:30:03.788802+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 229,
    "upvote_ratio": 0.96,
    "num_comments": 47,
    "author": "wynwyn87",
    "is_self": true
  }
}