CodeTrain / Roadmap
Roadmap
What has shipped since launch, what is being built right now, and what is being considered. Shipped items carry the date they reached production. Nothing ahead of today carries a date, because promising one would be guessing.
CodeTrain launches
A Socratic coding tutor that refuses to write your code for you, released as a free open-source agent and a managed tutor in the browser.
Live for everyone, free tier included unless noted.
▸The course mapCoursesJul 2026
Courses became lines, classes became stops and lessons became steps along them, so it is obvious what follows what instead of being a flat list of topics.
▸How LLMs Actually WorkCoursesJul 2026
Four classes and eighteen lessons building a working transformer in pure NumPy, with live demos for tokenisation and attention rather than diagrams of them.
▸Lessons from any public repo, freeYour codeJul 2026
Point the free tier at a public repository and the lesson is built from the code that is actually in it. Secrets and gitignored files are never read.
▸Competency receiptsTeamsJul 2026
A record of what someone wrote unaided, for onboarding sign-off. It reports no data as no data and never as a zero, because it is a claim about a real person.
▸Spaced reviewLearningJul 2026
Concepts you got stuck on come back at widening intervals, as a fresh drill built from what you got wrong rather than a replay of the lesson.
▸A guided first lessonGetting startedAug 2026
The first lesson is on us and walks through the screen as you go, so nobody has to work out what a Socratic tutor wants from a blank editor.
▸Concepts that say what is solidLearningAug 2026
Progress splits what you have practised into due for review, still learning and solid. There is deliberately no not-yet-started: we would have to invent a syllabus you never chose in order to report it.
Actively in progress.
▸Try a lesson without an accountGetting started
A real lesson on the front page: real editor, real execution in your browser, real checks, and a tutor whose replies are written in advance and labelled as such. Asked for by testers who wanted to feel the product before signing up.
▸Public roadmap and changelogTrust
This page, and a changelog at /changelog/ carrying every release note. Both are generated from the same source the in-app What's New card reads, so they cannot drift from what actually shipped.
Committed, not started. Order is roughly the order they will land in.
▸Real-world lesson examplesYour code
Worked examples on the marketing site showing what CodeTrain pulls out of recognisable open-source repositories, quoted from actual runs rather than written to look good.
▸Skill progression you can seeLearning
Streaks, levels and a sense of a concept getting stronger over time, built on the existing review schedule. One definition of solid across the learner view and the team dashboard, so gamification cannot quietly invent a second one.
▸An architecture and security pageTrust
A diagram of what crosses which boundary: what stays on 127.0.0.1 with the open agent, what the managed tutor sends and where, and what the sandbox host runs. The answer already exists in the privacy policy; it deserves a picture.
▸The Backend, Web and Data coursesCourses
Three lines already showing as coming soon on the course map: SQL, APIs and Git; HTML, CSS and the DOM; pandas and analysis.
Wanted, and not yet proven worth the complexity. Say so if one of these is the thing standing between you and using CodeTrain.
▸CI and test-suite integrationTeams
Raised by testers: have CodeTrain meet the code where it already runs. A check that turns a pull request into a lesson for whoever is about to review it, or a failing suite into a drill on the thing that broke. It would share the repo reading that repo mode already does, and fold naturally into team onboarding.
▸Onboarding journeys for a teamTeams
A lead picks the parts of a codebase a new hire has to understand, and CodeTrain builds the path through them and reports who got where. Available in early access on Team today; this is making it something you configure rather than something we set up for you.
▸A status pageTrust
Honestly deferred rather than planned. An all-green status page with no monitoring behind it is decoration, so this waits until there is real uptime history worth publishing.
The line keeps going. If something you need is missing from it, say so and it gets considered on the spot. There are few enough people using this that one email genuinely moves the order.
Every release, in full
This page is the shape of things. The changelog is the detail: every user-facing change since launch, newest first, the same notes that appear in the product.