Fleet docs v0.2.0-rc.448

Home: your sessions

The first screen of the page. It shows the sessions that you started, what needs you, and one line of health. Every other panel is folded below it and loads only when you open it.

How to read it

  • Needs you is at the top, and only when something waits for you: an agent that is blocked, asks a question (needs input), is stuck or lost, or failed in the last 24 hours. Each line names the session it belongs to ("in lead-1") and has the buttons to answer, send a message or stop. An item is listed here and nowhere else on the first screen.
  • Your sessions lists what a person started: a chief, a chat, an agent started from a terminal, and a terminal session that ran fleet spawn ("terminal"; "session ended" when that session is gone and its workers still run). Each row has a state dot, the name, one line of its latest report, and how long ago it was active. The name opens the session in Chat.
  • Channels: when the sessions carry a channel (a named area such as Fleet or Data), the list is grouped by channel, with "Other" for sessions that have none. With no channel on any session, the list is flat.
  • The worker count under a session ("6 workers · 2 working · 1 needs you · 2 finished") counts every agent below it, at any depth. Click it to list them in place.
  • show finished shows the sessions and workers that are done, stopped, parked, ended, or failed more than 24 hours ago. They are hidden by default. The choice is kept in the browser.
  • The health strip shows the nodes that are up, each box's load and free memory, and your usage windows. Red is a problem: a node down, a box below its memory alarm or loaded above its cores.
  • Graph opens the Graph page, the live map of the fleet. The agent graph that used to be a panel here is there now.
  • The folded panels: Processes, Boxes (each box and the monitor), Claude usage, Builds, Projects and deploys, and Log. A panel the server has no data for is not shown.

What it reads

The page asks for /api/state?view=home every 15 s. That answer has three sections: home, fleet and usage. While a folded panel is open, the page asks for the full /api/state.

sections.home.data:

Key What
sessions Each session: id, label, kind, project, channel (when the registry has one), health, shown, line (its report, else what it does), last_activity_min, finished, needs, can, workers (the same fields, plus under), worker_counts (total, live, finished, by_health, not_listed)
needs The items that need a person, sessions and workers, with session
counts sessions, finished_sessions, not_listed
boxes One line per box: host, load1, cores, cpu_pct, mem_available, mem_total, mem_low, stale
panels The section names of the full state, so the page knows which folded panels to show

At most 40 finished sessions and 15 finished workers per session are listed; the rest are counted. No dollar figures and no token counts are in the section.

The section: fleet/internal/dash/home.go. The page: fleet/internal/web/index.html.