What a session records
A session is a recording, and you should know exactly what is in it before you press Start. This page describes what the software does — nothing here is aspirational.
What lands in the record
| What | In detail |
|---|---|
| Your prompts and interrupts | The full text of every message you send the agent, and the moment you stop it mid-turn. |
| The agent’s replies, tool calls and results | What it said, which tool it invoked with which input, and what came back — including whether the call failed. |
| Files you open, and for how long | The path and the dwell time. Closing a file and switching editors are recorded too. |
| Your edits, as diffs | Edits are batched per file and stored as a unified diff, so the content you write is in the record. It is not a keystroke log: there is a couple of seconds’ debounce and no character-by-character capture. |
| Where you navigated | Go-to-definition and symbol jumps — from, to, and the symbol. |
| Terminal commands | The command line you ran in the session terminal and its exit code. Anything you type into that terminal is part of the record, so treat it as observed. |
| Model choice, tokens and cost | Which model you picked, and the usage and spend it produced against the session’s budget. Also whether and when you compacted the context window. |
| The session’s own bookkeeping | When the invite was opened, when you pressed Start, and when you submitted or the clock ran out. |
That is the whole list. The record is a flat log of those events, each with a timestamp and an actor — you or the agent — and the replay is built from nothing else.
What is not captured
The premise of this product is that you will be asked to explain your own work, which makes surveillance unnecessary. So there is none:
- No camera, no microphone, no screen or video recording of any kind.
- No keystroke logging, no mouse tracking, no eye tracking, no clipboard capture.
- No screenshots and no capture of other windows, tabs or applications.
- Nothing from your own computer. The workspace runs on our infrastructure; on your machine there is only a browser tab.
- No browsing history, and no attempt to identify you beyond the invite you were sent.
- No proctoring, and no attempt to detect whether you used an agent — you are given one on purpose.
Your work and the agent’s are kept apart
You and the agent write to the same files, so the recorder decides which of you made each change. Agent writes are on the timeline as the tool calls they were; they are never attributed to you as an editor.edit. That works in your favour: it is what makes a small, surgical hand edit visible as yours instead of being lost in a large generated diff.
The record cannot be edited afterwards
When you submit — or when the clock runs out — we snapshot the tree, revoke the session’s model key, and seal the log. Sealing is enforced where the writes happen: further events are refused. Nobody adds to it, edits it or deletes from it afterwards, and that includes the company that invited you and it includes us.
Reports exported from a session are immutable snapshots for the same reason. Exporting again creates a new one; there is no edit and no delete. An archive that can be rewritten after the fact is worth nothing.
A disposable VM, one per session
Your workspace is a virtual machine created when you open the invite and destroyed when the session ends. It is yours alone — not a container shared with another candidate — and it runs in an EU region. If you close your laptop mid-session the machine suspends and resumes when you come back, so the filesystem survives.
Nothing dials into that machine from the internet; the editor is reachable only through our control plane, and only while your session is live. Egress is open so you can search, fetch and install packages — mail and outbound SSH are blocked, which is about abuse, not about you. The model credential inside the machine is scoped to your session, capped, and not readable from your shell.
The company that invited you
The recording belongs to the account that sent your invite, and that account is the only one that can read it. Recordings are not pooled, not shared between companies, and not used to compare you against anyone else’s candidates. Who inside that company watches your session, and how long they keep it, is their decision to tell you about.
If something here is unclear, ask before you press Start — set-NEXT_PUBLIC_ACCESS_EMAIL@example.invalid.