Tag
All content about Claude, organized for fast scanning.
Claude has introduced several significant updates, including cross-session messaging that allows tasks to communicate more efficiently by sharing summaries rather than full logs. Additionally, the latest version features a restructured command system for managing background tasks and subtasks. Anthropic has also emphasized a reduction in guardrails for prompts in Claude 5, claiming improved performance metrics and cost-effectiveness compared to competitors.
Claude Code has just added cross-session messaging, letting one task ask another questions and send updates. Instead of syncing full chat logs or files, it hands off a generated summary to reduce repeated setup. The feature is available on macOS and Linux.
Claude Code has updated /fork to spin up a background session while you keep working. Its former subagent behavior now lives in /subtask, which reports a final result back. The changes are live in v2.1.212+.
Anthropic’s Thariq shared new context-engineering guidance for Claude 5, arguing prompts are only part of what the model sees. The company says it cut 80%+ of Claude Code’s system prompt with no measurable loss, leaning more on tools, Skills, and references.
Anthropic has just rolled out Claude Opus 5, touting near-frontier performance at half the price of Fable 5. The company’s benchmark bundle puts it near the top in coding, knowledge work, and agentic tasks—though results vary by test.
Boris Cherny lays out a four-step blueprint for AI adoption, focused on breaking bottlenecks and layering guardrails—not just adding tokens. He highlights features like automated reviews, multi-agent workflows, and self-verification, plus a better ROI test than usage metrics.
Boris Cherny argues teams should make agentic coding useful by encoding repeat work into lint rules, CI, tests, and repo docs—not one-off fixes. He suggests files like CLAUDE.md and REVIEW.md so agents can contribute with minimal prompting.
ClaudeDevs has just rolled out an in-app browser for Claude Code on desktop, so it can read and interact with docs, designs, and websites without switching apps. The browser is sandboxed and configurable, with optional session persistence.
Claude Code is getting a new /checkup maintenance command aimed at tidying unused skills, MCPs, and plugins. It can also deduplicate and split CLAUDE.md files, disable slow hooks, and update settings to reduce per-session context overhead.
Thariq says Claude work breaks down when prompts don’t match the real codebase and constraints. His workflow focuses on surfacing “unknowns” early with interviews, prototypes, and tight planning—then logging deviations until the map fits the territory.
Anthropic has just rolled out Claude Sonnet 5, bringing more autonomous tool use and stronger reasoning at lower prices. The company says it nears Opus 4.8 on key benchmarks, and it’s now the default for Free and Pro users.
Anthropic has just rolled out Claude Desktop for Linux, bringing a native app experience to Ubuntu and Debian in beta. Early reactions focus on practical requests, including Arch/Fedora support, RPMs, Wayland compatibility, and performance details.
Boris Cherny, creator of Claude Code, discusses his path from startups and Instagram to Anthropic, where Claude Code emerged from the company’s focus on coding, enterprise, and safety. He explains how AI agents are transforming software development, why businesses must reorganize around AI to unlock major productivity gains, and how Anthropic is expanding compute and developer tools. He also reflects on the future of jobs, software engineers, startups, security, and why he believes coding will become a basic skill like reading and writing.
Anthropic has just rolled out Claude Tag, bringing Claude into Slack as a proactive teammate. Tag it in a thread to split work into stages, use connected tools, and report back with results. It’s in beta now for Claude Team and Enterprise plans.
Claude has just rolled out Claude Design, a beta feature for paid web and desktop plans. It can import a design system from code or files, edit layouts directly on a canvas, and sync changes both ways with Claude Code.
Paweł Huryn says Fable 5 can beat Opus 4.8 on audit economics, even at 2x token pricing. Across 60 metered Claude Code sessions, Fable cost more per run but surfaced a planted cross-file bug far more often—cutting expected spend to catch it.
Lance Martin says Claude Fable 5 performs best when built around self-correction loops and cross-session memory. Using benchmarks like Parameter Golf and Continual Learning Bench, he reports stronger gains than Opus 4.7—while replies debate cost and verification.
Anthropic has just rolled out Claude Fable 5 and Claude Mythos 5, pairing a general-release model with a more permissive version for trusted users. The company touts big gains in coding, vision, and research, plus new safety routing and lower API pricing.
Claude Code has just rolled out nested subagent support, an experiment in “agents kicking off agents” to better manage context. The first release caps nesting at depth=5, with a new “fork:true” option to run skills in separate context windows.
Anthropic’s Boris Cherny says Claude Opus is especially strong at multi-hour, even multi-day, autonomous work. He shares five tactics—from auto permissions and dynamic agent workflows to browser-based self-verification—plus notes on ROI, token usage, and caveats.
Anthropic says Claude Code’s /fork can now spin up a background agent using the exact context from your active session, then return results to the original thread. It also clarifies /branch as the older, manual workflow—sparking questions about tokens and receipts.
ClaudeDevs has rolled out a new ant CLI for Claude Platform, bringing Messages API and Managed Agents to the terminal. It promises OAuth login, piped YAML requests, TUI exploration, and Git-versioned agent configs synced from CI.
Anthropic has just rolled out a Claude Code research preview called dynamic workflows, letting Claude generate an orchestration script and coordinate fleets of subagents. It targets big jobs like migrations and bug hunts, but can burn tokens quickly. Available on Max, Team, Enterprise, and APIs.
Anthropic has just rolled out Claude Opus 4.8, touting sharper judgment, more honesty, and longer independent work. A new “Fast mode” promises roughly 2.5x speed and lower cost, while Claude Code gets deeper agentic workflows for long-running tasks.
Anthropic has rolled out a new security-guidance plugin for Claude Code, designed to flag risky patterns during edits, model turns, and commits. The company says internal testing cut security-related PR comments by 30–40%, while users debate accuracy and false positives.
Anthropic has published a new guide detailing how Claude Code performs in huge monorepos and legacy systems—and why results hinge as much on setup as on the model. It breaks down the “harness” teams use to keep navigation, context, and governance on track.
Anthropic has added prompt cache diagnostics to Claude Console, showing exactly what changed when a request misses the cache. The view also breaks down the token cost of the miss, helping developers debug prompts and track spend.
The opening of the talk defines “vibe coding” as more than just using AI to help write code. The speaker argues that true vibe coding means letting the model handle the implementation to the point that you “forget the code exists,” while you focus on the outcome. He explains why this matters: as AI systems get better, they will be able to handle larger and larger chunks of work, making it unrealistic for humans to stay in a tight line-by-line review loop forever. He then frames the core challenge as how to use this approach safely in production. His answer is that engineers should stop obsessing over every implementation detail, but still stay accountable for the product’s behavior and quality. He compares this to managers or executives overseeing work they cannot personally execute in full detail: they succeed by verifying outcomes, requirements, and checkpoints rather than inspecting everything directly. A key caveat in this early section is tech debt. He says that unlike product behavior, tech debt is still hard to validate without actually understanding the code. Because of that, he recommends using vibe coding mainly on leaf nodes of a codebase, meaning isolated features where problems are less likely to spread into the core architecture.
Agents can be smart and still unreliable for real work when they lack domain expertise. This talk argues that the next step isn’t more agent scaffolding—it’s packaging reusable expertise as “Skills” that agents can load when needed. Key takeaways Breaks down what Skills are: organized folders of procedural knowledge (including scripts/tools) that can be versioned, shared, and composed. Explains why code and the file system can act as a universal interface, while Skills supply the missing domain context. Walks through “progressive disclosure” to protect the context window and enable libraries of hundreds or thousands of Skills. Maps an emerging architecture: agent loop + runtime environment + MCP servers for connectivity, with Skills providing expertise—and how that supports deployment across domains.
Coding agents are everywhere—but what actually made them finally usable for real engineering work? This talk walks through Jared Zoneraich’s independent breakdown of Claude Code’s architecture and why he believes “simple” beats brittle, over-engineered agent frameworks. Key takeaways Breaks down the “Master Loop” approach: a single-threaded while-loop that repeatedly calls tools and feeds results back to the model. Covers the core toolset (e.g., Bash, Grep/Glob, diff-based editing) and why Bash is central for robustness and training-data reasons. Explains prompt-driven planning via to-do lists—structured guidance without deterministic enforcement. Discusses reliability concerns: sandboxing/permissions, context management, and the use of sub-agents to avoid bloating the main context.
If you’re weighing Claude Code versus Cursor (or trying to juggle both), this walkthrough shows what changes when Claude Code is fully integrated inside Cursor—so you can work with live context without constantly re-explaining your code. Key takeaways Walks through setup in Cursor’s integrated terminal: updating Claude, signing in, and confirming the integration. Shows how the status indicator reflects the active file, enabling prompts like “what does this file do?” without naming it. Demonstrates line awareness: select a block of code and ask “what does this do?” with the selection as context. Breaks down the diff view workflow—review proposed changes, revert specific blocks, and accept/reject (with an optional auto-accept toggle), plus linking Cursor from an external terminal via /ide.
Learn how to integrate Claude Code 4 with Cursor in this step-by-step tutorial. This new feature from Anthropic brings full Claude Code support to the Cursor AI IDE, giving you new features, like inline diff views and real-time code context, all within your favorite IDE. I’ll walk you through the setup process for Cursor and explain key features that make this integration of the best AI coding agent upgrades yet.