Troubleshooting aixplain Desktop, Koder and Omni

This article helps you fix common problems with aixplain Desktop, Koder, Scan and Omni and explains how to report a bug.

Check your install first

If you use the CLI, run koder doctor. It checks the install, configuration, storage, providers and recent logs, and says what it finds. Make sure you are on the latest version with koder --version, and see Update aixplain Desktop.

The app

The browser didn't open when I signed in

• Select Copy next to the sign-in link in the app.
• Paste the link into your browser and finish signing in there.

The app says it lost its connection

Use Restart in the app. It brings the app's server back without relaunching the app, and works even after the server has crashed.

Something isn't working after an update

• Download the current installer from aixplain.com/koder and install it over your current app. Your sessions and settings are kept.
• If the CLI is on version 0.2.4 or 0.3.0, run the installer once, because those versions can't upgrade themselves.

The app is still running after I closed the window

On macOS, closing the window doesn't quit the app. Quit aixplain from the app menu.

I ran out of credits

aixplain models draw on your team's credits. Open Settings → Account & usage to see your balance and top up, or run koder billing. See Account, plans and billing.

Models

My Claude, ChatGPT or Cursor plan doesn't show up

• Make sure that vendor's CLI is installed and signed in: Claude Code, codex login or cursor-agent login.
• Check Settings → Models & providers → Your subscriptions, or run koder providers subs. Each plan shows as Ready, Not signed in or Not installed, with the command that fixes it.
• If a plan shows Not signed in, sign in to that vendor's CLI in a terminal, then check the status again.

I see "Couldn't reach the provider"

• Check your network connection.
• Open the technical details behind the toggle to see what failed.
• Select Try again. Your message goes back in the chat box, ready to send.
• If it keeps failing, pick another model in the model picker.

If your computer slept during a request, the app waits for the network when it wakes and carries on.

The model can't read my image or PDF

The app tells you before sending when the model you picked can't read an attachment. Pick a model that accepts images in the model picker. See Choose a model.

A response stopped partway

If the provider's safety filter stopped the response, the app says so and keeps the partial reply. Rephrase the request, or try another model.

My local model doesn't appear

• Make sure Ollama is running. The app finds a running Ollama with no setup.
• Check that the model can chat. Embedding models are left out of the picker.
• Check the model's context. Local models need at least 32,768 tokens.

Permissions

Full access switched back to Auto

This is expected. Full access goes back to Auto every time the app restarts. Pick it again from the Permissions menu. See Choose how much the agent does on its own.

The agent keeps asking before it reads .env

This is expected. Secret files such as .env ask before every read, in every mode, including reads inside shell commands. Always allow covers only the file it names.

Koder and the CLI

koder isn't found after install

The installer places koder in ~/.koder/bin and adds it to your user PATH. Open a new shell, or add ~/.koder/bin to your PATH. In a CI job that runs in the same shell, call ~/.koder/bin/koder directly or add that folder to the job's PATH.

A CI job can't reach a model

Run koder doctor in the job. It checks the install, config, storage, providers and recent logs.

Scan

I can't find Scan in the app

Open a project in the sidebar first, then select Security scan. You can also start a new chat and choose Check for security bugs, or search the command palette for "Scan for security bugs".

Scan shows a finding that I think is safe

Scan reads the code but doesn't run it yet, so every finding is marked Likely. Read the trace and the code, check them against how your code really runs and select Not a real bug if it can't be reached. See Find security issues with Scan.

Omni

My Omni chats from the web don't show up

Omni in the desktop app and Omni at app.aixplain.com are separate. Each keeps its own sessions and settings, and they don't sync yet. Omni through WhatsApp or Telegram is the cloud Omni.

Omni says a tool is missing

Connect the app Omni names, then ask again. In an organization, ask your admin whether that connection is allowed. See Get started with Omni.

A run stopped at a connected app

Check whether it's waiting for your approval. Omni asks before it sends, spends, books or connects, and every send, create, change or delete in a connected app is approved one call at a time. In the desktop app, Omni home lists chats stopped at an approval or a question, and scheduled runs that failed.

Report a bug

• From the app: use the bug button to send feedback straight to the Koder team. Logs and the chat are included only if you tick them, and keys, tokens, your home path and personal details are removed on your computer first. You see the exact text before it's sent.
• On GitHub: open an issue on GitHub with your version, operating system, the steps to reproduce it and what you expected. Run koder report to save a bug report with the session, recent logs and version, and attach it.
• Security issues: email care@aixplain.com. Remove credentials and private data from logs and screenshots first.