A finished file tells you what was handed in. Alps keeps how it got there — and distils it into the few things worth your attention.
Not another dashboard to read. Alps points at the moments that matter: where a student got stuck, what they kept reworking, and whether the work was steady or one late sitting.
One student, one afternoon — replayed, flagged, and compared.
A scripted walkthrough — not live student data. The panels are the ones teachers use.
Every teacher has asked these about a submission. Alps answers them in about a minute.
The lines a student kept returning to are the lines they struggled with, and Alps shows you exactly which ones — read across a whole session rather than from a single moment.1 You stop guessing which concept to reteach and start seeing it.
Work is grouped into sittings, so steady effort across a week looks visibly different from one long evening. Useful for a conversation, not for a penalty.
Alps does not answer that, and will not pretend to. It shows you what was recorded — including that a block arrived in one paste — and leaves the judgment where it belongs: with you.
A mark on the finished result gives a student nothing to act on. Alps gives you something specific to say: the moment it turned, and what they did next.
Nobody has time to read a chart per student. Alps watches for a small number of moments and puts them in front of you — and stays quiet the rest of the time.
A student ran their code again and again and the same failure kept coming back — a well-established signal that a novice is stuck rather than progressing.2
Something that ran fine earlier was broken by a later change and stayed broken — usually the moment a student lost the thread.
A sizeable block arrived in one paste from outside Alps. It records how the text entered the editor — not where it came from, and it implies nothing.
A dash means nothing stood out, and that is the normal state. Copying from the Alps textbook is recognized as ordinary work and is never flagged.
Detectors guess and get people in trouble. Alps shows you the recording and leaves the conclusion to you.
| Feature | Alps Process Insights | A typical AI detector |
|---|---|---|
| What it reports | What was recorded | A probability it inferred |
| Stretches it did not observe | Shown as gaps | Filled in by the model |
| Verdict on the student | None — you decide | An accusation |
| Risk to a student who did nothing wrong | Nothing to be wrong about | The well-known failure mode |
| Effect on grading | None | Often flags or blocks |
| Copying from your own course material | Recognized as normal work | Frequently flagged |
Recording how novices actually program is long-established practice in computing-education research.3 What is new is handing it to the teacher in a form they can use during marking.
Students can open their own replay on any coding activity and watch their solution take shape — which is genuinely useful when something worked an hour ago and no longer does.
“It worked before I changed something.”
Every teacher has heard it. Now the student can go and find the moment themselves — and so can you.
Some of the established research the feature builds on. Alps is not affiliated with the authors or projects cited.
See where every student struggled, what they reworked, and the moment it turned — without reading a chart for each one. Start with the free Educator Basic tier.