Replay an Assessment Session

Every attempt can be replayed. Not a video — a reconstruction from the event log, which means it is searchable, skippable, and linked to the report.

What the replay shows

• Prompts the candidate sent, and the agent's responses
• Tool calls the agent made and what they returned
• Files as they changed, with diffs
• Changes that were reverted
• Terminal commands and their output
• Test runs and results
• Suggestions accepted and rejected
• Time between events

How to use it

Jump from a finding. Every evidence-backed finding in the report links into the replay at the moment it happened. This is the fastest route: read the concern, click through, see the thirty seconds it came from.

Watch the first five minutes. How a candidate opens a task is revealing. Did they read the code, run the tests, and look around? Or did they paste the brief into the agent and hit go?

Watch the last ten minutes. Did they review what they were about to submit, or did they stop when the tests went green?

Search the prompts. Reading a candidate's prompts is close to reading how they think. Precise, contextual instructions look very different from "make it work".

What you will not see

No webcam, no microphone, no screen recording, no keystroke capture outside the workspace. Ducker records the work, not the person. That is stated plainly to candidates in the Candidate Privacy Notice.

Sharing

Replays are visible to team members whose role grants access to candidate data — see Roles and Permissions. Treat a replay as you would any other candidate record: it is personal data, and your retention policy applies to it.