Claude Code adds /goal to run until tasks are complete

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.

Claude Code adds /goal to run until tasks are complete

TL;DR

  • Claude Code 2.1.139: Added /goal command, per Daniel San’s X post
  • /goal behavior: Keeps working across turns until a completion condition is met
  • Supported modes: Works in interactive, -p, and Remote Control
  • Stop/continue modes: /goal outcome-based; /loop clock-based; stop hooks script-based; normal chat manual follow-up
  • Template command: npx claude-code-templates@latest --setting statusline/vercel-deployment-monitor for Vercel deployment monitor status line
  • Community feedback: Interest in multi-step handoff; concerns about reliability, stale context, vague stop conditions, and usage/token caps

According to a post on X, Claude Code 2.1.139 has added /goal.

The command appears to let Claude keep working across turns until a completion condition is met, and the post claims it works in interactive mode, -p, and Remote Control.

The post also outlines how Claude Code determines when to continue and when to stop. These modes are now listed as:

  • /goal waiting for an outcome
  • /loop waiting for the clock
  • stop hooks waiting for a script

/goal was also added last week on Codex, where it drew positive feedback from the community, along with a practical path from repeated turn-by-turn prompting to a single declared exit condition. One reply described the appeal as finishing work without constant intervention, though the same thread repeatedly returned to the practical constraint of token and usage limits.

Source: X post

Continue the conversation on Slack

Did this article spark your interest? Join our community of experts and enthusiasts to dive deeper, ask questions, and share your ideas.

Join our community