Settings

Which rounds the plan is built for. The onboarding promises you can add one any evening — this is that evening.

Starter files, test scaffolding and the way he reads your code.

The language you speak in. The interface stays English because your interview will be.

Plain — he answers as he sees fit. Laddered — six steps from an orienting question down to almost the answer, and each “I’m stuck” moves one step, never two.

A tutor who catches you at every pause teaches you to expect that. A real interview answers silence with silence.

The mind behind the teacher. Each teacher keeps their own; a change applies to your next session, not the one running.

Plan, history, error journal, mastery and the current diagnosis — one JSON file, no waiting and no email.

Sessions, journal, plan, repeats, stories, mastery — every row that belongs to you. Not the problems and designs (those are not yours), not other people on this machine, and not your account: you stay signed in.

Audio: nothing — recognition and speech run locally. The text of the session goes to the model provider this instance is configured with, under its key.

Company, level and city. Everything the plan schedules is built backwards from it.

Sign-in exists and data is separated per account: your plan, history and skill map belong to whoever is signed in. Signing out leaves the machine running — it does not erase anything.

Goal, tracks, teacher and the sound check — the same four steps as the first day. The sound check has no other door: skipping the wizard used to close it for good.