CIT Course Tools

Record course-project development locally, replay how code changed, and use the CIT Course Tools simulator and testing workflow inside VS Code.

The dockable Recording & Tools panel brings together lab selection, Start/Resume/Pause Recording, Open Replay, submission packaging, and an embedded terminal interface. The Python companion remains responsible for scaffolding, model simulation, testing, and packaging.

Explore development history

Use the recording timeline to step through changes or play them chronologically. Switch between recorded files at the same point in time. Replay includes line numbers, cursor and selection displays, adjustable speed, and persistent event-size markers. Valid new events refresh automatically.

Each lab keeps its active recording in labs/labNN/logs/recording.jsonl. The lab identity remains in the events and Replay heading. Existing prefixed logs are copied safely and retained as migration backups; conflicting histories stop migration or packaging rather than overwriting either file. Starting and resuming require confirmation. Recording pauses remain visible in history; changes made while paused are unobserved snapshots, not reconstructed typing.

The demonstration uses sample code. Event colors indicate size, not detected AI misuse. View the static replay screenshot if you prefer not to view animation.

Keep course tools close to your code

Open the Python TUI inside the dockable panel, or use Open in Terminal as a fallback. Select the active lab from the panel or TUI. Use the Workbench for guided simulator interactions and the Tests view to verify your harness against your instructor's lab scenario.

Package Submission calls the Python package and collects the selected lab's artifacts and recording history into a named ZIP. Packaging does not upload it. Instructors can review extracted recording files through the Command Palette.

More demonstrations: embedded simulator and event-size history. These are short looping GIFs from the September 2026 preview.

Getting started

Upgrading from a local prototype? Pause recording and disable/uninstall cit-course-local.cit-course-recorder before enabling this extension under jeffm-courseware. They are different extension identities and can otherwise coexist. Keep your workspace and recording files; recheck interpreter settings and recording consent after installation.

1. Open a trusted, single-folder course workspace in VS Code.

2. Install the compatible Python companion in the interpreter you will use:

   python -m pip install --upgrade "cit-course-tools[terminal]==0.3.2"
   

3. Open CIT Course Tools in the Activity Bar. Initialize the workspace if needed, then select a lab. Your instructor supplies course-specific materials.

4. Choose Start Recording, read the notice, and confirm. Check the recording status before editing your project files.

5. Use Open Replay, Open Embedded TUI, and Package Submission as needed.

The extension uses the Microsoft Python extension's selected interpreter when available, otherwise python on PATH. CIT Recorder: Python Path can specify an executable explicitly. Stable Python package 0.3.0 is not sufficient for these controls. Windows embedded terminals require the terminal extra. This release has been verified natively on Windows; Linux/macOS native validation is still pending. Multi-root and virtual workspaces are not supported.

Recording scope and responsible review

Recording is visible and local. It covers supported text/code under project/ and the selected labs/labNN/ folder, including evaluation.md (.py, .js, .ts, .html, .css, .md, .txt, .json, .yaml, .yml), editor changes, cursor/selection activity, saves, and supported copy/cut shortcuts. It does not read the system clipboard or record system-wide keystrokes. Some menu actions, keybindings, and extensions can bypass shortcut observation.

Generated logs/results, JSONL files, archives, hidden files, dependencies and build/artifact folders are excluded. External file changes are unobserved snapshots, not reconstructed typing. Editor changes can come from a person, formatter, completion or another extension; their source is not proven.

Compatibility: extension 0.1.15 requires Python cit-course-tools 0.3.2, which provides recording-layout 3. Upgrade both companions together. The earlier extension 0.1.14 / Python 0.3.1 pair uses layout 2 and cannot be mixed with the new pair.

Colors indicate event size: green at 2 characters, yellow at 100, and red at 1,000, with intermediate shades. They do not detect AI misuse. An insertion could be a paste, completion, or another edit; copying and cutting can be normal development. Baselines, gaps, and local histories are not proof of authorship.

No recording uploads or background telemetry are performed by this extension. Git, cloud-sync software, and services contacted through your own harness remain separate. Recordings contain source code: do not put credentials in it. Review submission contents before sharing. Recording pauses after reopening VS Code and stops visibly if a write fails or a size limit is reached; existing logs are preserved. Instructors should explain recording expectations before graded work.

Support

Email jeffm-courseware+support@outlook.com with versions, reproduction steps, and a non-sensitive error message. Contact your instructor for grading or course-policy questions. Do not attach student recordings, submission archives, or credentials to an initial support request.

License

MIT. Bundled third-party components retain their respective license notices.