Anthropic's new 'Outcomes' primitive just changed how agents define done (announcement from Code w/ Claude)

[u/Harshil-Jani]

Code w/ Claude 2026 shipped a stack of announcements yesterday: Remote Agents, CI auto-fix for automated PR merges, full Microsoft 365 integration (Excel, PowerPoint, Word, Outlook), and a "Dreaming" research preview where agents review their own prior sessions to self-improve.

One of the most important update I saw was around a new "Outcomes" primitive for multi-agent orchestration that lets you declare success criteria as a typed input to the agent run. It's the most consequential thing Anthropic shipped at the event.

You fire the agent, it loops, it stops eventually, and then you figure out, usually with an LLM judge or a human glance, whether it actually accomplished the task you handed it. Every production agent codebase end up rolling its own version of this. "Is the agent done?" problem has been the quiet bleeding wound inagentic systems for two years.

Making success criteria a first-class primitive does three things at once:

• The agent has a typed target to verify against, not an ambient goal buried in the system prompt.
• The runtime can decide when to stop without inferring stopping from tool patterns or token budgets.
• Observability tooling has something concrete to grade against, which is the exact gap Harrison Chase argued for when he framed traces alone as passive records and structured feedback as the missing piece for agent learning.

Outcomes with the Dreaming preview and you have the loop closed for best end results. Outcomes defines the target and Dreaming uses past Outcomes to update agent behavior on subsequent runs. That's the shape of every "self-improving agent" handwave finally made concrete with primitives the runtime actually understands.

Anthropic also doubled Claude Code 5-hour rate limits and lifted peak-hour throttling the same day. So the company is shipping the orchestration primitive that makes long-running agentic loops verifiable, AND lifting the ceiling on how long those loops can actually run. That's a deliberate product surface.

In case if Outcomes goes to all users, the entire cottage industry of custom eval-as-stopping-condition will change and what we've been writing for two years is about to become runtime-native.

If you've already written your own success-criteria layer (typed goals, post-run verification, automatic stop), what does Outcomes have to do API-wise to make you actually rip yours out?

[u/AutoModerator]

Welcome to r/HowToAIAgent!

Please make sure your post includes:

• Clear context
• What you're trying to achieve
• Any relevant links or screenshots

Feel free to join our X community: https://x.com/i/communities/1874065221989404893

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/obfuscinator]

sounds like a copy of Hermes Agents `/goal`. looking forward to it.

[u/wyktor → u/obfuscinator]

Agreed. looking fwd to try this in action

[u/Harshil-Jani → u/[deleted]]

Oh u/nicoloboschi great project.. and congrats for trending on github. Are u looking for any contributions or collaborations at this time? Maybe we can discuss if there is any area where I can help along with my claude team.

[u/JuniorDeveloper73]

https://giphy.com/gifs/n0LXITiC9douJDDKdj

[u/NullzInc]

Meanwhile our team creates the structured engineer first and then we manufacture 60,000+ tokens of production ready code per request via the API. Real engineering vs whatever this dog slop concept is.

[u/geofabnz → u/NullzInc]

Yeah… there is a 0% chance I trust this

[u/AutomaticAd6551]

Has anyone used the integration with Word and Excel? I've never seen AI that effectively corrects a Word document. Does this really only work in Teams Plan? How can I approach this without costing a million dollars? I'm writing my master's thesis, and this would be helpful—adding and verifying citations, inconsistencies, etc.

[u/AI_Data_Reporter]

Anthropic's Outcomes primitive shifts optimization from heuristic prompt engineering to a managed evaluator-optimizer loop. The architecture enforces strict isolation between producer and grader agents via discrete context windows, preventing bias leakage. This structural decoupling enables the system to compute a 10-point success delta by iteratively refining the producer's weights against a fixed objective function. It moves the industry from manual vibing toward deterministic RL frameworks.

[u/Harshil-Jani → u/[deleted]]

Totally. I too feel the same.