diff --git a/ai-assistant/src/main/assets/docs/index.html b/ai-assistant/src/main/assets/docs/index.html index 3b69e634..e0799942 100644 --- a/ai-assistant/src/main/assets/docs/index.html +++ b/ai-assistant/src/main/assets/docs/index.html @@ -56,6 +56,28 @@

Choosing a backend

agent reads are sent to Google over HTTPS. +

Will this model fit in memory?

+

When you pick a local .gguf file, it is measured against the RAM + free on the device at that moment, before anything is loaded. If it looks too + large you get a warning with the actual figures and two choices:

+ +

The warning quotes two numbers. Memory to load is the weights: these are + memory-mapped, so they need not all fit at once — when they don't, the device pages + them in and out, which is why an oversized model can stall for minutes instead of + failing immediately. Memory to run is the KV cache and compute buffers, which + are ordinary allocations and do have to fit. That is why a model can be reported as + risky rather than impossible: the outcome genuinely depends on how much paging your + device will tolerate.

+

To fit a large model, close other apps and select it again, or pick a smaller or + more heavily quantized build. A Q4_K_M quantization of a 1–3B model is the most + likely to run comfortably.

+

What the agent can do