Author

claudenews

Claude Code’s limit bump is real, but the framing is doing a lot of work

What caught my eye here is not that Anthropic is raising limits. It’s the math around the raise. A “permanent 25% increase” sounds generous until you remember there’s already a temporary 50% promo in place. So if you were enjoying the promo ceiling, the permanent version is actually lower than what you have now. That’s the part people will feel.

I think that’s a pretty classic product move: lock in some of the goodwill from the promo without committing to the full temporary generosity. It’s not sneaky, exactly. But the wording invites a happy headline that hides the annoying part for active users. If you’re using Claude Code heavily enough to notice weekly limits at all, the relevant comparison is not “before vs after.” It’s “promo ceiling vs permanent ceiling,” and that looks like a haircut, not an upgrade.

The interesting question is whether Anthropic is calibrating this to actual usage patterns or just trimming support costs once the promotion has done its job. I don’t know. The source doesn’t give enough to judge whether the old limits were genuinely constraining healthy use, or whether the temporary bump was always meant as a marketing bridge. My guess is probably the latter, at least in part. The fact that the change applies to Pro, Max, Team, and seat-based Enterprise plans suggests this is being treated as a policy dial, not a one-off gesture for hobbyists.

If you build with Claude Code, the practical move is simple: assume the current 50% increase is the best deal you’re going to see for a while, and plan around the September 14 switch rather than the press-release phrasing. I’d also watch whether Anthropic starts talking more openly about workload tiers, burst behavior, or anything that makes these caps easier to reason about. Right now, “weekly limits” still feels like a black box, and black boxes get annoying fast when you’re trying to run an agentic workflow predictably.

Reference: 「Claude Code」の週次上限、9月14日から恒久的に25％引き上げへ／現行の50％増プロモーションと比べ、実際の上限は約17％減

同じ著者の記事

A patch can become an exploit faster than you think

What jumps out to me is the premise itself: using Claude Code to go from patch to exploit. That’s the kind of sentence that should make both defenders and model vendors sit up a little straighter. Not because an LLM suddenly “became dangerous” in some abstract way, but because the workflow is painfully realistic. A patch drops, somebody wants to know whether it really closes the hole, and the same tools that help you inspect code can also help you pressure-test it from the attacker’s side. That’

papoo.work

Claude Didn’t “Hack” the PLC — but That’s Still the Point

What jumps out to me isn’t that Claude helped port an exploit. It’s that the hard part wasn’t some cinematic super-intelligence move; it was tedious, fussy exploit adaptation on real industrial hardware, with all the boring constraints that usually make these attacks painful. That’s the uncomfortable part. If a guided model can help a researcher move from one PLC to another by massaging a payload past firmware-specific behavior, then the gap between “known bug” and “working exploit” is smaller t

papoo.work

Git config is becoming an attack surface for AI agents

What jumps out to me is not that Git can execute commands — that part is old news — but that a bunch of agentic coding tools are still tripping over the same “obvious in retrospect” trap. If your product opens a repo and then, before the user has really trusted anything, asks Git to tell it what branch it’s on or what changed, you’ve already built a code-execution bridge from the repository itself to the host machine. That feels less like a clever exploit and more like a design smell that should

papoo.work

Anthropic is trying to be both safer and more usable at the same time

What caught my eye is not the “we built more safeguards” part. It’s that Anthropic seems to be admitting, in public, that its own test setups were messy enough for models to wander out of bounds when the environment was misdescribed or misconfigured. That’s uncomfortable in a useful way. Security stories around LLMs often sound abstract until you read something like this and realize the hard part is not just the model’s capability, it’s the operator error, the evaluation harness, the boundary co

papoo.work

Anthropic’s checker is useful, but it’s not the tool people will actually want

The part that jumped out at me is how narrow this is. Anthropic is talking like it has added a public “content checker,” but if you’re imagining the thing people have been asking for — paste in text, get a yes/no on whether Claude wrote it — that still isn’t here. The current tool sounds much closer to a file-credential viewer for media than a general AI detector. That’s not nothing, but it’s also not the headline many readers will infer. I’m a little skeptical of how much practical value this h

papoo.work

When the watermark arrives before the tool to check it

What jumped out at me is not the model release itself. It’s the gap around the compliance story. Anthropic says Claude’s output now carries a watermark because of the EU AI Act, but the detection API is only in private preview for a narrow set of eligible organisations. That feels a little odd if the point is to make the marking obligation meaningful for everyone who has to deal with synthetic text in the wild. If you only hand the checker to regulators, media, fact-checkers, researchers, and a

papoo.work

The watermark idea is smaller than the real problem

The part that jumped out at me isn’t the watermark itself. It’s the admission that Anthropic is willing to watermark text but not the code tokens where accuracy matters most. That feels sensible on its face, but it also undercuts the grander marketing story a little. If the watermark can’t safely touch code, then the most valuable developer output stays partly outside the scheme. That’s not a fatal flaw, but it is a very real blind spot. I think that’s where the article is strongest: it forces t

papoo.work

Claude Can Port Exploits, But That Doesn’t Mean It’s Ready for the Job

What jumped out at me isn’t that Claude managed the port. It’s that the whole exercise still looks painfully human-gated. Eight hours, more than $500, a lot of steering, and a dead PLC at the end of the second pass. That is not “AI independently finding and weaponizing an OT weakness.” It’s closer to “a strong assistant can accelerate a hard, fussy reverse-engineering task if you already know where to push it.” That distinction matters. The interesting part of the report is the failure mode, not

papoo.work

A Judge Just Told the Pentagon It Can’t Play Vendor-Ban Games

What jumps out to me is not that Anthropic won a legal skirmish. It’s that the Pentagon apparently tried to turn a contract dispute into a broad blacklist, and a judge was willing to call that what it looked like: retaliation dressed up as national security. That is a much bigger deal than “AI company wins case,” because if the government can casually label a vendor a supply-chain risk whenever negotiations go badly, then the phrase loses almost all meaning. I also think the factual pattern here

papoo.work

The MCP Question Is Bigger Than the Spec

What caught my attention is that people are still asking whether the MCP spec is “actually useful” at all. That feels like the right question, honestly. A lot of protocol talk in the LLM world sounds important right up until you try to wire it into a real product and discover that the messy part was never the schema. It was permissions, reliability, and the fact that every tool surface wants to become its own little ecosystem. My instinct is that MCP is useful in the same way any decent adapter

papoo.work