+ Use this guide to obtain a CodeChat Capture access token, store it in the + CodeChat VS Code extension, and turn on dissertation study capture. +
+ ++ You need a Mississippi State email address, the class code supplied by + the instructor, and the CodeChat Editor extension installed in Visual + Studio Code. +
+msstate.edu.+ Copy the entire token from the email exactly as shown. +
+Ctrl+Shift+P.Enter.+ You can also run CodeChat Editor: Enter Capture Token + directly from the Command Palette. +
++ A valid token should produce a participant ID and an instance ID in + the capture status details. +
+Ctrl+Shift+P.+ Consent persists. Record Study Events is session-local, + so turn it on again after reopening VS Code. +
++ The CodeChat capture status bar item shows the current capture state. + You can click the status bar item or run + Manage CodeChat Editor Capture to see more detail. +
+ +| Status | +Meaning | +What To Do | +
|---|---|---|
| Capture: Remote | +Capture is on and events are reaching the remote capture system. | +Continue working normally. | +
| Capture: Uploading | +CodeChat is actively uploading queued capture events. | +Continue working normally. | +
| Capture: Queued | +Events are stored locally and waiting to upload. | +Check your network connection if this does not clear. | +
| Capture: Starting | +The local CodeChat server is starting or reconnecting. | +Wait a few seconds, then recheck the status. | +
| Capture: Waiting | +CodeChat is checking capture readiness or waiting for a server response. | +Wait a few seconds, then validate the token if this status does not clear. | +
| Capture: Off | +Capture recording is off for the current VS Code session. | +Run Manage CodeChat Editor Capture, then turn recording on. | +
| Capture: Error | +CodeChat encountered a local or remote capture error. | +Open the CodeChat Capture output channel and contact the instructor or research team if it persists. | +
capture token status: Accepted participant_id=... instance_id=...
+ After turning capture on and editing a file, the same output channel
+ should show queued capture events such as session_start,
+ save, write_doc, or write_code,
+ depending on the activity performed.
+
| Symptom | +Likely Cause | +Fix | +
|---|---|---|
| No token email arrives. | +The email address was mistyped, the message went to junk mail, or the current AWS dev email service is limited to verified recipients. | +Confirm the email address, check junk mail, then request another token. | +
| The portal rejects the request. | +The email is not an msstate.edu address, or the class code is wrong. |
+ Use your Mississippi State email address and enter the class code exactly as provided. | +
| Capture: Waiting for token | +No accepted token is stored in VS Code. | +Run Manage CodeChat Editor Capture, then Enter Capture Token. | +
| Capture: Waiting for consent | +Recording was turned on before consent. | +Run Give Consent and Record Study Events, or turn consent on separately. | +
| Capture: Paused | +Consent is on, but Record Study Events is off for this VS Code session. | +Run Manage CodeChat Editor Capture, then Turn Record Study Events On. | +
| Capture: Token rejected | +The pasted token is wrong, incomplete, or revoked. | +Clear the token, paste it again from the email, then validate it. | +
| Capture: Disabled by portal | +The participant or instance is disabled in the capture database. | +Contact the instructor or research team. | +
| Capture: Service unavailable | +The network or remote capture system is temporarily unavailable. | +Keep working. If the same token was previously accepted, CodeChat will keep matching events queued locally and upload them when the service returns. If this status does not clear, update to the current CodeChat build. | +