Live 2026-11-18 '자비 사과랑 배 중에 뭐가 더 달아' was searched as
'사과와 배 중哪个가 더 단가요'. The rule and the user message's closing line
now say to use only the query's letters.
Eval test_search_in_users_language.py, new case fruit (qwen3.6-35b-a3b,
game PC): Han in the search 7/7 before; rule only 3/3, closing line only
3/3, both 0/6; whole file 12/12.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- botBrowser `play`: searches YouTube for the words as said, opens the first video (not an ad,
without the playlist) and starts it, in one call (an address given opens that page); `type`
also takes `query`. Live 0.1.19: the model stopped on YouTube's home page or the results, a
retry was refused as a third call, and the answer still said the video played.
- `brain.location` (기본 위치, default 대한민국) goes to the brain as `location_name`: the time line
says it without GeoIP (no database on the game PC), and getWeather without a place uses it.
- Planner and webSearch keep search words in the user's language (never translated into
English), so recommendations fit where the user is.
Evals (qwen3:8b, 3 runs): play ending on a playing video found with the words as said 0/6 -> 5/6;
Korean searches for Korean requests 6/9 -> 8/9.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Drop the engine's deterministic Korean weather shortcut. It bypassed the
chat model and the tool runner, so a location the user had stated could
never be used. The tool already returns one clean Korean sentence.
- getWeather and the tool-argument prompts pass the place the user has
said they are (conversation or memory) and leave the argument empty
otherwise, so the detected location is not copied into it.
- getWeather retries a "district, city, country" name with its leading
parts dropped when the geocoder finds nothing.
- The planner gets the live time/location line and plans
searchMemory topic='where the user lives' only when the location is
unknown or disabled.
- The per-reply repeat guard counts only this reply's tool messages, so
calls carried over from the previous reply no longer block a retry the
user asks for.
- Memory extractor: the context block sits after the examples and the
no-location example uses a different query, so a location already in
context is not asked for again. New counterpart eval checks that it is
still asked for when the context has none.
- Tool retry eval fails every call in turn 1, so a model that retries by
itself inside turn 1 still exercises the user's "try again".
- Specs (planner, reply), docs/llm_contexts.md and the roadmap updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
M0 on Strata caught both v2 models skipping a tool they had been given:
the recommended model made up "24 degrees, sunny" instead of calling the
weather tool, and the fast model said "timer set" without calling the
timer tool (3 of 3 each). qwen2.5:7b does the same through the engine.
- Prompt: TOOL_HONESTY_RULES in the persona (live facts only from a tool
result this turn, actions only claimed after a tool reports success, no
answer text next to a tool call), restated at the end of the system
message by tool_honesty_reminder() with the turn's real tool names.
- Engine: skipped-tool guard. When a native-tool model answers before any
tool has run and the plan names a callable tool as a concrete call, the
answer is dropped and the plan steps are direct-executed, then the model
answers from the results. Only literal, schema-valid steps run (regex
fast path, no LLM repair); otherwise the held-back answer is delivered.
- Planner: the AVAILABLE TOOLS lines now carry argument names
(planner_tool_catalog), so concrete steps use the tool's real keys.
- Eval evals/test_tool_skip_confabulation.py; on qwen2.5:7b, 3 runs each,
available-tool cases went from 0/12 to 9/12 calling the tool.
- M0 kit: tools_fast / tools_recommended stages (run_m0_tools.bat) rerun
tool calling before and after the fix on the real models, loading the
production system_prompt.py and planner.py.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ollama keeps a separate loaded model instance per (model, num_ctx). The
main agentic chat used num_ctx=8192 while the router/enrichment/digest
passes used 4096, so every voice turn forced at least one cold reload
(~3.4s) when switching context sizes — the dominant per-turn latency
(measured: resident chat call 0.27s vs cold 3.4s).
Introduce a single OLLAMA_NUM_CTX (default 8192, env-tunable for tight
VRAM) used by call_llm_direct, chat_with_messages, call_llm_streaming and
the planner, collapsing a turn to one resident instance.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>