curated · 2026-09-16

This is worth a click because Anthropic is pushing Claude from a Q&A box toward a workspace. Before this, making docs or slides meant jumping into a separate Claude Workspace tab. Now you generate, edit, and export right in the chat thread — the path is much shorter. Boris Cherny is an Anthropic engineer, so the source is solid, but the post doesn't say whether this is rolling out to all users or paid tiers first, and there's zero detail on export fidelity. I'd treat it as 'feature is live, details need real-world testing.' If the PowerPoint export holds up, it puts direct pressure on light Google Slides and Canva use cases.

The useful bit here is how Anthropic sidesteps the deadlock where stronger models get locked down harder. Instead of piling on more safety filters, they're shifting vetting upfront: check the team's credentials and ethics first, then grant access in two tiers. Standard Use covers most daily R&D work with an annual renewal; High-risk Use is per-project, renewed every six months, and strips all biology safeguards. Monitoring moves from real-time blocking to offline pattern analysis with 30-day data retention, and the data isn't used for training. I'd flag two gaps: the post doesn't disclose application fees or approval timelines, which are pretty important if you're considering applying. Also, Mythos high-risk access is limited to a small set of US-vetted entities for now—not broadly available. But the direction is clear: build a trusted channel for pros rather than blanket-blocking everyone. That's a smarter play than just stacking more safety classifiers.

This is worth a click because it tackles a real pain point: every new session with an AI coding tool feels like amnesia—you have to re-explain test commands, code style, and project structure. Grok Build now auto-captures these conventions and decisions as markdown notes in the background, then reads them back before touching code in later sessions. The demo shows it remembering "use just test, not cargo test," then automatically running the right command after a code change. That's more proactive than Cursor Rules or Copilot's instructions files—you don't write the notes manually; it extracts them from conversation. I'd discount this a bit, though. xAI doesn't spell out what counts as "durable" vs. "transient"—that boundary gets fuzzy fast in real projects. /dream merges scattered notes into topic files, which sounds like auto-summarization, but the post gives no examples of output quality. It's also live only for new sessions, so existing projects have to wait. If the auto-capture is actually reliable, it addresses one of the biggest gaps in AI coding tools: context continuity. The real question is how often it gets things wrong in practice.