# Command Center Source: https://www.hyperagent.com/docs/concepts/command-center > For AI agents: the documentation index is at https://www.hyperagent.com/llms.txt and the complete documentation in one file at https://www.hyperagent.com/llms-full.txt. Any docs page is also served as Markdown by appending `.md` to its URL. The cockpit for running many agents at once: catch what's waiting on you, see what's running, and track cost and quality across the fleet, then drill into the one that needs you. You're running several agents, and most of them work while you're not watching: one on a 7 AM schedule, one answering in Slack, one triggered by a webhook. You can't open each one to check on it. The **Command Center** is where you don't have to: one page that catches what's waiting on you, shows what's running, and tracks cost and quality across every agent at once. A blocked approval just waits, a runaway schedule just spends, and quality drifts with nobody in the thread. Checking the Command Center like an inbox is how an unattended fleet stays a managed one. ## It's the fleet view; one agent's view is its Activity tab [#its-the-fleet-view-one-agents-view-is-its-activity-tab] The Command Center is workspace-wide: every agent, one dashboard. That's what makes it different from an agent's [Activity](https://www.hyperagent.com/docs/concepts/agents/activity) tab, which shows a single agent's runs. You live here when you operate many agents and drill into Activity or a thread when one needs a closer look. Open it at `/command-center` from the user menu; a team workspace has its own Command Center over the team's shared fleet, and **Refresh dashboard** re-pulls the data in place. ## Clear what's waiting on you [#clear-whats-waiting-on-you] The first thing to check is whether anything is blocked on a decision from you, because an unattended agent that hits an approval or a proposed change just waits. **Needs Attention** collects exactly those items so they don't sit unseen in a sub-page. Its lead row summarizes the workspace's pending improvements and opens the queue at `/improvements`; each item below shows the start of its description and a type tag, like `New Rubric`, and links straight to where you act on it. Clearing this list is the main thing you *do* here. What these proposals are and how you review them is [Learning](https://www.hyperagent.com/docs/learning). ## See what's running right now [#see-whats-running-right-now] Before you kick off new work, **Active Operations** tells you what's already in flight across the workspace: the agent runs executing right now. When it reads **"All quiet — no active operations."**, nothing is running, which is the calm state, not a missing one. It's the fastest way to know whether an agent is still mid-task before you pile on. ## Catch a runaway cost [#catch-a-runaway-cost] Cost is the number that surprises operators of unattended fleets, so the Command Center keeps it in view. The **Total Cost** figure sits in the headline stats, and **Cost Breakdown** shows where the spend is going; **Open cost portfolio** drills into cost per agent, which is how you find the one schedule quietly running up a bill and decide whether it's worth it. ## See whether quality is holding [#see-whether-quality-is-holding] Agents drift, and a scheduled agent can degrade for weeks before anyone opens a thread. **Avg Score** in the stats and **Score Trends** over time are the early warning: a criterion sliding down is your cue to open that agent, read a low-scoring run, and fix it. The scores come from the rubrics you set in [Rubrics and evaluations](https://www.hyperagent.com/docs/learning/rubrics-and-evaluations). ## Find the agent to dig into [#find-the-agent-to-dig-into] The Command Center points; the detail lives one click away. The **Agent Roster** lists every agent with a **Search agents...** filter, and **Recent Runs** is the cross-fleet feed of what just happened. An agent opens to its own page, a run opens its thread, and that agent's full history is its [Activity](https://www.hyperagent.com/docs/concepts/agents/activity) tab. So the loop is: notice it here, drill in there, act in the thread. ## FAQs [#faqs] When you're minding more than one agent. The Command Center is the fleet view: what's blocked, what's running, and cost and quality across every agent. An agent's [Activity](https://www.hyperagent.com/docs/concepts/agents/activity) tab is one agent's run history, the place you drill into after something here catches your eye. Because nothing is running, which is the good case. The card reads "All quiet — no active operations." when the workspace has no runs in flight, and fills the moment an agent starts working. The workspace's pending improvement proposals, the learning suggestions and rubric proposals waiting for review. The card exists so a decision that's holding up an agent doesn't hide in a sub-page; each item links to the queue at `/improvements`. Yes. A team workspace has its own Command Center reporting on the team's shared fleet the same way your personal one reports on yours.