Local and cloud models¶
NAVIGATOR has no model of its own: your host's agent (Hermes, OpenClaw, Claude Code, Cursor…) does the thinking, on whatever model you gave it. NAVIGATOR only needs to know two things:
- What model the host runs:
cloudorlocal. Then it can keep LOCKED project data away from a cloud model. - Where a local model is, so that it can let that model read LOCKED files when the host's model is a cloud model.
The rule¶
| Project mode | Host model cloud |
Host model local |
|---|---|---|
| OPEN | the host's model reads the project files | the same |
| LOCKED | the host's model does not read the files: local_model action=ask lets the local model read them, and the answer is written to <project>/OUT/LOCAL_MODEL_<time>.md. The host gets only the file name and size |
the host's model reads the files |
LOCKED also keeps a project on its own inventory, makes web searches generic, and shows only file paths for troubleshooting records, whatever the model.
Device reads in a LOCKED project¶
With a cloud host model, device read (and facts, compare) in a LOCKED project returns the status,
timing and record paths only, never the outputs. To work on them, the host passes the record path to
local_model action=ask (files=[...]) or to scrambler action=sanitize (inp=
Settings (~/.config/navigator/navigator.yml)¶
MODELS:
HOST: cloud # what the MCP host's model is: cloud (default) | local
LOCAL: # an OpenAI-compatible endpoint on this host or your LAN
URL: http://127.0.0.1:11434/v1 # Ollama; vLLM, LM Studio and llama.cpp server work the same way
MODEL: qwen3.5:9b
API_KEY_ENV: "" # the NAME of an env var holding a key, if the endpoint needs one
TIMEOUT_SEC: 300
MAX_INPUT_CHARS: 60000 # how much project text one call may send
ALLOW_HOSTS: [] # host names you vouch for as your own machines
HOSTcan also come from the host's MCP config: envNAVIGATOR_HOST_MODEL=local. Use it when one NAVIGATOR install serves two hosts (for example a Hermes profile on Ollama and another on a cloud model).- The local URL must resolve to a loopback, private or link-local address (or be in
ALLOW_HOSTS): a LOCKED project's data must not leave your network. Proxies are not used. - No key is stored here. Encrypting keys in host configs is planned (Bitwarden Secrets Manager is one option).
The tool¶
local_model action=status # host model cloud/local; local endpoint reachable, models
local_model action=ask project=JOB1 task="Which OSPF neighbors are not FULL?" files=["RAW/show-ospf.txt"]
files are paths inside the project (default RAW/). Every call goes in the project's RUNLOG.md (for a
LOCKED project on a cloud host without the task text).
Running the host itself on a local model¶
For a fully local setup, point the host's own model at the same endpoint and set HOST: local:
- Hermes: a profile whose
modelis the Ollama endpoint (provider: custom, base URLhttp://127.0.0.1:11434/v1), andNAVIGATOR_HOST_MODEL: localin that profile'smcp_servers.navigator.env. - OpenClaw / Cursor / Claude Code: their own model settings; Claude Code runs on Anthropic's models (or
Vertex / Bedrock), so it is a
cloudhost.
Small local models are slow on a CPU (a 9B model took about 90 s for a short log on navhost) and weaker at tool
use; a common split is a cloud host model for OPEN work and local_model for LOCKED files.
Words: project mode and chat model¶
Two separate settings. The project mode (OPEN / LOCKED) is what may happen to a project's data; it
lives in the project folder. The chat model (CLOUD / LOCAL) is where the bot's own thinking runs; it is
set per chat thread. In Hermes: /model cloud and /model local (any case). The default chat model is
LOCAL when the profile has a local model.
Two model settings, two defaults. Do not mix them up:
| Setting | Where | Who reads it | Default |
|---|---|---|---|
MODELS.HOST (or env NAVIGATOR_HOST_MODEL) |
navigator.yml or the host's MCP config |
NAVIGATOR, to decide what it may return | cloud |
The chat model (/model cloud, /model local) |
the Hermes thread | Hermes and navigator-guard | LOCAL, if the profile has a local model |
NAVIGATOR cannot see which model a thread is on. On Hermes, NAVIGATOR_HOST_MODEL stays cloud, so
NAVIGATOR keeps withholding LOCKED device output even on a LOCAL thread. That is the safe side: work on the
records with local_model ask or scrambler sanitize. navigator-guard does know the thread's model, so on a
LOCAL thread it lets the bot read the project's files itself.
| CLOUD model | LOCAL model | |
|---|---|---|
| OPEN project | The bot sees device output and files and may search the web directly. Fastest | Everything works; nothing leaves the host; slower |
| LOCKED project | Device reads return status and record paths only (#152); navigator-guard blocks the host's own file, shell and web tools on the project; only the project's inventory; analysis through local_model ask or scrambler sanitize. The card warns |
The chat runs on the host, so navigator-guard lets the bot read the project's files; the inventory limit still applies. NAVIGATOR still withholds device output (it cannot see the chat's model) |
Hermes: LOCKED projects switch the thread by themselves¶
With the navigator-reply plugin, a message that starts or opens a LOCKED project ("new LOCKED project
X", "create project X as locked", any case) on a thread that is on the cloud model runs /model local
before the message is handled, so the chat itself runs on the local model (the profile's
model_aliases.local). Nothing changes for OPEN projects. /model local and /model cloud work by hand,
in any case.
After project create the thread gets a card:
🔒 Project DEMO3 (new)
• Folder: /data/projects/DEMO3
• Mode: LOCKED • Inventory: EVPN_LAB
• Model: gemma4:12b (local) — switched automatically for LOCKED
A LOCKED project on a cloud model gets a warning line with /model local. Replies on the local model are
much slower (tens of seconds per step on navhost's CPU).
Small local models and tool arguments¶
gemma4:12b sometimes leaves out project= or guesses argument names. The navigator-reply plugin
remembers each thread's project (from project create, or any successful call that named one) and fills
project= in when a navigator call has none; an explicit project is never replaced. The inventory tool
takes inventory= as well as name=.
Try it¶
- Run
navigator-setup(ornavigator-setup set MODELS.LOCAL_URL http://127.0.0.1:11434/v1 MODELS.LOCAL_MODEL qwen3.5:9b), or add theMODELSblock above to~/.config/navigator/navigator.ymlby hand, and restart the services that run NAVIGATOR (on navhost:systemctl --user restart atlas-link rudder-scheduler hermes-gateway). - Ask "local model status":
configured,reachableandhas_modelmust all be true. - Run tests N1–N9 in TESTING_CHAT.md (or CC9 in TESTING_CLAUDE_CODE.md).
navigator-setup asks for them (MODELS.HOST, MODELS.LOCAL_URL, MODELS.LOCAL_MODEL) and saves them only if the URL is a local address that answers with that model; change one later with navigator-setup set MODELS.<KEY> VALUE.
What is not built¶
- NAVIGATOR does not route a whole conversation between models; the host picks its model.
- Roles (QC, ANALYZER…) run as the host's subagents on the host's model. A host that can give a subagent its
own model (Hermes
delegate_taskwith a model override) can run them locally; NAVIGATOR does not do it. - The scrambler is rule-based and calls no model.