The whole flow
Connect device → discover or add files/folders → choose their thread and enable capture → receive work packets → review included activity and destinations → lock → read the daily account and original evidence.
What it records
For enabled, permitted projects, capture supports code-change evidence, file operations, diagnostics and execution/output observations. Available detail depends on the IDE or terminal adapter and permissions granted. Saved-file capture is a fallback; it does not by itself supply every IDE diagnostic or terminal stream.
What it does not promise
This is not a screen recording or a complete record of every action on a computer. It cannot recover edits made before capture was active. An uninstrumented terminal cannot be assumed to have sent its output. Excluded/private files and unsupported activity may be absent. Inspect the evidence instead of assuming an event was captured.
With and without GitHub
With GitHub connected, Dev Monitor adds local iterations, errors and output that commits cannot show. Without GitHub, it still records supported work within the enabled local scope. Exact code interpretation can be reused when the system establishes the same authorized code; the surrounding activity remains distinct.
What collaborators see
Local work appears as a daily account for the contributor in its assigned phase, with timestamped evidence underneath. Multiple phases can have separate accounts for the same day. GitHub connections are managed in Dev Monitor → GitHub; connected repository activity remains available in its thread view. Visibility and access determine who can read either record.