Fetching from the wire…
Top 5 · 2026-05-12 · source-backed
Two features shipped in Claude Code v2.1.139 that I've been wanting for months.
The /goal command lets you set a completion condition and walk away. Instead of manually re-prompting after each step ("okay now run the tests" ... "fix that failure" ... "run them again"), you type /goal all tests pass and coverage exceeds 80% and Claude keeps working across turns until the condition is met. It shows live progress. It works in interactive mode, headless -p mode, and Remote Control mode.
Agent View is the other half. Run claude agents and you get a unified dashboard listing every running, waiting, and completed session in one screen. Combined with /goal, you can run multiple goal-driven sessions in parallel from one terminal. Start three features, each with their own completion condition, and monitor them from a single view.
I've been using Claude Code in my personal projects for months. The single biggest friction point was the re-prompt loop. You'd set up a complex task, Claude would hit a test failure, and you'd need to manually say "fix it and try again." Over and over. The /goal command eliminates that entirely for well-defined tasks.
The practical use case I'm most excited about: "make all tests pass" as a goal while I work on something else. Or "implement the API endpoint from the spec and verify it handles all edge cases in the test file." Tasks with clear success conditions are perfect for auto-loop.
Agent View is available on Pro, Max, Team, Enterprise, and API plans. The /goal command works everywhere Claude Code runs. If you're already using Claude Code, update and try /goal today. If you're not, this might be the feature that tips you over.
A word of caution from James Shore, who published "You Need AI That Reduces Maintenance Costs" the same day: if AI makes you write code 2x faster but maintenance costs stay the same, you now have 2x the code to maintain. His formula: 2x output requires 0.5x maintenance costs, or you're underwater. Auto-loop makes generation faster. It doesn't automatically make the output more maintainable. Keep that in mind.
Each link below shares sources, entities, or timing with this story.
Within five days of each other, both Claude Code (v2.1.158, May 31) and Cursor (3.6, May 29) shipped remarkably similar architectures for autonomous agent execution. Both use a classifier subagent that reviews each pending action against conversation context and decides: allow...
Go run git log --format=%B -20 | grep Claude-Session in a repo you've been agenting on. If you get hits, you've been publishing a trailer you never agreed to. A 270-upvote PSA on r/ClaudeAI documented that Claude Code appends a Claude-Session: git trailer to commits and drops...
Your Claude subscription is about to get a lot more expensive if you're running agents programmatically. Starting June 15, Anthropic is decoupling all programmatic usage (Agent SDK, claude -p, Claude Code terminal) from the interactive subscription pool. Instead of eating from...
One line in the v2.1.215 changelog, July 19: Claude Code no longer invokes the /verify and /code-review skills on its own. You call them explicitly now (changelog). If your workflow assumed a review pass fired at the end of a task, it doesn't anymore, and nothing told you. Cod...
The dominant orchestration shape is now a deterministic script that fans work across many subagents, has independent agents attack a problem from different angles, then has other agents try to refute the findings until answers converge before anything reaches you. Anthropic la...
If you're on Pro, Max, or Team, the permission prompt you've been hitting Enter on for a year goes away Friday. Anthropic confirmed auto mode becomes the default, replacing per-call approval with a classifier that inspects each tool call for irreversible, destructive, or out-o...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.