Skip to content
Recaply.
Sign inSubmit a tool

LearnTutorials

Claude CodeTutorialsOpen Claude Code

Run parallel coding agents with Claude Code agent view

Run several Claude Code agents at once with agent view: dispatch tasks, peek at progress, reply and review each branch in about 15 minutes.

By Recaply EditorsIntermediate15 min5 stepsUpdated

A hand holds 3 strings, each tied to a small paper kite flying side by side

What you need

Agent view is a research preview, so its screens and keys may still change.

  1. Step 1: Update Claude Code

    2 min

    Agent view only exists in recent versions, and the newest ones fix the most problems.

    1. In your terminal, run claude --version to see which version you have.
    2. Run claude update to install the newest version.
    3. Installed with Homebrew? Run brew upgrade claude-code instead.
    Run this
    claude --version
claude update

    You should see a message that Claude Code updated to a new version, or that it's already up to date.

    The update fails on an npm install?

    Run npm install -g @anthropic-ai/claude-code@latest without sudo. Skip npm update -g, since it may not move you to the newest release.

    The native installer updates Claude Code in the background, so most people are already current.

  2. Step 2: Open agent view in your project

    1 min

    New sessions start in the folder you open agent view from, so open it at the top of your repo.

    1. In your terminal, go to your project folder.
    2. Run claude agents.
    3. If Claude Code asks whether you trust this folder, accept it.
    Run this
    cd [YOUR PROJECT FOLDER]
claude agents

    You should see a full-screen list with an input at the bottom and a row of key hints.

    claude agents lists your subagents and exits?

    Your version doesn't have agent view yet. Run claude update. If it still fails, check that the disableAgentView setting isn't turned on.

  3. Step 3: Dispatch 2 separate tasks

    3 min

    Each prompt starts its own background session, so 2 tasks run side by side.

    1. Type the first task in the input at the bottom and press Enter.
    2. Type the second task and press Enter again. This starts a new session, not a follow-up.
    3. Pick tasks that touch different files, such as tests in one and docs in the other.
    Your 2 prompts, sent one at a time
    Write unit tests for [FILE OR MODULE]. Run them and fix any that fail.

Update the setup section of README.md so it matches the current install steps.

    You should see 2 new rows under Working, each with a short name taken from its prompt.

    Your prompt was turned down as too short?

    Prompts under 4 characters are refused. Describe the task in a full sentence, and name the file or folder it covers.

    From your shell, claude --bg "[TASK]" starts the same kind of session. Add --name to give it a label.

  4. Step 4: Peek at a session and reply

    3 min

    The peek panel shows what a session is doing or asking, without opening the whole chat.

    1. Move to a row with the arrow keys and press Space to open the peek panel.
    2. For a row under Needs input, read the question the session is asking.
    3. Type a reply and press Enter. For numbered choices, press the number, then Enter.

    You should see the session's latest status or question, and your reply sent without leaving the list.

    Your reply doesn't clear a permission prompt?

    Permission prompts can't be answered from the peek panel. Press → to attach, answer the prompt, then press ← on an empty prompt to go back.

    A reply of exactly /stop stops that session at once.

  5. Step 5: Review the work and clean up

    6 min

    Each session saves its work on its own branch, so you review it like any other change.

    1. Press Enter on a row to attach and read the full chat. Press ← on an empty prompt to leave.
    2. When a session finishes, check the pull request number on its row, or ask it where the work is.
    3. Commit anything you want to keep, then press Ctrl+X twice to delete the session.

    You should see finished rows under Completed or Ready for review, each pointing to a branch or a pull request.

    A session won't delete because of unpushed commits?

    Push or merge the commits, then delete it again. Deleting a second time without pushing throws those commits away.

    Claude commits and pushes its own branch when the repo has a remote. It never pushes to main or master, and it never merges.

You get

2 or more Claude Code agents working at once, each on its own branch, all watched from one screen

Try next

Install agent skills in Claude Code6 steps · 5 minInstall an agent skill in any AI coding agent6 steps · 5 minConnect an agent to GitHub with DigitalOcean Action Gateway6 steps · 20 min

Did this guide work for you?

Sources

0 of 5Next: Update Claude Code