One problem.
One clear next step.

If npm is missing, install Node.js and reopen your terminal. If only CodeTutor is missing, install it with npm install -g codetutor@latest, then reopen the terminal. Check that the Node installation used by your IDE matches your regular terminal. Do not use sudo as a first fix.

node --version
npm --version
codetutor --version

A path such as /path/to/your/project is an example, not a real folder. Open your actual project in your IDE, open its integrated terminal, then run codetutor .. Check pwd on macOS/Linux or Get-Location in PowerShell first.

Check the directory shown in CodeTutor against your editor's project folder. Lesson workspaces are separate and their paths are printed by codetutor learn resume. Also check that the model supports tools and that you approved the proposed edit. An explanation or plan is not a file edit.

This warning is separate from CodeTutor sign-in. Review the package name and the script before deciding whether to approve it. First run codetutor --version: if it works, do not change npm's global script policy just to dismiss the warning.

Run the login command, open its browser link, and approve the matching device code. Wait for the terminal to confirm authorization. Login is required for managed AI; local lessons remain available without it.

codetutor account login
codetutor account status

Start a fresh login from the CLI. Use the newest link and code, and complete approval while the terminal is waiting. Check your spam folder. If the service reports an email rate limit, stop repeated requests and retry after the reported delay.

The operating-system credential vault prompt is separate from your CodeTutor login. Check that the requesting application is the CodeTutor binary you installed. If your Mac login password is rejected or the popup repeats, cancel it and stop retrying. Check the login keychain's lock state in Keychain Access. Do not reset your entire keychain, disable security, or paste your Mac password into the website.

Update the CLI, then attempt a fresh login. If it still fails, report the CLI version, macOS version, and exact error text without credentials. This needs a vault integration fix, not a provider API key.

This means the web or desktop build is missing its public account configuration. Users should not add server secrets or create a Supabase project to use CodeTutor. Try the CLI and report the affected app version or URL so the build can be corrected.

Lesson validators need Bun installed separately and available in the same terminal as CodeTutor. Follow the official Bun installation guide, reopen your IDE's terminal, and verify the command below. Installing CodeTutor alone does not install this lesson-check command. No account or provider key will fix a missing runtime.

bun --version

If this succeeds but the validator still cannot start, check that your terminal and IDE use the same PATH. Report the exact error without private paths or credentials.

Starter answers intentionally fail. Open the Workspace folder printed by CodeTutor, read README.md, edit index.js or index.ts, and save before checking again. Keep the bundled tests unchanged. Hints guide you without editing your files; a solution reveal shows a diff without replacing your answer.

codetutor learn hint js-01-values

Use the ID of the lesson you are actually working on. Follow the first-lesson walkthrough →

Sign in and explicitly select an available model in the picker. Type a prompt and check your usage allowance. A chat-only model will not be able to edit files. If the catalog cannot load, report the error rather than configuring an unrelated provider key.

The selected model or managed service could not fulfill the request. Save your prompt, check the account usage screen, and retry later or deliberately choose another supported model. Do not repeatedly resend a paid request or expose your own Gateway credentials as a workaround.

A hosted web page cannot access your filesystem by itself. It needs your local CodeTutor server and an approved pairing. Keep the server running and use the exact origin requested by the pairing flow. Do not use a wildcard CORS rule or expose the server to your network to work around this.

For the same-origin local interface, run this from your project terminal and open the URL it prints:

codetutor web --hostname 127.0.0.1

The published beta has a known signing issue. A successful download does not prove a valid application signature. Use the npm CLI while a corrected installer is verified. Do not disable Gatekeeper or remove quarantine recursively from broad folders.