Skip to main content

Troubleshooting

The hotkey does nothing​

Another application may own Alt+Shift+D. Change Celeris's hotkey in Settings, or quit the other app. On macOS, also check Celeris is still listed under System Settings → Privacy & Security → Accessibility.

The capture is blank or shows only the wallpaper​

macOS has not granted Screen Recording. Add Celeris under System Settings → Privacy & Security → Screen Recording, then restart Celeris. The grant takes effect only on relaunch.

Celeris picks the wrong window​

Grant Accessibility under System Settings → Privacy & Security so Celeris can read the frontmost window's title, or name the window in your prompt.

Sign-in never completes​

  • Check the code you typed in the browser matches the one in Celeris. Use the copy button rather than retyping.
  • Check the browser window did not open behind another app.
  • Start again from Settings → Account. A pending sign-in expires after a few minutes.

A command fails with "command not found"​

Celeris uses the environment it was launched with. A tool added to your path in a shell profile may be missing when Celeris starts from the Dock or Start menu. Use an absolute path in the prompt, or launch Celeris from a terminal that has the tool on its PATH.

The conversation could not be compacted​

When a conversation outgrows the model's context, Celeris summarises the older part and saves the full text to files on your machine. If that fails, the composer shows an error ending in "Start a new chat with the saved spill paths". If the error mentions CELERIS_BASE_URL / CELERIS_API_KEY not configured, sign in from Settings → Account. Then start a new chat and point it at the saved paths to carry on.

A setting could not be saved​

When Settings shows "Couldn't save; check your connection", the change was not written. Settings are stored in a local settings.json, so check that the file is readable and the disk is not full. If Celeris could not read the file, it says so at the top of the page and saves nothing until it can. Fix the file's permissions, or move it aside, and make the change again.

The plugins list could not be read​

"Couldn't read your plugins. Reload to try again." means Celeris could not read the data folder it keeps plugins in. It does not mean a plugin is broken. Press Reload to read the list again. If the message keeps coming back, check that Celeris's data folder is on a disk it can read, then restart Celeris.

Celeris could not answer​

When a request to Celeris fails, the conversation shows a red card that names the cause:

  • Couldn't reach Celeris means the request was cut off before it arrived. Check your internet connection, VPN or proxy, then press Retry or send the message again.
  • Celeris had a problem answering, or a reply that could not be read, means the service failed on its side. Press Retry after a moment. The card's Details keeps the raw reply for a bug report.
  • Celeris is busy right now means you reached a rate limit. Wait a moment and try again.

If the same card keeps coming back, send a report as described in Still stuck.

A connector stopped working​

Its access may have expired or been revoked. Disconnect and reconnect it in Settings → Tools → Connectors.

Voice does not hear you​

Check Celeris has microphone permission in your operating system's settings and a speech provider key is set in Settings → Voice. Dictation turns off after a minute of silence; click the microphone to resume.

Still stuck​

Type report a bug in the composer, or choose Send feedback from the account menu. Otherwise, contact support with the approximate time of the problem.