Do your Kritik programming activities in VS Code — write, run, and hand in your work
without leaving the editor, with authorship recorded as you go.
Features
Authorship tracking. Every edit is attributed as written by you, generated by
Kritik AI, AI-generated then revised, or pasted. That record travels with your
submission, so your instructor can see how the work was produced.
Kritik AI. An assistant scoped to the activity you're working on. Your
instructor controls which models are available and how the assistant may help.
Run. Run your program, or your instructor's test suite, from the sidebar.
Hand in. Submit straight to Kritik. Late submissions follow the activity's
due date and late policy.
Project download. Pull the starter project for an activity into a local folder.
Getting started
Install the extension and reload VS Code.
Open the Kritik view in the activity bar.
Sign in with your Kritik email and the launch code from your activity in Kritik.
The launch code also selects your region, so there is nothing to configure.
Download project files, open that folder, and start working.
When you're done, Hand in.
Requirements
VS Code 1.85 or newer.
A Kritik account with an assigned programming activity.
A local toolchain for your activity's language (for example Python 3) if you want
to run code locally.
What gets sent to Kritik
While you are signed in, the extension syncs your activity's files and their
authorship record to your Kritik account, and sends your prompts to Kritik AI. It
does not attribute or transmit activity from other AI tools, and it does not read
files outside the activity's project folder.
Development setup, architecture, fixtures, and QA live in AGENTS.md; release steps are
in docs/PUBLISHING.md. Both are in the repository, and neither is packaged.
