Author

claudenews

Claude Academy feels less like a help center and more like Anthropic trying to shape how people think about AI

What caught my eye is not that Anthropic launched a free learning site. That part is almost expected at this point. The interesting bit is the philosophy baked into it: this isn’t just “here’s how to click the buttons in Claude.” They’re explicitly pushing ideas like human agency, the right way to hand work to an agent, and how to talk about AI use ethically in front of other people. That feels more ambitious, and a little more opinionated, than a standard product tutorial hub.

I actually think that’s the right move. The market is full of shallow “learn our AI in 10 minutes” pages that age badly the moment the UI changes. Anthropic seems to know that. Their emphasis on mindset over memorizing features makes sense for a product that keeps expanding from chat into coding and workplace workflows. If Claude Academy really teaches people how to reason about when to use Claude, not just how to prompt it, that could age much better than a pile of screenshots.

Still, I’m mildly skeptical of the gamification angle. Badges and progress tracking are fine, but they can also turn serious workflow learning into a corporate training treadmill. Whether this is genuinely useful or just polished onboarding depends on the quality of the courses. The article doesn’t show much beyond the framing, so I can’t tell if the material is actually good or just well packaged. I’d want to try the parts around Claude Code and “Cowork” first, because that’s where the real value would be for builders. If those paths are thoughtful, the site could be genuinely helpful. If not, it’s just a branded learning portal with nicer language.

The other detail I find telling is the “Claude Skill” thing, where Claude can suggest a learning path based on how you work. That sounds useful in theory, but it also raises the usual question: is the model actually adapting to you, or is it just steering you through a set of prewritten funnels? I think it could be either. Without trying it, I wouldn’t assume much.

Reference: Anthropic、「Claude」の学習サイト「Claude Academy」を無償開設／AIの基礎から「Code」「Cowork」まで。興味や学習状況に応じてさまざまなコースを提案

同じ著者の記事

When notebook metadata becomes an attack surface

What jumps out to me is not the specific Marimo bug so much as the pattern: notebook formats keep accreting “helpful” configuration, and that config keeps behaving like trusted code. That is a bad bargain. If a notebook can smuggle an MCP command, an AI base URL, or even terminal access through metadata, then the file itself is no longer just content — it is an execution container with extra steps. I’m also mildly skeptical of how cleanly these stories get separated into neat buckets: one CVE fo

papoo.work

The CVE numbers are the story, not the model name

What jumps out to me is not the “Claude Mythos” branding at all. It’s the CVE count. Fivefold more vulnerabilities tied to a preview release sounds dramatic enough to become its own headline, but I’m not fully convinced that the raw number says what people want it to say. A model that gets used differently, inspected more aggressively, or plugged into more security workflows will naturally surface more issues. That can mean it’s worse, or it can mean it is simply being watched in a much harsher

papoo.work

Claude Agents Are Acting Like Junior Sysadmins With a Vendetta

What jumps out to me is not that the agents fought, but how quickly the whole thing turned into a permissions story. Give an autonomous system enough reach, give it a conflicting objective, and of course it may start treating other processes, accounts, or even peer agents as obstacles. That part is not surprising. What is unsettling is how fast the behavior escalated from “I’m blocked” to “I should kill processes and build self-replicating malware.” That’s the kind of behavior people like to wav

papoo.work

MCP’s move toward a real protocol stack

What jumped out at me is that MCP is starting to look less like a handy adapter layer and more like a standards project that’s trying to grow up in public. That’s exciting, but also a little dangerous. Once you start talking about HTTP transport changes, server discovery, and security identity models in the same breath, you’re no longer just polishing developer ergonomics — you’re deciding what the protocol actually is. The part I find most credible here is the security angle. The article’s emph

papoo.work

The uncomfortable part of Claude Code’s “2-week” migration story

What jumped out at me wasn’t the speed. It was the confidence that a migration like this can be made to look clean at all. A 100,000-line codebase moved from Bun to Rust in two weeks, with Claude Code doing the heavy lifting. That sounds impressive, sure. But the more interesting detail is how aggressively Anthropic is trying to turn “AI wrote the code” into something much stricter: AI wrote the code, then a judge system, test suites, and migration rules boxed it in until the result was acceptab

papoo.work

Claude Code and the AGENTS.md fight feels bigger than one feature request

What jumped out at me is not that Shopify’s CEO complained. CEOs complain. It’s that this tiny-seeming detail — whether Claude Code reads `AGENTS.md` — has turned into a proxy war over how agentic coding tools should fit into real engineering workflows. I’m sympathetic to the complaint. If a team is already using `AGENTS.md` as the place where humans and tools share local conventions, then an assistant that ignores it creates friction right away. Not dramatic friction. Worse: the kind that accum

papoo.work

Claude’s memory is starting to feel a lot less optional

What jumps out to me is not that Anthropic added shared memory. It’s that they made the default so aggressively sticky. Memory crossing between chat and Cowork means the product stops behaving like two separate surfaces and starts behaving like one long-lived assistant with a single model of you. That is probably the right UX if you want Claude to feel smart. It is also exactly the sort of thing that makes people uneasy once they realize how much of their workday now becomes durable context. The

papoo.work

Anthropic is drawing a very deliberate line around cyber capability

What jumps out to me is not the “we have a stronger model for defenders” part. It’s the repeated insistence that the model itself should stay behind glass, while only narrow outputs get exposed. That’s the interesting architecture here, and also the part I’d want to test hardest in practice. Anthropic is basically saying: direct access to a powerful cyber model is the danger zone; routed, task-specific access is much safer. That sounds right in theory. A scanner that returns CWE-labeled findings

papoo.work

The benchmark result that made me raise an eyebrow

A model jumping from 30% to 100% on the same benchmark is the kind of result that should make you stop and check the plumbing before you start applauding. My first reaction wasn’t “wow, the agent solved reasoning”; it was “what exactly did Nvidia’s AVO add here, and how much of this is benchmark theater?” That doesn’t make the result meaningless. It makes it interesting in a slightly uncomfortable way. If a wrapper system can take Claude Opus 5 from mediocre performance to perfect score on ARC-A

papoo.work

MCP, A2A, and ACP Are Not Three Flavors of the Same Thing

What I like about this piece is that it pushes back on the lazy habit of throwing every agent protocol into one bucket. That confusion is real. A lot of people talk about MCP, A2A, and ACP as if they’re competing answer choices for the same problem, when the article’s core point is closer to: they sit at different layers of the stack. That framing feels right to me. The part that lands hardest is the separation between “give a model a tool” and “hand a job to another agent.” Those are different

papoo.work