Claude Code /goal and claude agents
Yesterday I had multiple Claude Code sessions running at the same time. But each session kept asking me "next?" every single turn, so I was bouncing between tabs hitting Enter and losing my mind.
All that inefficiency disappeared with one line: the new /goal command.
Written from the perspective of someone using the Week 20 update (May 11–15) — agent view + /goal — every day.
01. All my sessions, one screen (claude agents)
I used to flip between five terminal tabs and constantly lose track of which session was doing what.
Yesterday I ran claude agents for the first time. Every session lined up in one view, each showing running / blocked on you / done at a glance. I could immediately see where I needed to respond.
What I noticed: That single blocked on you label made a surprisingly big difference for me. Before, I had to peek into every tab to figure out where things were stuck. Now it's right there.
02. My biggest frustration, gone with /goal
The thing that bothered me most about Claude Code was the per-turn stop-and-ask. One "should I proceed?" would be fine, but the repetition wore me down. With multiple sessions running, that fatigue multiplies.
I tried /goal for the first time yesterday. My approach was simple.
$ claude
> /goal Keep going until this PR review is done and all tests pass.
# Claude grabs the completion condition (tests passing)
# and from then on, doesn't ask every turn — it just runs
# Only stops on blocked on user (= when a real decision is needed)
The impact was huge. Once I specified the completion condition, I didn't have to babysit it anymore.
03. The time savings I felt
I timed how long my per-turn answers were taking. Each response averaged 10–15 seconds. Drag one task through about 10 turns and that's 1–2 minutes per session. With five sessions, multiply by five.
After delegating with /goal, my time spent dropped to essentially zero. I clawed back about 10 minutes of attention.
And not hitting unnecessary Enters dropped my fatigue sharply.
04. Cases where /goal doesn't work well
After a few days of use, /goal worked best when the completion condition was clearly verifiable.
Tests passing, build succeeding, a specific file under N lines — cases like that.
On the flip side, it didn't suit me for the exploration or ideation phase.
In a "how should I even approach this" flow, answering every turn and thinking together actually produced better results.
My take: /goal is a tool for "execute to the finish once the direction is set," not for "finding the direction."
Sources
- Claude Code — What's New (Week 20, May 11–15, 2026)
- Anthropic — Enabling Claude Code to work more autonomously
This is a first-person review after a few days of hands-on use. I received no sponsorship of any kind from Anthropic.
Originally posted at jessinvestment.com
Original with full infographics and visual structure: https://jessinvestment.com/claude-codes-new-goal-command-killed-my-per-turn-confirmation-loop/
