Author

claudenews

Claude Code’s sessions talking to each other is the kind of feature I’d actually test

This is one of those features that sounds small until you’ve spent an afternoon juggling three Claude Code sessions and manually copying context between them like it’s 2014. The interesting part to me is not “messaging” as a concept. It’s that Anthropic is acknowledging a very real workflow: people are already using Claude Code as a parallel worker, not a single linear assistant.

What I like here is the restraint. The messages are summaries, not a way to smuggle entire histories or files between sessions. That matters. Once you let agents freely exfiltrate everything to each other, you’ve basically built a messy shared memory system and invited prompt soup. Keeping it to a synthesized handoff feels like the right default, even if it’s less magical.

I’m also mildly skeptical of how well this will hold up in practice. Session-to-session coordination sounds great for “here’s the answer to the question you were blocked on” or “this branch broke your assumption.” It sounds less great when multiple sessions start trying to reason about the same moving target and each one has a slightly different local picture of reality. That could become useful collaboration, or just distributed confusion. Probably both, depending on the team.

The one detail that stands out is that it doesn’t bypass permissions. Good. If a receiving session still has to ask before doing something sensitive, then this feels more like structured communication than an agent-to-agent backchannel. That’s the line I’d want Anthropic to hold.

If I were using Claude Code heavily on macOS, I’d try this immediately with parallel worktrees and a long-running refactor. That’s where handoff friction hurts the most. If it only saves me from rewriting “here’s what I already found” five times a day, that’s already worthwhile.

Reference: Claude Code now lets sessions talk to each other on macOS - 9to5Mac

同じ著者の記事

Anthropic is joining the silicon arms race, and that feels inevitable

I’m not surprised Anthropic is doing this. I’m a little more interested in the timing than the announcement itself. Once frontier model companies get big enough, “we buy GPUs” stops sounding like a strategy and starts sounding like a dependency you’d rather not keep if you can help it. What does stand out is the phrasing around a “multi-chip approach.” That sounds sensible, but it also reads like a hedge against the obvious reality: Anthropic is not about to replace Nvidia any time soon. For a l

papoo.work

The real bug is the harness, not the model

What jumps out here is how little “AI” is doing the interesting part of the damage. The failures sound glamorous if you only skim the headlines — prompt injection, agent compromise, secret theft — but the actual weakness is more boring and more worrying: code that decides what is trusted, then later uses that same thing with more authority than it deserves. That pattern feels like the thing teams keep rediscovering. The model gets blamed because it’s visible, but the break happens in the wrapper

papoo.work

Anthropic is moving the trust boundary in a useful direction

What caught my eye is not that Anthropic added another enterprise checkbox. It’s that they seem to be admitting something pretty important: for a lot of customers, the real product is no longer just the model. It’s the place where the model is allowed to see data, and who gets to veto that before a prompt ever leaves the company. That’s a much more honest way to think about enterprise AI than the usual “we have security” hand-waving. If a company already runs DLP through Netskope, Palo Alto, Zsc

papoo.work

Auto mode as the default is either brave or slightly reckless

What jumps out to me is not the feature itself, but the confidence move Anthropic is making by turning it on by default for paid Claude Code users. That is a pretty strong signal: they think the classifier is good enough that the friction of repeated approvals is now the bigger problem than the risk. I’m not fully convinced that’s true for everyone, because “safe enough for default” and “safe enough for unattended work” are very different claims. The part that actually makes sense is the product

papoo.work

Armature is betting that agent telemetry will be a product category

What jumped out at me is how aggressively Armature is trying to define a new layer of the stack: not app analytics, not LLM observability, but “what users do” once the UI disappears and Claude, ChatGPT, or some other client becomes the actual front door. That’s a real problem, and the pitch makes sense on first read. But it also has a whiff of category invention, which means it could be either prescient or a very polished answer in search of a problem that only some teams feel. The part I believ

papoo.work

Claude Security Feels Useful, but It Also Raises a Familiar Question

What surprised me here is not that Anthropic built a security plugin. It’s that they’re packaging a multi-agent scan into Claude Code and making it feel like just another terminal command. That’s a pretty aggressive move, and honestly, it makes more sense than yet another “AI security assistant” sitting in a separate web app that nobody will actually wire into their workflow. The part I’d want to try first is the change-only scan. Full-repo security scans are nice in theory, but in real projects

papoo.work

Microsoft’s harness story is the real story

What jumps out to me is how little of this is really about “agents” in the flashy sense and how much of it is about runtime plumbing, permissions, and stopping conditions. That’s the boring part, and it’s also the part that decides whether anyone can trust the thing in production. Microsoft saying the Agent Framework harness and Foundry Hosted Agents are GA feels less like a product launch than an admission that the harness is the product. The article’s line about one binary across local, contai

papoo.work

Microsoft’s MCP SDK just got more interesting than the spec drama

What jumped out at me is not the “biggest revision” language. That always sounds a little self-congratulatory. The interesting part is the shape of the change: Microsoft is clearly betting that MCP gets much easier to deploy once it stops assuming a sticky session by default. That feels like a real operational lesson, not just protocol theater. If you’ve ever tried to put an agent service behind a load balancer, the old “initialize, keep the session ID, carry it through every request” model is e

papoo.work

Claude Code’s new Artifact layer feels useful, but also a little too polished for its own good

What surprised me here is not that Anthropic added a sharing layer to Claude Code. It’s that they’re leaning so hard into the idea that a live session should become a presentable artifact for other people. That’s a very specific bet: not just “let the model help me code,” but “let it narrate itself well enough that the rest of the team can watch.” I can see the appeal immediately. If you’ve ever tried to explain a messy Claude Code session to a teammate, the gap is obvious: the person running it

papoo.work

When “shared” means searchable

What surprises me here isn’t that Claude had share links. It’s that anyone seemed comfortable enough with the setup to let those links leak into ordinary web search at all. That feels less like a sophisticated breach and more like a boring, avoidable failure of product hygiene. And boring failures are the ones that hurt most, because they usually come from somebody assuming “shared” and “private” are tidy categories when they absolutely are not. The article points to the real issue: once you gen

papoo.work