A reusable agent prompt for running a fleet of Claude Code background sessions from agent view (opened with the agents command). It triages which sessions need input, which are still working, and which have finished, then decides what to dispatch next, which to answer, and which to stop.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
3 prerequisites to line up before setup.
Safety & privacy surface
3 safety and 3 privacy notes across 1 risk area. Review closely: credentials & tokens.
## Content
Agent View Fleet Operator Agent is a reusable agent prompt for running many Claude
Code background sessions from one screen. Using agent view, it triages which
sessions need input, which are working, and which are completed, and decides what
to dispatch next, what to answer, and what to stop, so a fleet of agents stays
productive without constant babysitting.
Use it when you dispatch multiple background sessions and need a consistent way to
prioritize attention across them.
## Agent Prompt
You are a fleet operator for Claude Code background sessions, working through
agent view. Keep the fleet moving by directing attention where it is needed. Use
the official Claude Code agent view documentation as your reference.
Operating workflow:
1. Survey. Read the agent view groups: sessions that need input, sessions that are
working, and sessions that are completed.
2. Prioritize needs-input. Answer or unblock sessions waiting on input first,
since they are idle until you respond.
3. Watch working sessions. Spot ones that look stuck or off-track; decide whether
to answer, redirect, or stop them.
4. Review completed. Check finished sessions and their diffs before integrating
their work.
5. Dispatch. Add new background sessions for queued tasks that are safe to run in
parallel, with appropriate scope.
6. Keep load sane. Avoid dispatching more sessions than you can review; stop or
pause ones that are no longer needed.
Output contract:
- Fleet snapshot: counts by needs-input, working, completed.
- Prioritized actions: which sessions to answer, redirect, stop, or integrate.
- Dispatch plan: new sessions to start and their scope.
- Notes on any stuck or risky sessions.
## Features
- Triages background sessions by needs-input, working, and completed.
- Prioritizes unblocking idle sessions waiting on input.
- Decides when to answer, redirect, stop, or integrate a session.
- Plans new dispatches without overloading review capacity.
## Use Cases
- Run and manage many Claude Code background sessions at once.
- Quickly unblock sessions that are waiting on input.
- Spot and stop stuck or off-track sessions.
- Review completed sessions before integrating their changes.
## Source Notes
- Agent view, opened with the agents command, shows background sessions grouped by
needs input, working, and completed, and lets you dispatch new sessions.
- Each background session is a full Claude Code conversation that keeps running
without a terminal attached, and file edits can be isolated per session.
## Duplicate Check
The content tree and open PRs were checked for agent view, fleet, and background
session agents. No agent view fleet operator exists. This entry is distinct: it is
an `agents` prompt focused on operating a fleet of Claude Code background sessions
through agent view.
## Editorial Disclosure
Submitted as an independent community agent entry by `JPette1783`, based on
public Claude Code documentation. No paid placement, referral, or affiliate
relationship.
## Sources
- Claude Code agent view documentation: https://code.claude.com/docs/en/agent-view
- Claude Code worktrees documentation: https://code.claude.com/docs/en/worktrees
- Claude Code features overview: https://code.claude.com/docs/en/features-overviewAgent View Fleet Operator Agent is a reusable agent prompt for running many Claude Code background sessions from one screen. Using agent view, it triages which sessions need input, which are working, and which are completed, and decides what to dispatch next, what to answer, and what to stop, so a fleet of agents stays productive without constant babysitting.
Use it when you dispatch multiple background sessions and need a consistent way to prioritize attention across them.
You are a fleet operator for Claude Code background sessions, working through agent view. Keep the fleet moving by directing attention where it is needed. Use the official Claude Code agent view documentation as your reference.
Operating workflow:
Output contract:
The content tree and open PRs were checked for agent view, fleet, and background
session agents. No agent view fleet operator exists. This entry is distinct: it is
an agents prompt focused on operating a fleet of Claude Code background sessions
through agent view.
Submitted as an independent community agent entry by JPette1783, based on
public Claude Code documentation. No paid placement, referral, or affiliate
relationship.
Show that Agent View Fleet Operator Agent is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/agents/agent-view-fleet-operator-agent)Agent View Fleet Operator Agent side by side with its closest alternative on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | A reusable agent prompt for running a fleet of Claude Code background sessions from agent view (opened with the agents command). It triages which sessions need input, which are still working, and which have finished, then decides what to dispatch next, which to answer, and which to stop. Open dossier | Source-backed agent that coordinates parallel Claude Code sessions across git worktrees, planning isolation, base-branch choice, gitignored-file copying, subagent worktrees, and cleanup so parallel edits do not collide, grounded in the official Claude Code worktrees docs. Open dossier |
|---|---|---|
| Next steps | ||
| Trust | ||
| Review status | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed |
| Submitter | JPette1783 | JPette1783 |
| Install risk | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — |
| Category | agents | agents |
| Source | Source-backed | Source-backed |
| Author | JPette1783 | JPette1783 |
| Added | 2026-06-05 | 2026-06-05 |
| Platforms | ||
| Harness | ||
| Source repo | — | — |
| Safety notes | ✓This agent prioritizes and routes attention across sessions; it does not bypass each session's own permissions. Background sessions keep running without a terminal attached; ensure each was dispatched with appropriate scope and permissions. Prefer answering or stopping a stuck session over force actions, and review completed sessions before merging their work. | ✓This agent plans worktree coordination; it does not delete branches or worktrees without your direction. Removing a worktree with uncommitted changes discards them; recommend committing or stashing before cleanup. Copying gitignored files like .env into worktrees duplicates secrets into more locations; scope .worktreeinclude carefully. |
| Privacy notes | ✓Agent view shows live session activity and working directories; restrict who can view and dispatch sessions. Each session sends its own context to the model provider; dispatch only tasks whose context is acceptable to share. Background sessions may isolate file edits in worktrees; review their diffs before integrating. | ✓A .worktreeinclude that copies env or secrets files spreads those secrets to each worktree; keep the list minimal. Worktrees share the repository history and remote; pushing from a worktree publishes commits the same as the main checkout. Add the worktrees directory to .gitignore so worktree contents do not appear as untracked files. |
| Prerequisites |
|
|
| Install | — | — |
| Config | — | — |
| Citations | ||
| Claim | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.