Agents Overview
The Agents module shows your organization's AI agents: the live Fleet of sessions, the Log of what happened to each, the Workflows each running agent follows with the step it is on, and a step timeline on every work item an agent worked.
On this page
The Agents entry in the side menu is where you watch your organization's AI coding agents. It has three views, and a fourth for DevStride staff:
| View | What it shows |
|---|---|
| Fleet | Every agent session running right now, with what it is working on and whether it is alive. It updates live. |
| Log | What happened to each session: when it went quiet, stopped, stalled or recovered, and whether anyone was told. |
| Workflows | The workflow each running agent follows, drawn as phases and steps, with a marker for each agent on the step it is on and what its finished steps said. |
| Machines | DevStride's own engineering machines. Shown to DevStride staff only. |
Opening Agents takes you to the Fleet. The Fleet and the Log used to live under Configure Settings → AI Assistants → Agent Fleet; that address no longer opens, so update any bookmark to the Agents module. Older health notices that linked to the old address no longer open it either; new ones open the Log.
Who sees it#
You see the Agents module when your role holds View Agents Module. The Owner and the Admin role hold it, and so does every role that already held Manage Agent Claims. Members do not hold it unless you add it to their role in Roles & Permissions. Anyone who can open the module sees the details behind each Fleet row, including session addresses, so grant it with that in mind.
A member needs no permission for their own agent sessions to appear in the module.
Fleet and Log#
The Fleet lists each running session with its name, what it is working on, its status and when it was last seen, and the Log keeps every change in a session's health, newest first. How sessions appear, what Working, Waiting on a person, Warning, Stopped and Stalled mean, and who is notified when a session stops are explained in Live status on the Agent Fleet.
Workflows#
Agents → Workflows draws the workflow a running agent follows: its phases from left to right and the named steps inside each. Choose a workflow at the top when your agents follow more than one. Each agent running that workflow appears as a marker on the step it is on right now, and finished steps show how they ended. The page updates as agents report, without a refresh.
Below the picture, Agents on this workflow lists each agent, the step it is on, how long it has been there and the work item it is building. Select a row to open that agent's run: every step it has reported, how each ended, how long it took, its one-line result, a few lines of evidence and its links (a pull request, a commit, a branch). A step that was tried more than once shows its latest attempt, with the earlier ones listed under it.
When no agent is running a workflow, the page says so. A run whose agent has stopped leaves the picture and stays on its work item.
What a step report holds#
A step report is short on purpose: the step's name, how it ended, a one-line result, a few lines of evidence such as counts, commands or a short commit id, and the links the agent already has. It is never a transcript: no conversation, prompt or file contents are sent, and secrets and passwords are removed before anything is stored.
Agents running the DevStride Claude Code plugin 4.1.0 or later report each step of the Build workflow by default; see Plugin updates. Other agents can report through the record_workflow_step tool in the Tool Reference.
Work items you cannot open#
A run for a work item you cannot open still shows its marker and each step's status and times, but its item, results, evidence and links are hidden.
The step timeline on a work item#
Every work item an agent has worked on shows a Workflow steps timeline at the top of its Agent Sessions tab (see Item workspace tabs). Each run is one card: who ran it, when, and how it ended, with its steps grouped by phase, each with its result, time taken, links and evidence. The timeline follows the item's own access: you see it when you can open the item, and anyone who cannot is told the details are hidden.
Machines#
Agents → Machines lists what DevStride's own engineering environment is made of: each machine with its checkouts, cloud stages and database branches, how old each is, when it was last used and what it cost. It is shown only to DevStride staff; other organizations never see it.