From 4.1.0 build-item reports, as it runs, which step of its Build workflow it is on and how the last step ended: a one-line result, a few lines of evidence and the links it already holds, never session text, a prompt or a file's contents. The reports appear in DevStride's Agents module and on each item's step timeline. Reporting only observes: where a report cannot be taken (an older server, no permission, no network, no DevStride connection) nothing more is sent for that run, nothing is said, and the work never waits or stops because of it.

Key Shape Default Purpose
workflows absent, { "provider": "devstride" }, { "commands": { "report": "<command>" } }, or null absent: on, through the agent's own DevStride connection null switches reporting off for the repository.
workflows.provider "devstride" "devstride" Report through the agent's DevStride connection.
workflows.commands.report string absent A repository with its own store names a command instead. It receives each report as one JSON object on stdin and prints OK, ABSENT, FORBIDDEN, UNREACHABLE or ERROR as its first line. A block naming both a provider and a command uses the command.

To switch reporting off on one machine, set DEVSTRIDE_WORKFLOWS=0 (false, off and no also count) in its environment.