Skip to content

Day 25 of 52 · about 20 min · Subagents

Hand off tasks and track them in agent view

When you have three separate tasks, doing them one after another means waiting on each. Agent view lets you hand them all off, do something else, and step in only when a session needs you or is done.

You’ll finish with

  • Two tasks running as background sessions while you do something else
  • A reply sent from peek, and a finished session reviewed

You’ll need

  • Agent view is a research preview: its screens and shortcuts may change.
  • Background sessions use your plan’s usage like interactive ones, so two at once use it about twice as fast.
  • A git repository with at least one commit, so sessions that edit files get their own worktree.

Before you start

Tell us about your setup and the steps change to fit it. Your answers stay in this browser, and you can change them at any time.

Which system are you on?

Commands differ between systems. Pick the one you’ll run Claude Code on.

The steps

One step at a time. When a step’s check matches, tick it and the next one opens.

0 of 4 steps done0%
  1. Step 1 of 4: Open agent view

    Start the screen that lists every background session.
    Terminal

    Run: claude agents

    What happens: In a folder you haven’t trusted yet, the trust prompt comes first.

    Run it from your project folder. New sessions start there.

    Check it worked

    Agent view fills the terminal: empty groups and an input at the bottom. Esc takes you back to the shell.

    If it didn’t work

    It prints your subagents and exits

    Run claude update. Still exits? Check disableAgentView and CLAUDE_CODE_DISABLE_AGENT_VIEW.

  2. Step 2 of 4: Dispatch two tasks

    Each prompt you send starts its own background session.
    In Claude Code

    You type: List every error message the quote command can print and the input that causes it

    You type: Add a short Options section to README.md that explains --discount and --vat

    What happens: Press Enter after each one. The second edits a file, so it moves into its own worktree first.

    One question that only reads, one task that edits.

    Check it worked

    Two rows appear, each with a one-line summary that updates as the session works.

  3. Step 3 of 4: Peek and reply

    Check a session without opening it, and answer if it waits on you.

    In order:

    1. You

      Select a row

      ↑ / ↓

    2. You

      Peek

      Space shows its latest output or question

    3. You

      Reply

      Type and press Enter

    4. You

      Attach

      Enter or → opens the full session

    Attach only when you need the whole conversation.

    Check it worked

    Peeking at the finished question shows its answer. A Needs input row shows its question.

    If it didn’t work

    Your reply doesn’t answer a permission prompt

    Permission prompts can’t be answered from peek. Attach with → and answer there.

  4. Step 4 of 4: Review the result, then stop or delete

    Attach to the README session, read its report, and decide what to keep.

    Its recap and report say where the work is, such as a branch in its own worktree. Unless your CLAUDE.md says you handle git, it has committed there. ← on an empty prompt takes you back.

    Stop: Ctrl+X once

    • Ends the session
    • The row moves to Completed, with a grey icon

    Delete: Ctrl+X twice

    • Removes the row; the transcript stays for claude --resume
    • Removes the worktree Claude made, uncommitted changes included
    • Asks again before discarding unpushed commits
    Merge or push what you want to keep before you delete.

    Check it worked

    You found the README change on its branch, and the list shows only the sessions you kept.

Finish · 4 of 4 steps to go

You can hand off work and check back later

Background sessions keep running after you close agent view. Run claude agents to see them again.

What you’ll have checked

  • Two sessions dispatched from one screen
  • A finished session reviewed

Lesson updates by email

Get lesson updates by email

Leave your email and we’ll tell you when we add or update a lesson.

We’ll email you when we add or update a lesson. We use your email only for this. Privacy policy

Claude Code for your team

Want Claude Code set up across your team?

HorizonLux sets up and repairs Claude Code for teams: CLAUDE.md rules, hooks that enforce them and reviewed MCP servers. Book a free call to talk it through.

Questions

Questions about Day 25

Is `claude agents` the same as `/agents`?

No. `claude agents` opens agent view for background sessions. `/agents` inside a session points you to your subagent files.

Sources

Checked against the official Claude Code docs on .

Independent resource, not affiliated with Anthropic. HorizonLux wrote this lesson; Claude Code is made by Anthropic.