Troubleshooting

My license key is not accepted

Luciai Studio says why it refused the key; each message and its fix are listed here. The two most common causes: the key was not copied in one piece, or it is a key from the time the free plan lasted a month — Luciai Studio replaces it with one without an end date by itself when it is online. A free month that has ended asks for your free account.

If a key you just received looks expired, check your computer's date and time: the end date is compared with your computer's clock.

Lucicoder does not see my Ollama models

Make sure Ollama is installed and running, and that you have pulled a model. This lists the models you have:

ollama list

Then pick Ollama as the provider in the header of the Lucicoder panel, and the model in the model picker.

A small local model does not use its tools well

Lucicoder falls back to a universal XML grammar when a model's native tool calls do not work. You can choose yourself: /native off always uses the grammar, /native on always uses native calls, and /native auto detects again. A model made for code, such as qwen2.5-coder, is a good choice.

Claude Code or Codex bills API credit instead of my subscription

The command-line tool is logged in with an account that has no active subscription, so its usage goes to the vendor's API. Lucicoder detects this and offers Switch account: log in again with your Claude Max or ChatGPT subscription.

A model I expect is not in the list

Model lists are fetched live from each provider and cached. When a provider cannot be reached, a built-in list is shown instead, and labelled as such. Check your connection, and the API key in the provider settings, which open from the model picker.

Lucicoder will not run a command, or stops it

A hard denylist blocks dangerous commands in every approval mode, and no prompt gets around it. If you are sure about the command, run it yourself in a terminal.

A command Lucicoder runs is stopped after 120 seconds. For a dev server or a watcher, ask Lucicoder to start it as a background task; /tasks lists those.

I want to undo what Lucicoder did

Every turn is a checkpoint: one click reverts everything that turn changed. For older changes, Local History — in the command palette — keeps every save and every Lucicoder edit as a version you can compare and restore. More on checkpoints.

The debugger does not start

Python: debugpy has to be installed for the interpreter you picked. Luciai Studio shows the exact command for that interpreter; it looks like this:

python -m pip install debugpy

Node.js and TypeScript: VS Code's js-debug is installed on demand the first time you debug. Rust: the program is built with cargo build, and CodeLLDB is installed on demand.

Java debugging is not available yet; it is on the roadmap.

The Docker panel says Docker is not running

The Docker panel works through your Docker command-line tool. Start Docker Desktop, then open the panel again.

The testing view cannot read my results

The testing view detects Jest, Vitest, Mocha, Cargo, Go, Maven and pytest, runs your suite and parses the results. When it cannot parse the output, it says so — run the suite in a terminal to read the full output.

The security view says an auditor is missing

The security view runs the real auditors: npm audit, pip-audit, cargo audit, govulncheck and osv-scanner. For one you do not have, it shows an install button.

The GitHub view shows nothing

The GitHub view works through your own GitHub CLI login. Install the GitHub CLI and sign in:

gh auth login

The GitLab view uses a token instead, which is kept in your operating system's credential store.

A guest cannot join my Live Share session

Live Share works on a local network or over a VPN only, and a guest needs the session's token. There is no TLS yet, so use it on networks you trust.

Still stuck?

Ask on the support page or write to adeel.ahm1985@gmail.com. Tell us your Luciai Studio version, what you did, and the exact message you saw.