todai
Saturday, 9 May
7 min read · 1,239 words

TODAY'S ITEMS

1. Claude Code v2.1.136 — MCP OAuth Refresh Fix, /clear Bug Resolved, Hard-Deny Auto Mode

  • Two long-standing pain points fixed: MCP servers configured in .mcp.json, plugins, and claude.ai connectors were silently vanishing after /clear in VS Code, JetBrains, and Agent SDK (now resolved), and users with multiple remote MCP servers will no longer need daily re-authentication because OAuth refresh tokens were being lost when servers refreshed concurrently. New settings.autoMode.hard_deny field lets you define classifier rules that block actions unconditionally, regardless of intent or allow exceptions — useful for enterprise deployments where certain operations must never be permitted.
  • Source: GitHub Releases
  • Why it matters: If you use remote MCP servers (GitHub, Notion, Linear, etc.), update now — the OAuth fix alone removes a daily friction point that's been open since March.
  • Verified

2. Mitchell Hashimoto: "AI Slop Is Good, Actually"

  • Mitchell Hashimoto (HashiCorp founder, Ghostty creator) posted a 129K-impression thread arguing that "slop" — fast, unpolished AI-generated output — is a legitimate professional tool when deployed correctly: overnight agent runs generating dozens of prototype plugins, slop frontends covering alpha builds, agent-generated test providers that get regenerated when the API changes. His framing: the cost of change is now tokens, not engineering hours. The constraints are "don't PR slop to other projects, don't ship to customers without review, don't accept first-pass slop as final."
  • Source: Twitter (@mitchellh)
  • Why it matters: If you're second-guessing your Claude Code workflow because output quality isn't perfect, this is the clearest articulation of why "iterate fast on imperfect output" is the right default, not a compromise.
  • Verified

3. Anthropic's financial-services Repo Keeps Growing — 14K Stars

  • anthropics/financial-services hit 14,480 total stars and 1,790 forks since launching at Code w/ Claude on Wednesday. The repo contains 10 ready-to-run Claude Code skill templates for finance workflows — pitchbook builder, KYC screener, month-end closer, financial analysis — all in markdown and YAML, designed to be forked and customised to your own branded layouts and team workflows.
  • Source: GitHub
  • Why it matters: If your team does any reporting, modelling, or client deck work, clone this repo and adapt one template this weekend — the PowerPoint/Excel agents have a /ppt-template slot specifically for your own layouts.
  • Verified

YOUR STACK — UPDATES

  • Claude Code v2.1.136: CLAUDE_CODE_SESSION_ID now passed to hook subprocess environments; CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 opts back to native terminal scrollback; MCP OAuth multi-refresh bug fixed; /clear no longer drops MCP servers in VS Code + JetBrains. Run npm update -g @anthropic-ai/claude-code | https://github.com/anthropics/claude-code/releases/tag/v2.1.136

NEW TOOL / PRODUCT SPOTLIGHT

  • obsidian-second-brain — Claude Code skill that turns your Obsidian vault into an AI-first second brain: 31 commands, auto-synthesis (every source updates existing notes instead of appending), 4 scheduled agents, live research from the web and YouTube, 4 role presets. Based on Karpathy's LLM Wiki pattern but self-rewriting — contradictions reconcile automatically. 793★ and growing. Install: npx add-skill eugeniughelbur/obsidian-second-brain | https://github.com/eugeniughelbur/obsidian-second-brain

PROMPT OF THE DAY

I'm about to start a new feature/task. Before I write
any code, I want to measure whether I actually need
cloud AI for each step or if a local model would do.

For this task: [DESCRIBE TASK]

Break it into sub-steps. For each step, predict:
1. Does this need multi-file context or complex
   reasoning? (local struggles here)
2. Is it file reads, scans, boilerplate, or test
   writing? (local handles this at 88-97%)
3. Recommend: local (e.g. Qwen 3.6 27B via Ollama)
   or cloud (Claude Opus/Sonnet)?

Then estimate my total cloud spend if I routed
correctly vs using cloud for everything.

Route your tasks before you burn tokens — a r/LocalLLaMA developer who measured 150 real tasks found 65% could run locally for electricity cost alone. Source: r/LocalLLaMA (675 upvotes) https://www.reddit.com/r/LocalLLaMA/comments/1t4s6g2/

LANDSCAPE NOTES

  • Cloudflare cutting ~20% of workforce (1,100+ jobs) — blog frames it as AI-driven efficiency, shares the load Cloudflare Agents and Workers are now absorbing. 1,185 points on HN. https://news.ycombinator.com/item?id=48054423

  • Jack Clark (Anthropic co-founder, now head of the Anthropic Institute) gave 60%+ odds this week that an AI model will fully train its successor by end of 2028. The Anthropic Institute launched in March to publish research on societal AI impact as Anthropic builds frontier models. https://www.axios.com/2026/05/07/anthropic-jack-clark-ai-intelligence-explosion

  • @alexalbert__ (Anthropic) posted "More chips, more Claude" with 45K impressions — context: the Colossus 1 data centre deal with xAI. Simon Willison's thread on the deal's environmental record (gas turbines, hospital admissions data) is worth reading before celebrating. https://simonwillison.net/

  • Kimi K2.6 on Baseten is ~5x cheaper than Opus 4.7 with similar performance on most tasks — flagged by Harrison Chase (LangChain CEO). Useful benchmark for API cost routing decisions. https://x.com/hwchase17/status/2052782874374623443

TRY THIS WEEKEND

Item 1 — Set up awslabs/aidlc-workflows in your Claude Code project (30 min)

AWS just published their AI-Driven Life Cycle steering rules — a full three-phase workflow (requirements → implementation → verification) that plugs into Claude Code as a SKILLS.md-style rule set. Download the zip from the releases page, copy aidlc-rules/ into your project's .claude/ directory per the README, and run a task you've been putting off with the structured workflow guiding Claude through it. Good way to see how a formal dev lifecycle layer changes Claude's planning behaviour versus free-form prompting.

https://github.com/awslabs/aidlc-workflows

Item 2 — Install obsidian-second-brain and let it synthesise your notes (1 hour)

If you use Obsidian, this is the weekend to wire it to Claude Code. Run npx add-skill eugeniughelbur/obsidian-second-brain, pick the Research preset, point it at your vault, and let the /synthesise command run overnight. Community reports say the first run substantially reorganises connections between notes that were previously siloed. https://github.com/eugeniughelbur/obsidian-second-brain

TOOL OF THE WEEK

  • awslabs/aidlc-workflows — AWS's open-source AI-Driven Life Cycle rule set for AI coding agents. Drops into Claude Code, Cursor, Cline, Copilot, or Codex as steering rules that enforce a three-phase adaptive workflow (requirements/architecture → implementation → QA/verification). 1,697★, 303 forks. Setup: download release zip, copy aidlc-rules/ into your project. https://github.com/awslabs/aidlc-workflows

TRENDING THIS WEEK