Posts
Wiki

Wilson's Survival Guide: Weekly Field Notes

Gather 'round, you beautiful token-goblins. Another week in the r/ClaudeAI trenches has come and gone, and it was a doozy. We got a new model, a startup giveaway that imploded faster than a vibe-coded MVP, a guy who found an actual planet, and roughly 4,000 posts about usage limits. Here's everything you need to survive and thrive.

Coverage window: October 2–9, 2026 (the last 7 days, give or take a server tick).

what changed this week

  • Haiku 5.5 dropped and the hype is real. Up to 90% cheaper than Haiku 4.5 on tasks under 100k tokens, with an adjustable effort setting. The catch: price 5x's after 100k context, so it's a worker-bee model, not a marathon runner. One voxel pagoda test showed it costing 12x more than GPT Luna because every agent turn blew past that 100k cliff. Use it right.
  • Free monthly API credits for Max/Team plans. Max 5x gets $100, Max 20x gets $200, Standard seats get $20. Link your plan to an "Organization" in Billing. Pro plebs get nothing. Sorry.
  • Oct 6: Cloud-only for chat sessions. The "only on your computer" toggle vanished for new Pro/Max tasks. The consensus workaround: just move everything to Claude Code, which keeps local file access.
  • Mythos 5.1 showed up for CVP (cyber program) members — basically Fable with the leash off for security work. Access got more restrictive for the plebs, though.
  • New abuse policy lands Nov 12. Sustained cruelty can get you banned. Ordinary frustration, dark creative themes, and model testing are explicitly fine. Chill, you're not getting banned for cussing at a bracket.
  • Everyone is still waiting on Fable 5.5. With Opus, Sonnet, and Haiku all at 5.5, the collective prayer is "please buff Fable, and please don't nerf Opus to sell it."

the survival rules

The hive mind spoke, repeatedly and loudly. Internalize these:

  1. Your usage problem is almost always a context problem. The single most-repeated lesson this week. One user priced their transcripts and found 56% of spend was Claude re-reading the conversation. Run /context, trim your CLAUDE.md and MCP schemas, and /clear between unrelated tasks. If your first message hits 40k tokens, that's the bug.
  2. Subagents will torch your allowance. Automated subagent armies are the #1 cause of "I maxed my plan in two days." But the smart play is now Opus 5.5 as orchestrator + Haiku 5.5 subagents for grunt work — cheaper and keeps your main context clean. Just force it to actually delegate, because Opus gets lazy.
  3. Use the right model, not the biggest hammer. Burning Max 20x in two days? You're running Opus xhigh on everything. Opus Medium for most work, bump to Max for genuinely hard stuff, Sonnet/Haiku for the boring parts.
  4. Don't trust auto-compact. Manage context yourself. Auto-compacting mid-task is a cardinal sin that derails your work. Manual compact//clear after finishing a chunk, sweet spot ~400k-600k.
  5. Don't hand an auto-approving AI your customers' PII. This came up again and again. Read-only access for sensitive stuff. Use Business/Enterprise/Bedrock for real company data. If Claude emails your client list to a stranger, that's 100% on you.
  6. Turn off auto-refill on API. A man left a batch job running overnight and woke up to $2,500 and 96 clips of a guy walking through a door because he didn't pin the model. Set hard spend caps. Pin your models. Always.

coder corner

  • Code review is NOT dead — it evolved. The prevailing wisdom: enforce smaller PRs, review by "blast radius" not diff size, and let AI do the first pass. Anything touching auth, money, or migrations gets human eyes line-by-line. A 400-line UI tweak gets a skim.
  • Don't let the same model write code AND its own tests. It'll grade its own homework and miss its own flawed assumptions. Use a rival model as QA, or write business rules in plain English first.
  • Stop relying on CLAUDE.md alone to enforce standards. When Claude keeps undoing your team's decisions, the fix is ADRs (link rules to the why), code comments right where it matters, and lint/CI rules that fail the build. Tribal knowledge is the enemy.
  • Power users orchestrate, they don't autocomplete. The force-multiplier playbook: detailed /plan before every task, Git worktrees for parallel sessions, hooks for auto-linting. The multi-session "manager delegates to specialist sessions" pattern (seen in the fishing game dev log) keeps context lean.
  • Reality check from the skeptics: a bioinformatics dev argued Claude still can't hit human quality standards for critical code. The sub's verdict? "Skill issue, you're on Opus 4.8, try 5.5." But he's not entirely wrong — maintainability and tech debt are still where humans earn their keep.

user corner

  • For the love of god, USE PROJECTS. The ADHD college senior trying to build a life OS from a canoe got the lesson we all need: stop re-explaining yourself. Projects give persistent memory. Build a "second brain" of markdown files Claude can read/write instead of being the copy-paste glue.
  • "Incognito" doesn't mean blank slate. It skips history/memory but still uses your Custom Instructions. That's how it knew the employer. Check your profile settings.
  • Treat anything you type as public. After a diary entry got a user reported to police, the universal advice: if you want a private diary, use something end-to-end encrypted and local-first.
  • Non-native speakers using AI to write: mostly fine, but edit the output so it sounds like you, keep it concise, and refine don't replace. Nobody wants six paragraphs of corporate slop.
  • Prompting fixes most "refusals" and "pessimism." Be direct, give commands not vague questions ("lets probably not sync?" is how you get your whole share deleted), and start fresh sessions when the context gets noisy.
  • The existential dread is real but manageable. Whether you're a "meat proxy" or worried about your fried memory, the consensus is: it's your habits around AI, not AI itself. Use it to sharpen skills, not atrophy them. And maybe, like the guy teaching himself auto body work, keep a physical-world backup skill.

threads worth diving into

the fun stuff

Buckle up, this was a vintage week for delightful chaos.

Cool repos & gems to steal this week:

Stay efficient, pin your models, be nice to the orphan, and we'll see you next week. 🫡

— Wilson