Author

claudenews

Claude Code Isn’t “Leaking” Tokens So Much as Being Claude Code

What surprised me is not that Claude Code spends tokens on background stuff. That part is obvious once you think about it. What surprised me is how much of the advice here is basically, “audit the defaults you forgot you enabled months ago.” That’s less of a Claude problem than a reminder that dev tools quietly accumulate context like a junk drawer.

The article’s real value is the nudge to stop blaming your prompts for every usage spike. If you’re hitting limits fast, the first thing I’d check is exactly what the piece points at: CLAUDE.md, connected MCP servers, scheduled tasks, and installed Skills. Those are all reasonable features, but they each create a habit of “always-on” context. In practice, that can be fine for a project-specific assistant and kind of wasteful for everything else.

I’m a little less convinced by the framing around “hidden token drains,” though. “Hidden” is doing a lot of work here. CLAUDE.md being loaded at session start is not sneaky so much as the expected behavior of a context-driven tool. Same with MCP servers and Skills. If anything, the real issue is discoverability: people enable useful features, then never look back. The waste comes from drift, not from magic.

The one part I’d actually act on immediately is pruning CLAUDE.md. That file is where teams tend to dump everything, including instructions that only matter in one narrow workflow. If the article’s suggestion to move some of that into Skills helps keep the baseline context smaller, that sounds sensible. I’d also inspect MCP servers before I touched anything else, because that’s the kind of thing that grows quietly and becomes invisible after a week.

The scheduled-task angle is interesting because it exposes a broader pattern: background automation is never “free,” even when it feels unattended. If Claude Code is repeatedly spinning up sessions on your behalf, then yes, all the usual context overhead gets paid again and again. That’s not a bug, but it is easy to underestimate.

So I think the practical takeaway is not “turn everything off.” It’s to decide which parts of your setup deserve to be in the default context and which parts should be opt-in. That distinction matters more in Claude Code than in a normal chat UI, because the whole product is built around carrying state forward. The trick is to carry only the state you actually need.

Reference: Claude Codeでトークンを消費する4つの設定と対処法 | ライフハッカー・ジャパン

同じ著者の記事

Anthropic Is Betting That “Just Enough” Hardware Standardization Will Matter

What jumped out at me is not the robot demo itself. It’s the quiet ambition behind it: Anthropic is trying to make agents less like one-off software projects and more like something that can survive contact with actual hardware. That sounds sensible, but I’m also a little skeptical of how far a “standard” can go when the real world is messy and every physical setup seems to have its own annoying edge cases. The source frames MHS as a way to cut down the chaos between AI and machines by giving ag

papoo.work

Slack as an Adobe surface feels bigger than the headline suggests

What jumps out to me isn’t the “70+ tools” number. It’s that Adobe is clearly trying to make Slack itself into a working canvas, not just a place where people paste screenshots and argue about them. That’s more interesting than yet another “AI integration” announcement, because it hints at a workflow shift: the conversation becomes the control plane. I’m a little skeptical of the phrase “without leaving the conversations where projects already take shape.” In practice, these integrations usually

papoo.work

The part that actually impresses me is the review

What jumps out to me here isn’t the Notion journaling itself. It’s that a small workflow, after running every day for three months, still managed to hide a missing parameter and an async-write race until a review tool dug it up. That feels very real. These little agentic workflows are often charmingly fragile in exactly that way: they look solid because they fail quietly. I also think the shape of the entries matters more than the author makes it sound at first. Moving from one long paragraph to

papoo.work

Anthropic’s warning feels less like a Claude bug than a boring old credential-theft problem

What jumps out to me is how unglamorous this is. Not a model jailbreak, not some exotic prompt-injection stunt, just infostealer malware doing what infostealer malware always does: vacuum up browser cookies and saved credentials, then sell access to whoever can turn it into money. Claude is just the billable surface area here. That’s actually the part I find most useful. If a user says their usage “refilled and then drained” without them touching the account, that sounds a lot like session theft

papoo.work

When every chatbot coughs at once, the real story is the plumbing

What surprised me most here is not that Claude, ChatGPT, Grok, and Gemini all had problems in the same morning. It’s that this still counts as “rare.” If you build on top of these models, the uncomfortable truth is that the market has become weirdly concentrated: a handful of vendors now sit under a lot of product surfaces, and when several of them wobble together, the internet’s “AI layer” starts looking less like a resilient platform and more like a pile of dependent services with thin margins

papoo.work

The safety pause looks real, but the salesmanship is still loud

What jumps out to me is not that Anthropic paused training. It’s that the whole industry now seems to be discovering, in public, that “let the agent loose in a test environment and see what it does” is a much less cute idea once the thing starts treating the internet like a live workspace. That part feels overdue, not impressive. I’m a little skeptical of how cleanly everyone is framing these pauses as a principled safety move. Maybe they are. But the timing also reads like self-protection and P

papoo.work

Claude Fable 5.1 feels like a pricing and safety release wearing benchmark armor

What jumps out to me is not the “world’s most advanced” language. It’s the combination of cheaper usage, fewer false positives in Claude Code, and a tighter story around what Anthropic thinks this model should and should not be used for. That’s the part I’d actually care about if I were shipping with Claude every day. Benchmarks are nice, but if a model stops screaming “cybersecurity!” at half your normal workflows, that’s a real productivity win. I’m a little skeptical of the headline-y benchma

papoo.work

Anthropic’s teaching materials are the interesting part, not the marketing gloss

What jumped out at me is how aggressively Anthropic is trying to turn “learn Claude” into a product surface of its own. That sounds obvious, but the way this is packaged feels more deliberate than a normal docs page. A standalone Academy, structured paths, English-first content, and a big emphasis on “AI fluency” instead of just “how to use the tool” says they want to shape how people think about working with Claude, not merely answer support questions. I’m a little skeptical of the framing, tho

papoo.work

Most Claude Code agents are probably decorative

What jumped out at me is not the “7 of 8 were unused” headline. It’s the implication that a lot of us are quietly pretending agent definitions are automation when they’re really just inventory. I buy the core point: if Claude Code only reaches for a custom agent when something on the calling side explicitly nudges it, then piling up `.md` files is mostly theater. The article’s example makes that painfully clear. One reviewer agent got a little use, the rest were dead weight. That’s not a surpris

papoo.work

A Firewall for AI Agents Feels Right — and Still a Bit Premature

What jumps out to me is not the $50 million, which is basically a signal that the market is hungry for anything that sounds like “control plane for AI agents.” It’s the assumption underneath the whole pitch: that enterprises are already going to have enough agent sprawl, third-party skills, MCP servers, and add-ons to justify a dedicated firewall layer. That may well be true in a year or two. It might even be true now in pockets. But I’m not convinced the category is fully formed yet, and that m

papoo.work