ur-agent 1.15.0 → 1.16.1

package/docs/AGENT_FEATURES.md

@@ -32,8 +32,16 @@ ur claim-ledger add --claim "..." --source web:https://example.com
 ur claim-ledger validate
 ur browser-qa validate
 ur browser-qa run home-page-smoke --dry-run
+ur --discover-ollama
+ur --ollama-host http://192.168.1.50:11434
 ```
 
+## v1.16.0 Additions
+
+| Addition | Surface | What it adds |
+| --- | --- | --- |
+| Network Ollama discovery | `ur --discover-ollama`, `ur --ollama-host <url>`, `settings.ollama` | Scans active local subnets for Ollama servers on port 11434, verifies via `/api/tags`, and shows a host picker for the current session. |
+
 ## v1.15.0 Additions
 
 Seven additions from the 2026 agent-platform gap list. They keep UR local-first

package/docs/AGENT_UPGRADE_1.16.0.md

@@ -0,0 +1,102 @@
+# UR Agent 1.16.0 Upgrade Notes
+
+UR 1.16.0 adds local-network Ollama discovery. The agent can now find Ollama
+servers on your LAN, let you pick one at startup, and remember the choice for
+future sessions. The endpoint is no longer hardcoded to `localhost:11434`; it
+can be set via settings, environment, or a CLI flag.
+
+## Network Ollama Discovery
+
+### One-time discovery at startup
+
+```sh
+ur --discover-ollama
+```
+
+UR scans the active local subnets (wired Ethernet and Wi-Fi/WLAN) for hosts
+listening on port `11434`, verifies each one by fetching `/api/tags`, then shows
+a picker with:
+
+- `This computer` — your local `ollama serve` at `http://localhost:11434`
+- every discovered LAN host and the number of models it advertises
+
+Select a host and UR uses it for that session only. The choice is **not**
+persisted, so plain `ur` continues to use `localhost:11434`.
+
+### Enable discovery on every startup
+
+Add to `~/.ur/settings.json`:
+
+```json
+{
+  "ollama": {
+    "lanDiscovery": true
+  }
+}
+```
+
+The picker appears on every startup. The choice is still session-only and is
+not written to settings.
+
+### Point to a specific host without scanning
+
+```sh
+ur --ollama-host http://192.168.1.50:11434
+```
+
+This is session-only and does not write settings. It takes precedence over
+settings and `OLLAMA_HOST`.
+
+### Persistent host via settings
+
+```json
+{
+  "ollama": {
+    "host": "http://192.168.1.50:11434"
+  }
+}
+```
+
+When `ollama.host` is set, UR uses it automatically. Precedence is:
+
+1. `--ollama-host <url>` CLI flag
+2. `OLLAMA_HOST` environment variable
+3. `ollama.host` in user settings
+4. fallback `http://localhost:11434`
+
+## What Uses the Chosen Host
+
+The resolved host is used everywhere UR talks to Ollama:
+
+- interactive chat requests (`/api/chat`)
+- installed-model listing (`/api/tags`)
+- model metadata refresh (`/api/show`)
+- local embeddings (`/api/embed`)
+- `ur model-doctor`
+- `ur doctor` / `ur sysinfo`
+- startup preflight connectivity check
+
+## Security Notes
+
+LAN scanning is opt-in only. It never runs automatically unless you pass
+`--discover-ollama` or set `ollama.lanDiscovery: true`. The scan is limited to
+active local IPv4 interfaces and ignores loopback and link-local addresses. It
+uses bounded concurrency and short timeouts so it finishes in a few seconds on a
+/24 subnet.
+
+## Release Verification
+
+Run these before publishing:
+
+```sh
+bun test test/ollamaDiscovery.test.ts test/ollamaModels.test.ts test/ollamaTimeout.test.ts
+bun run typecheck
+npm pack --dry-run
+```
+
+Optional local smoke checks:
+
+```sh
+bun src/entrypoints/cli.tsx --discover-ollama --help
+bun src/entrypoints/cli.tsx --ollama-host http://localhost:11434 -p "hello"
+```

package/docs/CODE_FEATURE_INVENTORY.md

@@ -1,7 +1,7 @@
 # UR Agent code feature inventory
 
 This file is a code-derived inventory of what this agent can do in the
-`ur-agent` 1.15.0 source tree. It is meant to cover behavior that is easy to
+`ur-agent` 1.16.0 source tree. It is meant to cover behavior that is easy to
 miss in user-facing documentation.
 
 Sources traced include:

package/docs/CONFIGURATION.md

@@ -4,22 +4,69 @@ UR reads configuration from CLI flags, environment variables, and project or use
 
 ## Model Provider
 
-UR runs models strictly through the local Ollama app. The request endpoint is fixed and cannot be reconfigured from UR:
+UR runs models strictly through the local Ollama app. The default request endpoint is:
 
 ```text
 http://localhost:11434/api
 ```
 
-Any model exposed by that local Ollama app can be used, including local models and Ollama Cloud-backed models. UR does not call remote provider APIs directly and does not manage model API keys.
+Any model exposed by that Ollama app can be used, including local models and Ollama Cloud-backed models. UR does not call remote provider APIs directly and does not manage model API keys.
 
