Skip to content

Optional AI Input

AI input is optional: with it off, the engine only does local pinyin decoding and sends no network request at all. This page covers how to turn it on, what you get, and where the key lives. The data-boundary conclusions are on Privacy and data, not repeated here.


  • Off by default. The switch is Settings → Pinyin → Enable AI input.
  • Once on, the cloud only takes part in re-ranking and continuation. Every keystroke is still served local candidates first; being offline, timing out, or turning it off never changes that frame.
  • How special fields such as password boxes are handled is on Privacy and data. A cloud response is never written straight into your user dictionary or memory.

Settings → Pinyin. After ticking Enable AI input, fill three fields: provider, API URL, model.

The provider dropdown is a convenience preset: picking a row fills in the URL and model name for you, and both stay editable. Any OpenAI-compatible endpoint works.

ProviderPrefilled API URLPrefilled model
DeepSeek (default)https://api.deepseek.com/v1/chat/completionsdeepseek-chat
Tongyi Qianwenhttps://dashscope.aliyuncs.com/compatible-mode/v1/chat/completionsqwen-plus
OpenAIhttps://api.openai.com/v1/chat/completionsgpt-4o-mini
Grokhttps://api.x.ai/v1/chat/completionsgrok-4.6
Localhttp://127.0.0.1:11434/v1/chat/completionsllama3
Otherdoes not overwrite; uses what you typeuses what you type

The Local row points at an OpenAI-compatible endpoint listening on your own machine (Ollama, for example). A local service needs no key.


The key is not written to the config file. The settings window saves it into the Linux desktop Secret Service (GNOME Keyring / KWallet): type the new value under “API key”, press Save key, or Delete key to clear it; the status line next to it shows whether an entry already exists for that provider.

  • When no keyring is available, no cloud request is sent, and local pinyin input is unaffected.
  • Do not put the key in command-line arguments, environment variables, or logs, and do not “verify” it with a command that prints its contents.
  • To check whether your session can reach Secret Service:
Terminal window
busctl --user list --no-pager | grep -F org.freedesktop.secrets
command -v secret-tool

If the first line prints nothing, check that the desktop session’s D-Bus and keyring service are started and unlocked. The second command only tells you whether the diagnostic tool is installed.


Continuation has its own switch: Settings → Pinyin → Enable Ghost continuation, and it depends on Enable AI input already being on. The same page tunes:

ItemRange and default
Continuation debounce (ms)0–2000, default 300: how long a pause must last before a request goes out
Ghost minimum confidence0–1, default 0.6: below this score nothing is shown
Streaming continuationon by default
Continuation context scrubbingon by default
Prefer on-device re-ranking (off goes straight to the cloud)on by default

The context window is roughly 800 characters on each side of the caret.


When you pause, a grey suggestion may appear in the candidate row, labelled “from cloud”.

  • Press Tab to accept it.
  • Just keep typing to reject it — no extra key, and it does not interrupt the pinyin you are composing.
  • Cloud and local rows are clearly separated: local results say “from local”, cloud results say “from cloud”.

It says the keyring is unavailable Confirm the desktop session has GNOME Keyring or KWallet started and unlocked, then reopen the settings window and try again. The diagnostic commands are in section 3 above. Without a keyring, ordinary pinyin input keeps working — only the cloud stays silent.

It says “configured”, but no suggestion ever appears “Configured” only means an entry for that provider exists in the keyring; it does not mean the key still works. Check that the provider, model, and API URL match what your provider uses today, that the key is valid, and that the account has usable quota; re-save the key if needed.