Two Game‑Changing Features in Claude Code’s 10‑Day, 10‑Release Sprint

Why This Week’s Updates Were So Aggressive

The version number jumped from 2.1.140 to 2.1.150, delivering ten releases in ten days (missing 2.1.146). The surge coincided with Anthropic’s "Code with Claude" conferences in San Francisco and London, where the company bundles several weeks of work into a single launch.

Agent View: An In‑Terminal Agent Dashboard

Introduced in 2.1.139, Agent View groups all Claude sessions by status—Working, Needs input, Completed—allowing multiple sessions to be visible at once.

Background tasks can be sent with Ctrl+B, and the same sessions appear on the Claude mobile app.

Real‑world example: The author sent a long test‑generation task to the background, checked progress on a phone while getting coffee, and then accepted the diff directly on the desktop.

Critiques from the r/ClaudeCode subreddit note that the session list is global and lacks workspace filtering, and session restoration can be flaky.

How to Open Agent View

Enter: claude agents Exit:

Esc — return to a normal terminal

Inside Agent View, common shortcuts:

↑/↓ — move in the session list

Enter/→ — open the selected session

Space — open preview panel

Ctrl+T — pin the session

Ctrl+R — rename

Ctrl+X — stop or delete

Shift+Enter — dispatch a new task and enter it

? — show all shortcuts

Dispatch a background task:

claude --bg "Refactor user‑auth module, support OAuth2 + JWT"

View all background tasks: /tasks Filter by project (v2.1.141+): claude agents --cwd ~/projects/my-app Set permissions and model:

claude agents --permission-mode plan --model opus

/goal: Turning Vague Objectives into Trackable Task Maps

Added in 2.1.142, the /goal command converts a high‑level request into a hierarchy of subtasks with explicit states (pending → in_progress → completed) that appear in Agent View.

/goal Refactor user‑auth module, target OAuth2 + JWT refresh

Real‑world example: The author let Claude clear a backlog of issues; pending tasks indicated needed confirmations, while completed tasks could be reviewed via diffs without remembering the conversation context.

The main benefit is reducing context loss on long tasks, not merely saving time.

Using /goal

Set a goal:

/goal All tests pass, lint clean, CHANGELOG updated

Claude creates subtasks automatically; each completed subtask triggers a TaskUpdate marking it completed. Natural‑language controls adjust priority, pause, or delete tasks.

"Adjust priority, do X first" — re‑order tasks

"Stop, direction wrong" — abort and clear list

"Skip this" — mark as deleted

Check current goal status: /goal The output shows goal conditions, runtime, turn count, token usage, and the latest evaluator judgment.

Non‑interactive mode (for CI/automation): claude -p "/goal All tests pass and lint clean" Claude runs until all conditions are satisfied or the user interrupts with Ctrl+C.

The underlying mechanism reuses the TaskCreate/TaskUpdate toolchain, so each subtask’s state transition is visible in Agent View.

Why Combining Agent View and /goal Matters

/goal

structures vague intent into concrete tasks.

Agent View visualizes and schedules those tasks.

This shifts the developer role from waiting for Claude’s answers to orchestrating a fleet of agents: assign goals, monitor status, resolve blocks, and accept results.

Anthropic is moving from selling a model to selling a "developer‑AI collaboration workflow". The decisive factor for daily efficiency is no longer a single accurate answer but the system’s ability to handle long‑running, multi‑task, team‑style collaborations.

Final Recommendation

If you use Claude Code, prioritize learning Agent View and the /goal command. Test them on a substantial task—such as refactoring a module, adding a suite of tests, or cleaning up a batch of issues—so you can experience managing state with Agent View and regaining context via /goal.

After a full run, you’ll see that Claude has become a manageable work partner rather than just a code‑writing assistant.