27 posts tagged with "Claude"

Short answer: not as a single named feature, but functionally, almost yes.

Anthropic did not publish a launch called "auto-fix in the cloud." What it actually shipped is more interesting: Claude Code now has the pieces to run coding work on Anthropic-managed cloud infrastructure, monitor pull requests, attempt CI fixes automatically, and even merge when checks pass.

For developers, that distinction matters. This is not just branding nuance. It tells you how the workflow is really assembled, what is automatic, and what still depends on your setup.

Claude has shipped so much in the last few weeks that it is easy to miss the bigger pattern.

This is not just a run of isolated feature launches. Anthropic is tightening the loop around a more complete agent product: more memory, more context, more execution, more review, and better output surfaces.

If you build with Claude, or run teams on top of it, that is the real story worth paying attention to.

Claude’s 1M token context is no longer just a beta experiment.

As of March 13, 2026, Anthropic says 1M context is generally available for Opus 4.6 and Sonnet 4.6, which changes how teams should design long-code and long-document workflows.

This post summarizes what is actually available now, what still has caveats, and how to roll it out safely in production.

Anthropic’s March 2026 Skill Creator update is easy to summarize as “better tools.”

But for teams shipping agent workflows, the real change is bigger: skills now have a testable lifecycle, closer to software engineering than prompt tinkering.

This post breaks down what changed, what the community is learning in practice, and how to adopt it without overcomplicating your stack.

Most agent skills fail for a boring reason: we edit prompts, rerun once, and call it “better.”

Anthropic’s latest Skill Creator update pushes a more engineering-style loop: test first, measure behavior, then refine. If you build internal agent workflows, this is the shift that actually matters.

This post rewrites the official announcement into a developer workflow you can run every week.

Most teams do not fail with agents because of model quality.

They fail because they pick the wrong workflow pattern too early: too much orchestration, too many moving parts, and no clear reason for the complexity.

Anthropic’s recent guide on common agent workflow patterns is useful, but this post rewrites it for developers building production systems.

If you want Cowork to do real work for you, plugins are the lever.

As of February 28, 2026, we now have a clear official path:

• Anthropic introduced Cowork on January 14, 2026
• Custom plugin creation/sharing was announced on January 20, 2026
• Enterprise plugin directory updates shipped on February 24, 2026
• Plugin help docs were updated on February 25, 2026

This guide combines that official flow with practical lessons from community users so you can build your first useful plugin from scratch.

I’m not a hardcore developer. I’m more like: “I want AI to help me do stuff, but please don’t make me read 20 pages of docs first.”
So when I saw that Claude Code just shipped a new feature called Remote Control, I got curious. Then I noticed people in the AI community were also hyping something called OpenClaw.

This post is my beginner-friendly breakdown of what’s going on, what actually matters, and which one you should care about.

Anthropic introduced Claude Opus 4.6 on 2026-02-05, positioning it as a major upgrade for coding and long-running agentic work. From our Claude Code documentation perspective, this release is about more than model quality: it changes how we should structure tasks, manage context, and design reliable multi-step workflows.

On October 15, Anthropic released Claude Haiku 4.5. Four days later, we've collected real feedback from Hacker News, technical blogs, and developer communities, along with performance data, to see if this model actually lives up to the hype.

Spoiler: This might be one of the most disruptive AI model releases this year.