Wanted to try something fun and used the Remotion studio workflow to make an animation for my dnd group, something that I couldn't have imagined having the time to do in the past

Same $5 per million input tokens. Same $25 per million output. The pricing page says nothing moved from 4.6. But if you're on Max, your weekly Opus quota drains faster than it did a month ago. Same prompts, same code, same workload. The number on the invoice didn't change. The number of tokens per request did. Buried in Anthropic's own pricing doc, as a footnote under the model pricing table: "Opus 4.7 uses a new tokenizer compared to previous models, contributing to its improved performance on a wide range of tasks. This new tokenizer may use up to 35% more tokens for the same fixed text." Read that again. Same fixed text. Up to 35% more tokens. That's not a price change you'd see on the sticker. It's a price change on every single request you send. And honestly, that's only the first silent bump. When Claude Code v2.1.117 shipped, the default effort level on Opus 4.7 moved to xhigh. Opus 4.6 and Sonnet 4.6 still default to high. If you never ran /effort to check, every call you've sent since the update has been reasoning harder, and burning more thinking tokens, than the same call a month ago. Haiku doesn't support effort levels at all, which honestly isn't a limitation. It's flat-rate reasoning you can actually budget against. Two bumps stacked on the same workload. The Opus weekly cap on Max feels smaller because it effectively is. The obvious move is to use Opus less. That's the wrong frame. The right frame is that most of what you're running on Opus shouldn't be on Opus in the first place. Open /agents in any recent Claude Code session and look at what Anthropic's own built-in subagents run on. Explore runs on Haiku. Claude Code Guide runs on Haiku. statusline-setup runs on Sonnet. Only Plan and general-purpose inherit whatever your main conversation is using. Anthropic shipped the cost routing pattern directly into the product. Every custom subagent in your .claude/agents/ or ~/.claude/agents/ that doesn't set a "model:" field just inherits Opus and pays Opus rates for whatever it does.

I spend more time thinking about how to use AI than actually using it. Watching, learning, tweaking setups… but when it comes to sitting down and doing something real, I hesitate. Not sure if it’s overthinking or just avoiding mistakes. I am trying to fix that, though. Anyone else?

For those who missed the first post or just joined: The Lyceum is a 12-week program we're building. Live instruction from Jake and the Eduba team. Small cohorts. Real projects. You build something from week one, not watch tutorials. At the end, a competition with real prizes. Eduba's first certification, backed by the same methodology we've used to train Fortune 500 teams. Now here's what we've locked in since then. The Structure Three 4-week sprints with a 1-week break between each. Not 12 straight weeks of grind. You build, you breathe, you come back sharper. - Sprint 1: Foundation — Core methodology. Everyone starts here. - Sprint 2: Application — You're building. Real project, real progress. - Sprint 3: Capstone — Finish what you started. Demo day prep. The breaks aren't fluff. They're built in so you can catch up, refine, or just live your life without falling behind. The Cohorts Same curriculum across all three. The difference is where your hours go. Technical — Developers, engineers, technical founders. You're building a tool or production system. 30% of your time goes to Claude Code and integrations. Another 30% to production systems and capstone. This is the builder track. Business — Ops, managers, founders, consultants. You're automating a process or designing a system spec. Heavy emphasis on workflow design (30%) and decision frameworks (25%). You direct the work without writing the code. Creator — Marketers, educators, solo operators. You're building a content production system. One person replaces the team. 25% on content pipelines, 20% on workflow design. This is how you scale yourself. Pick the track that matches how you work. The methodology transfers no matter which one you choose. A 4th Cohort? We're considering adding a team cohort if there's enough interest. This would be for companies that want to enroll multiple employees, or for people in the community who want to form their own team and build together. If that sounds like you, let us know in the comments.

I was sharing our community with our senior developer/director and telling him that what we’re doing here is going to change how we structure things in the company and create better results using Claude Code. I’m currently part of the lead team developing the company’s AI assistant model with multiple structured agents and layered analysis systems designed to support precise sales and marketing execution. I told him that I couldn’t really afford an enterprise-level account for Claude, so I haven’t been able to fully test everything I’ve been learning here as a VIP member. He spoke with the higher-ups and secured a 5-seat plan for me so I can continue applying what I’ve been learning, help the business grow in the future, and train the team using @Jake Van Clief notes...