AssessME Process is a VS Code extension that records your coding process as encrypted
local logs, so your instructor can assess how your work developed over time. It is
built for process-based and in-class programming assessment.
File change history for the languages you enable (full content and diffs)
Typing activity counts in short time buckets
Typing timing: the millisecond time of each single character typed, and of
each single character removed with Backspace/Delete, in tracked files — never
which key or character
Editor changes and window focus events
Run / debug / task events, and program runs from the VS Code terminal, with timing and success/failure (program type only — no command text or terminal output)
Each paste into a tracked file and where it was copied from (same file, another
workspace file, another VS Code window, or outside VS Code) — never the
clipboard's contents
IDs of installed extensions relevant to your course's AI-tool policy
Your GitHub username (if you sign in) and a random VS Code device ID
Milestones you add deliberately
See the Privacy Notice for the complete data description. AssessME Process does not read
your clipboard (except to count the characters of a paste into a tracked file),
does not log key names or typed characters as a keystroke stream,
does not record typing outside tracked files, does not run shell
commands, and does not access files outside your workspace.
Privacy and storage
Logs are stored locally at <workspace>/.assessme/.
Logs are encrypted with AES-256-GCM; the session key is wrapped with your
instructor's public key, so only your instructor can decrypt them.
AssessME Process works fully offline — no network connection is required to record.
Requirements
VS Code 1.120 or newer
An open workspace folder
The extension must be configured with your instructor's public key
(templates/instructor_key.json); otherwise it will not record.
How students use it
Open AssessME Process from the Activity Bar.
Configure the tracked languages if your course requires it.
Start tracking from the Command Palette: AssessME Process: Start.
Code normally (edit, run, debug, test) while it records process events.
Mark milestones when needed.
The status-bar indicator shows when tracking is active. You can stop tracking at
any time with AssessME Process: Stop.
Notes
Start AssessME Process before you begin coding so your process is captured from the start.
Do not delete .assessme/ until your assignment has been reviewed. You can ask
your instructor for a decrypted copy of your own log at any time.
Your school or instructor sets policy, retention, and how logs are used.
