All content about Claude, organized for fast scanning.
30 itemsUpdated May 28, 2026
In Brief
Anthropic has introduced several enhancements to its Claude AI, including dynamic workflows for orchestrating subagents, which aim to improve efficiency in complex tasks. The latest version, Claude Opus 4.8, features a faster and more cost-effective mode, while a new security plugin helps identify risky coding patterns. Additionally, best practices for using Claude Code at scale have been outlined, emphasizing the importance of setup and governance in achieving optimal performance.
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.
Anthropic has just rolled out dedicated monthly “programmatic usage” credits for paid Claude plans, covering Agent SDK, claude -p, GitHub Actions, and third-party tools. Starting June 15, interactive chat keeps subscription limits while agents draw from the new credit.
Anthropic has just rolled out a temporary 50% increase to Claude Code weekly limits for Pro, Max, Team, and seat-based Enterprise users. The bump applies across CLI, IDE extensions, desktop, and the web, stacking with last week’s 2x 5-hour limit boost.
Notion has just rolled out its External Agents API, bringing third-party and custom agents directly into your workspace. The company says partners like Claude, OpenAI Codex, Cursor, and more will work out of the box, with a waitlist now open.
Claude Code 2.1.139 reportedly introduces /goal, a command that keeps working across turns until a stop condition is met. Early reactions praise the hands-off workflow, but raise concerns about reliability and usage caps.
Anthropic has just rolled out Fast Mode for Claude Opus 4.7 in research preview on its API and in Claude Code. It’s opt-in now for Claude Code users and becomes the default Thursday, with previews also live in tools like Cursor and Warp.
Claude has just rolled out agent view for Claude Code, a CLI dashboard for tracking all your sessions in one place. It shows what’s waiting on you, what’s still running in the background, and what’s finished. Available now as a Research Preview.
In a May 8 thread on X, Thariq argues Claude Code is increasingly better at generating HTML than Markdown. He says HTML enables richer structure, visuals, and interactivity—despite higher token cost and noisier diffs.
Anthropic used its Code with Claude keynote to highlight faster AI adoption and bigger capacity. Claude Code rate limits are doubling on paid plans, with higher API limits for Opus. New managed agent features add orchestration, outcomes, and “dreaming.”
Anthropic has rolled out a Claude Managed Agents update adding “dreaming” to refine memory between sessions, plus outcomes with a separate grader. Multiagent orchestration and webhooks also land, aimed at boosting task success with less developer steering.
Anthropic has struck a compute partnership with SpaceX and is raising rate limits for Claude Code and the Claude API. The deal unlocks more than 300MW of new capacity, aimed at improving availability for Pro and Max subscribers.
Claude Managed Agents are gaining multi-agent orchestration, rubric-driven self-improvement, “dreaming” memory curation, and webhook updates. The additions aim to streamline coordination and background learning, as early replies question cost, limits, and safety.
Claude has just rolled out Claude Security in public beta for Enterprise customers, promising vulnerability scans with validated findings and patch suggestions—no API integration required. New additions include scheduled scans, exports, webhooks, and scan-to-scan dismissals.
Anthropic published a postmortem on Claude Code quality complaints, pointing to three separate changes that hit reasoning effort, session history, and verbosity. All were reverted or fixed by April 20, and subscriber usage limits were reset April 23.
Simon Willison has published a new project that turns Anthropic’s Claude system prompt history into a browsable git repo. With prompts split into granular files and timestamped commits, you can use git log, diff, and blame to trace changes over time.
Claude has just rolled out a caching-focused dashboard in the Claude Developer Console, aiming to give developers clearer visibility into how prompt caching affects spend and time-to-first-token. The company is also spotlighting new resources to help improve cache hit rates.
Anthropic has just rolled out Opus 4.7, and reactions are sharply split. Simone Civetta argues the divide reflects uneven workflow impact, shifting benchmarks, and prompt breakage tied to stronger instruction following. He suggests higher “effort” modes to curb under-thinking.
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.
Paweł Huryn breaks down what changed in Claude Opus 4.7 versus 4.6—and why some “regressions” are really prompt friction. He shares 10 practical migration moves, from intent-first context files to batching asks and updating adaptive thinking settings.
Anthropic’s Boris Cherny shared new workflow tweaks for Claude Opus 4.7 focused on longer, less interruption-prone coding runs. Highlights include auto mode for safer auto-approvals, recaps and focus mode, and verification tools like /go for end-to-end tests.
Anthropic has just rolled out Claude Design, bringing conversation-first creation for prototypes, slides, one-pagers, and more. Powered by Claude Opus 4.7, it’s a research preview for Pro, Max, Team, and Enterprise with exports and Claude Code handoff.
Anthropic’s Opus 4.7 is pushing Claude Code toward longer, more agentic workflows. Boris Cherny details auto mode for fewer permission interruptions, plus recaps, focus mode, effort tuning, and a /go verification loop that can end in a PR.
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.