Reported by the assistant
filed from the Scheduler troubleshooter
System checks
Loaded models
Saved conversationsnewest first · oldest drop off automatically
'varaverk',
// All three stated rather than derived. Large is at the viewport cap here, and leaving medium
// to be worked out from the resting height would land it on that same cap — two settings
// doing the same thing.
'height' => '52vh',
'tall' => '68vh',
'tallLarge' => '85vh',
'empty' => "Ask Varaverk about itself. Answers come only from this installation's own "
. 'documentation, with sources.',
'placeholder' => 'e.g. what stops rsync and the mover running at once?',
'controls' => '',
]);
?>
build · JS NOT RUNNING
▶ Settings
Retrieval source
Intent routing favours per-script headers, which buries the
top-level prose. Pick README for "what is X" and "why does this exist" questions.
Varaverk Assistant only — the other profiles do not retrieve.
Looking things up
Not a web-search mode — it still answers
from what it knows, and reaches for results when it does not know, when the question
turns on something current, or when a version or figure is worth checking rather than
recalling. General Chat only: it is the one profile that cannot change anything, which
is why it is the one allowed to look outside. Your question is sent to the configured
search provider.
Reasoning
Kept and collapsed under each answer. Thinking time scales
with the question — seconds for a greeting, ~18s for a substantive one.
Configuration
written to master.conf
opens when you do
Standing memory — given to the assistant at the start of every conversation