[CodeTrain](https://codetrain.ai/) / 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 July 2026 A Socratic coding tutor that refuses to write your code for you, released as a free open-source skill, a local agent and a managed tutor in the browser. Since launch10 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. ### ▸Try a lesson without an accountGetting startedAug 2026 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 changelogTrustAug 2026 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. ### ▸The Conductor NetworkGetting startedAug 2026 Every account has a link, free tier included. You earn a fifth of the plan price for anyone who joins through it, every month they keep paying, and five people on Pro covers a plan of your own. Bring more and the rate rises. When they stop paying, so does the earning, and the dashboard shows you that the day it happens. You are here Building now2 Actively in progress. ### ▸Learning your own network, read onlyTeams Operations teams should be able to learn their own network the way engineers learn a repository: from the real thing, and without the risk. The shape is a connector the team runs themselves, holding their own credentials and exposing a fixed set of read-only commands, so CodeTrain reads real output and never holds a credential, never runs anything else, and never changes a device. Lessons and troubleshooting practice get built from what it finds, and when it cannot reach part of the network it says so instead of filling the gap in. Being built now. The connector, the read-only command set, the record of what was and was not reached, and a sandbox with a real router in it all exist and have been run against real hardware. None of it has been released, and no team has used it yet, which is the part that decides when it moves. ### ▸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. Next3 Committed, not started. Order is roughly the order they will land in. ### ▸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. Exploring4 Wanted, and not yet proven worth the complexity. Say so if one of these is the thing standing between you and using CodeTrain. ### ▸Conductors who teach, and conductors who helpTeams The Conductor Network has one track today: you share CodeTrain and earn a share of what the people you bring in pay. Two more are wanted and neither is designed yet. An educator track, so a teacher can bring a class into a real environment and see how they are actually doing rather than whether they submitted. And a community track, for the people who answer questions and keep others going, which is work that deserves the same recognition as bringing somebody in. Say so if you would use either, because that is what decides which gets built. ### ▸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 feed the onboarding journeys a Team lead can already build today. ### ▸Lessons that involve a networkCourses Every runtime today is deliberately offline, which is why a free lesson costs nothing to run and why nothing a learner writes can call out. That also rules out a whole category worth teaching: sessions and cookies, retries and timeouts, and status codes. The likely shape is endpoints we serve ourselves that behave like the real thing, so a lesson stays reproducible and offline-safe rather than depending on somebody else's uptime. Learning a team's own real network is a different idea with different rules, and it has its own entry above. Wanted, not yet designed. ### ▸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](mailto:hello@codetrain.ai) 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](https://codetrain.ai/changelog/) is the detail: every user-facing change since launch, newest first, the same notes that appear in the product. [Start free, no card](https://codetrain.ai/app/)[Read the changelog](https://codetrain.ai/changelog/) --- Source: https://codetrain.ai/roadmap/ This is the markdown twin of the page above. Every public CodeTrain page serves one on `Accept: text/markdown`. Start at https://codetrain.ai/llms.txt for the full map, or https://codetrain.ai/developers/ for the API.