-Model selection environment variables:
+### Reconfiguring the Ollama host
+
+The endpoint can be changed from UR in three ways, in order of precedence:
+
+1. `--ollama-host <url>` CLI flag (session only)
+2. `OLLAMA_HOST` environment variable
+3. `ollama.host` in user settings (`~/.ur/settings.json`)
+
+Examples:
+
+```sh
+# Session-only
+ur --ollama-host http://192.168.1.50:11434
+
+# Via environment
+OLLAMA_HOST=http://192.168.1.50:11434 ur
+
+# Persistent setting
+ur --settings '{"ollama":{"host":"http://192.168.1.50:11434"}}'
+```
+
+Model selection environment variables still work the same way:
 
 ```sh
 OLLAMA_MODEL=qwen3-coder:480b-cloud
 UR_MODEL=qwen3-coder:480b-cloud
 ```
 
-`OLLAMA_MODEL` selects the model name and takes precedence over `UR_MODEL`. If neither is set, UR lets its Ollama router choose from the model list advertised by the local Ollama app. If that discovery fails, the built-in fallback is `qwen3-coder:480b-cloud`. Neither variable can change the endpoint.
+`OLLAMA_MODEL` selects the model name and takes precedence over `UR_MODEL`. If neither is set, UR lets its Ollama router choose from the model list advertised by the configured Ollama app. If that discovery fails, the built-in fallback is `qwen3-coder:480b-cloud`.
+
+### Discovering LAN Ollama servers
+
+UR can scan your active local subnets for other Ollama servers and show a picker. This works for both wired Ethernet and wireless (Wi-Fi/WLAN) interfaces:
+
+```sh
+ur --discover-ollama
+```
+
+This is **session-only**: the picker appears and the chosen host is used for
+that session, but plain `ur` continues to use `localhost:11434` unless you set
+`ollama.host` explicitly.
+
+To make the picker appear on every startup, enable it in user settings:
+
+```json
+{
+  "ollama": {
+    "lanDiscovery": true
+  }
+}
+```
+
+The scan is limited to active local IPv4 interfaces, ignores loopback/link-local
+addresses, and uses bounded concurrency with short timeouts. It is opt-in and
+never runs automatically unless enabled.
 
 ## CLI Flags
 

package/docs/USAGE.md

@@ -64,7 +64,25 @@ ur --model qwen3-coder:480b-cloud
 ur --model qwen2.5-coder:latest
 ```
 
-UR talks only to the local Ollama app at the fixed endpoint `http://localhost:11434/api`. The endpoint cannot be changed from UR. Models exposed by that local app are valid, including Ollama Cloud-backed models. UR does not call provider APIs directly or manage model API keys.
+UR talks to the local Ollama app at `http://localhost:11434/api` by default, but you can point it at another Ollama server on your LAN or in another location:
+
+```sh
+# Discover and pick a LAN Ollama server at startup (session only)
+ur --discover-ollama
+
+# Point to a specific Ollama server for this session
+ur --ollama-host http://192.168.1.50:11434
+
+# Persistent setting (plain `ur` uses this host automatically)
+ur --settings '{"ollama":{"host":"http://192.168.1.50:11434"}}'
+```
+
+Precedence: `--ollama-host` > `OLLAMA_HOST` env > `ollama.host` setting > `localhost:11434`.
+
+`--discover-ollama` shows the picker every time but does **not** save the choice;
+use `ollama.host` in settings if you want plain `ur` to default to a LAN host.
+
+Models exposed by the chosen Ollama app are valid, including local models and Ollama Cloud-backed models. UR does not call provider APIs directly or manage model API keys.
 
 ## Project Instructions
 

package/docs/VALIDATION.md

@@ -8,7 +8,8 @@ You need:
 
 - A running Ollama server (`ollama serve`) with at least one model available
   in the local Ollama app. Local models and Ollama Cloud-backed models both
-  work because UR talks to the local app.
+  work because UR talks to the configured Ollama host.
+- A second Ollama server on the LAN if you want to test network discovery.
 - UR installed globally (`npm install -g ur-agent`) or this repo installed
   globally (`bun add -g github:Maitham16/UR-mapek`) or a
   local checkout (`bun run dev`).
@@ -17,7 +18,25 @@ You need:
 
 ```sh
 ur --version
-# expected: 1.15.0 (Ur)
+# expected: 1.16.0 (Ur)
+```
+
+## 0.1 Network Ollama discovery (1.16.0)
+
+With at least one other Ollama server reachable on your LAN:
+
+```sh
+ur --discover-ollama
+```
+
+Expected: a picker appears listing `This computer` plus the LAN host(s). Select
+the LAN host, then run a prompt and confirm traffic goes to the selected host.
+
+Without a LAN host, you can still verify host configuration:
+
+```sh
+ur --ollama-host http://localhost:11434 -p "say hi"
+ur --settings '{"ollama":{"host":"http://localhost:11434"}}' -p "say hi"
 ```
 
 ## 1. Marketplace tree resolves

package/extensions/vscode-ur-inline-diffs/package.json

@@ -2,7 +2,7 @@
   "name": "ur-inline-diffs",
   "displayName": "UR Inline Diffs",
   "description": "Review UR inline diff bundles from .ur/ide/diffs inside VS Code.",
-  "version": "1.15.0",
+  "version": "1.16.1",
   "publisher": "ur-agent",
   "engines": {
     "vscode": "^1.92.0"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ur-agent",
-  "version": "1.15.0",
+  "version": "1.16.1",
   "description": "UR terminal coding agent CLI",
   "type": "module",
   "packageManager": "bun@1.3.14",