v1.5.0

mtop now tells you why a local model is slow, or why its answers went wrong.

Why is it slow?

• When Ollama can't fit a model in VRAM it quietly runs part of it on the CPU. The models pane now turns that row amber and shows cpu 38% next to the TTL. Lemonade models running on CPU show up too.

Why is the answer off?

• A prompt that blew the context window gets a ctx 97% or ctx over, rejected marker in the requests pane, with details in the inspector.
• llama.cpp, vLLM and SGLang rejections are read from the error the server sends back, so that one's exact.
• Ollama trims prompts silently, so anything at 90% of the window or more is flagged as likely truncated.

Reasoning models

• Thinking tokens count toward tok/s on OpenAI-style streams (reasoning_content and reasoning).
• The inspector shows the thinking text separately from the answer, for Ollama, OpenAI-style and /v1/responses traffic.

More runners, more GPUs

• llama-swap, Lemonade and SGLang, with u to unload on llama-swap and Lemonade.
• AMD GPUs through amd-smi, with rocm-smi as the fallback.
• AMD and Intel GPUs on Windows, read from the system performance counters (temp and power show n/a there).

Also

• Two new /metrics series: mtop_model_cpu_percent and mtop_ctx_overflow_total. -notify fires for both warnings.
• The models pane now shows name, VRAM and TTL first, so the markers still fit a 100-column terminal.
• Moved to Bubble Tea v2.
• Captured prompt and answer text (-inspect) stays in memory and is no longer written to the history file.
• Fixes: an old Lemonade on :8000 no longer shows as vLLM, llama-swap no longer appears twice, and the by-model view doesn't reshuffle equal rows.

brew and scoop pick this up shortly; winget follows once Microsoft merges the bump.