From 3.25.0 the build loop can put the plan root it is working under on a shared board and run your own start and end commands, so the team sees which plans agents are working on. Only /devstride:setup agents writes this block, and it is the one setup mode that writes to DevStride: it reads first, shows every change, waits for a typed yes, then creates or adopts the board, the tag, the tag's place in every plan-root type's tag group and a shared table view. /devstride:doctor agents checks it read-only.

Key Shape Default Purpose
activeAgents.boardId string or null null The board plan roots are placed on. null means not adopted yet: the loop places no root until setup agents sets it, but the commands still run.
activeAgents.tagName string "agent active" The tag that marks a root an agent is working under, allowed on every plan-root type.
activeAgents.tagColor string "green" The tag's colour.
activeAgents.staleMinutes positive integer 20 Minutes without a heartbeat after which your presence implementation treats a session as gone; exported to both commands.
activeAgents.commands.start command containing <root> none Run once per build run, right after the root is placed. <root> is replaced only with an item number.
activeAgents.commands.end command, <root> optional none Run at every terminal exit: plan complete, no buildable story left, an explicit stop, an unrecoverable error. A crash runs no end; your own expiry covers it.

Both commands receive ACTIVE_AGENTS_ROOT, ACTIVE_AGENTS_TAG and ACTIVE_AGENTS_STALE_MINUTES, run from the repository root with a 10-second limit, and fail open: a failure is one line in the progress table and never blocks a story. Only the plan root is ever moved onto the board, once per run, with a comment naming the board it came from; never a story. From 3.60.0 the skills that create items (plan, insert-story, insert-defect, rebalance, create-story and create-defect) never copy a board from the parent, so a story, defect or epic planned under a plan that is on the board does not land there beside it; a one-off is offered every board except this one. A one-off has no plan root and does nothing here. An absent or null block writes nothing to DevStride for this feature and runs nothing. The contract is skills/setup/references/agents-mode.md and skills/build-item/references/active-agents.md in the plugin repository.