Skip to content

Say what is missing when a container session has no model or no index - #24

Merged
daniel-rossier merged 1 commit into
mainfrom
container-no-model
Nov 19, 2026
Merged

daniel-rossier merged 1 commit into
mainfrom
container-no-model

Conversation

@daniel-rossier

Copy link
Copy Markdown
Contributor

Two misleading outputs of spear-chat in the container shell:

  • No model configured: the session opened on the default local server, which is not there, and showed model: ? (local llama-server). The command now stops with what to put in ~/.config/spear/local.conf.
  • A tree the user registered: the startup check reported it as a corpus missing from the baked index, to be fixed by rebuilding the image, and the session suggested spear-index, which the image does not have. The check now separates the image's corpora (a fault) from the user's (not indexed yet) and names /reindex.

Tried in the image on a workspace with seven registered sub-trees; the suite passes.

Started from the container's shell with no model configured, SPEAR opened
on a local server that is not there and showed its model as a question
mark; the first question would have failed. The command now stops and says
what to put in the configuration file.

The startup check called a tree the user had just registered a corpus
missing from the baked index, to be fixed by rebuilding the image. It now
tells the image's own corpora, where that is a fault, from the user's,
which are simply not indexed yet, and says how to index one from a session
rather than with a host command the image does not have.
@daniel-rossier
daniel-rossier merged commit 403422d into main Nov 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant