SETUP / YOUR FIRST SESSION

From install
to your first “aha.”

Use your IDE's terminal, or any terminal opened in your project folder. No provider key needed for managed AI.

CodeTutor is in public beta. Start with a small project and review suggested changes before approving them.

01 / INSTALL

Make it available.

Install Node.js with npm first, then reopen your terminal. Run:

Terminal
npm install -g codetutor@latest
codetutor --version

This installs the CLI for future terminals too. If your terminal cannot find npm or CodeTutor, see installation help.

02 / AUTHORIZE

Sign in securely.

Terminal
codetutor account login
  1. Open the link shown in your terminal.
  2. Sign in and approve the matching device code.
  3. Wait for confirmation in the terminal before continuing.
Check sign-in
codetutor account status

Your Mac may ask to access its credential vault. Never enter your Mac password into a website or send it to support. Troubleshoot repeated prompts →

Not ready to sign in? Continue with local lessons. They do not use managed AI or account credit.

03 / OPEN YOUR PROJECT

The right folder matters.

In your IDE, open the project you want to work on, then open its integrated terminal. Check the path first.

macOS / Linux
pwd

Windows PowerShell
Get-Location

Once the path is correct, launch CodeTutor. The dot means this folder.

Terminal
codetutor .

04 / LEARN BY DOING

Choose. Ask. Review.

Select a model in the model picker. Choose a tool-capable model for project work, or a chat-only model for explanations.

Explain this project and help me write one test. Ask me questions before changing anything.

Keep the Tutor agent selected. Approve only edits and commands you understand. Review the resulting changes in your editor, run the checks, and ask the tutor to explain anything unclear.

NO ACCOUNT? START HERE.

Practice locally.

No sign-in, model connection, or AI credit needed. Install the CLI above first; then take these steps one at a time.

1. Prepare the lesson runtime

Bundled lesson checks use Bun, a JavaScript and TypeScript runtime. The CLI's built-in runtime does not install the separate bun command used by these checks. Check your terminal:

Check lesson runtime
bun --version

If Bun is missing, follow the official Bun installation guide, reopen this terminal, and check again. Initial installation needs internet access; lessons and checks work offline afterward.

2. Create your first lesson

Create a lesson
codetutor learn level beginner
codetutor learn start js-01-values --no-tui

CodeTutor prints a Workspace path. Open that exact folder with your editor's Open Folder action. Read README.md, edit index.js, and save. This is a separate practice folder, not your current project.

3. Ask for a hint if you need one

Next hint
codetutor learn hint js-01-values

Each request reveals the next hint, up to three. A hint does not change your files.

4. Check after saving your work

Check your lesson
codetutor learn check js-01-values

An unfinished starter is supposed to fail its checks. That is feedback, not an installation error. Read the result, edit your answer, save, and check again. Only a passing validator marks the lesson complete.

View progress
codetutor learn status

Returning to unfinished work? codetutor learn resume shows an in-progress lesson and its folder. If all lessons you started are complete, it reports that no lesson is in progress. To revisit this lesson, run codetutor learn start js-01-values --no-tui. Starting it again preserves your files unless you explicitly reset it.