ur-agent 1.84.3 → 1.84.4

package/docs/CONFIGURATION.md

@@ -143,6 +143,27 @@ ur config set base_url <url>
 ur config set base_url <provider> <url>
 ```
 
+OpenRouter's default `auto` policy keeps its current Auto Exacto ordering for
+tool turns and prioritizes end-to-end throughput for ordinary text turns.
+Every performance choice is explicit and editable:
+
+```sh
+ur config set openrouter.routing auto          # auto | throughput | latency | price
+ur config set openrouter.allow_fallbacks true    # true | false | auto
+ur config set openrouter.require_parameters true # true | false | auto
+ur config set openrouter.preferred_min_throughput 40
+ur config set openrouter.preferred_max_latency 3
+ur config set openrouter.service_tier priority # auto | default | flex | priority | fast
+ur config set openrouter.speed fast            # standard | fast
+ur config set model <openrouter-model>:nitro   # or :floor / :exacto
+```
+
+Thresholds are preferences, not exclusions. `priority` and `fast` can increase
+price and apply only where OpenRouter advertises upstream support; their
+default `auto`/`standard` values add no premium request. Explicit request-level
+provider preferences still win. Set either performance threshold to `auto` to
+remove it and return to OpenRouter's own routing data.
+
 `provider.fallback` is diagnostic recovery metadata, not automatic routing.
 When the active provider fails, `ur provider doctor` shows the configured
 recovery command; changing providers remains an explicit user action.
@@ -242,7 +263,10 @@ UNSLOTH_API_KEY=...
 
 NVIDIA NIM defaults to `https://integrate.api.nvidia.com/v1`, discovers the
 connected account's models live, and accepts a provider-scoped override for an
-enterprise or self-hosted NIM. Generic `openai-compatible` authentication is
+enterprise or self-hosted NIM. On NVIDIA's hosted endpoint, UR intersects the
+broad `/v1/models` feed with the key's ACTIVE NVCF function inventory and omits
+non-agent utility endpoints; a configured NIM gateway uses its own model feed
+without contacting NVIDIA's hosted control plane. Generic `openai-compatible` authentication is
 optional: `ur connect openai-compatible` or the picker's `K` key stores a
 credential when the chosen gateway needs one, without breaking anonymous
 local endpoints.

package/docs/TROUBLESHOOTING.md

@@ -210,6 +210,39 @@ press `K` on its `/model` screen; the key is optional and stored separately
 from `OPENAI_API_KEY`. NVIDIA NIM uses `ur connect nvidia-nim` and keeps any
 custom `base_url` scoped to that provider.
 
+### NVIDIA lists a model but inference returns `Function … Not found for account`
+
+- Cause: NVIDIA's hosted `/v1/models` feed can contain a function that is no
+  longer ACTIVE for the connected account.
+- Fix: upgrade UR, run `ur provider doctor nvidia-nim`, then open `/model` and
+  press `Ctrl+R`. Hosted discovery now intersects `/v1/models` with NVIDIA's
+  authenticated ACTIVE function inventory and excludes non-agent utility
+  endpoints. A definitive runtime 404 also removes that model from the current
+  endpoint-scoped session catalog.
+- Privacy: UR does not display or retain the internal NVIDIA function UUID and
+  account identifier from this error response.
+
+If `account_models` fails, reconnect a current build.nvidia.com key with
+`ur connect nvidia-nim`. A configured enterprise/self-hosted NIM endpoint is
+validated only against that gateway and does not use NVIDIA's hosted inventory.
+
+### `The provider reported that model … reached its per-response output boundary`
+
+This is not an input-context overflow and does not mean UR counted the text
+incorrectly. The provider ended the generation with its `max_tokens`/`length`
+finish reason on a response chunk whose boundary was the displayed value. The
+normal query loop silently continues from the exact cutoff with no fixed total
+continuation ceiling while every capped response adds novel work. It stops only
+after two consecutive empty or replayed capped responses, which indicates a
+stalled model loop rather than a long task.
+
+`UR_CODE_MAX_OUTPUT_TOKENS` changes only the per-response chunk, up to the
+model's discovered limit; it does not impose or remove a total task limit.
+Cloud requests use a practical chunk so routers retain fast endpoint choices,
+and local runtimes use a smaller reservation to avoid unnecessary KV-memory
+allocation. If the stalled-loop message appears, inspect the prompt/model for
+repetition before retrying.
+
 ### Unsloth is selected but unavailable
 
 - Likely cause: Studio is not running, no model is loaded, its generated API

package/docs/USAGE.md

@@ -173,6 +173,23 @@ ur config set responses.compact_threshold 20000
 ur config set responses.tool_search hosted
 ```
 
+For OpenRouter, UR preserves Auto Exacto on tool turns and uses throughput
+routing on non-tool turns. Tune that provider without hardcoded endpoints or
+request patches:
+
+```sh
+ur config set openrouter.routing auto
+ur config set openrouter.preferred_min_throughput 40
+ur config set openrouter.preferred_max_latency 3
+ur config set openrouter.service_tier priority
+ur config set openrouter.speed fast
+```
+
+`auto` is the recommended default. `priority`/`fast` are optional paid upstream
+features and are effective only for models that OpenRouter supports. Append
+`:nitro`, `:floor`, or `:exacto` to an OpenRouter model ID for its native
+throughput-, price-, or tool-quality-first virtual route.
+
 `provider.fallback` only controls the recovery suggestion printed by provider
 diagnostics. UR does not switch or retry across providers automatically; use
 `ur config set provider <id>` after reviewing the failure.
@@ -240,7 +257,11 @@ API-key access, and an API key does not grant subscription CLI access.
 NVIDIA NIM uses the build.nvidia.com key and hosted
 `https://integrate.api.nvidia.com/v1` endpoint by default. Connect it with
 `ur connect nvidia-nim`; use `ur config set base_url nvidia-nim <url>` for a
-different NIM deployment. On the `/model` model screen, `K` adds or replaces a
+different NIM deployment. For the hosted endpoint, `/model` shows only models
+that occur in both NVIDIA's `/v1/models` feed and the connected account's
+ACTIVE function inventory; utility endpoints such as embeddings, guards, and
+parsers are excluded. A custom NIM gateway retains its own independent catalog.
+On the `/model` model screen, `K` adds or replaces a
 provider API key and `E` edits its endpoint. This also makes optional
 authentication practical for generic OpenAI-compatible gateways.
 

package/docs/VALIDATION.md

@@ -19,7 +19,7 @@ You need:
 
 ```sh
 ur --version
-# expected for this release: "1.84.3 (UR-Nexus)"
+# expected for this release: "1.84.4 (UR-Nexus)"
 ```
 
 ### 0.0 Redteam mode and Reverse Skills (1.81.0)
@@ -72,7 +72,7 @@ changes must remain blocked. The deterministic regressions are:
 bun test test/taskListGate.test.ts test/toolExecutionFinalInput.test.ts
 ```
 
-### 0.0.0 OpenRouter research routing and provider UI (1.81.3; Ultra mapping updated 1.83.1)
+### 0.0.0 OpenRouter research routing and provider UI (routing updated 1.84.4)
 
 Connect OpenRouter, run `/model`, select OpenRouter, and verify that its model
 step shows catalog freshness plus pricing/context/tool/reasoning details. Focus
@@ -100,15 +100,58 @@ the auxiliary request stays on the active OpenRouter model, no `modelH` error
 appears, a real provider search count is shown, and a response that did not
 perform a search fails clearly instead of saying `Did 0 searches`.
 
+Inspect the OpenRouter request body. A turn containing tools must not contain a
+default `provider.sort`, leaving Auto Exacto active; a text-only request must
+contain `provider.sort="throughput"`. Both retain the stable `session_id`.
+Then verify explicit controls and native virtual variants:
+
+```sh
+ur config set openrouter.routing latency
+ur config set openrouter.allow_fallbacks true
+ur config set openrouter.require_parameters true
+ur config set openrouter.preferred_min_throughput 40
+ur config set openrouter.preferred_max_latency 3
+ur config set openrouter.service_tier priority
+ur config set openrouter.speed fast
+ur config set model <discovered-openrouter-model>:nitro
+```
+
+The forced routing value must appear on both tool and non-tool requests;
+fallback/threshold settings must use OpenRouter's snake-case wire keys;
+`priority`/`fast` must appear only when explicitly selected. `:nitro` must
+validate against the discovered base model and inherit its context, output,
+tool, and reasoning metadata.
+
 Deterministic coverage:
 
 ```sh
 bun test test/providerPickerPresentation.test.ts \
   test/openRouterEffort.test.ts test/providerModelDiscovery.test.ts \
   test/secondaryModelFallback.test.ts test/providerToolCalls.test.ts \
+  test/providerContextWindow.test.ts test/outputLimitRecovery.test.ts \
   test/usageAccounting.test.ts test/providerRouting.test.ts
 ```
 
+### 0.0.0a Provider output-boundary continuation (1.84.4)
+
+Use a provider fixture that returns `max_tokens`/`length` after non-empty
+partial output. UR must withhold the intermediate API error, add a continuation
+turn that requests only novel work from the exact cutoff, and continue for more
+than three responses while every response progresses. The original prompt,
+tool state, and completed output remain in context. Two consecutive empty or
+exact-replay capped responses must stop with the stalled-loop diagnostic.
+
+The per-request `max_tokens` value remains bounded by live/static model
+metadata. A model with a 128K advertised output ceiling uses a practical 32K
+default response chunk; `UR_CODE_MAX_OUTPUT_TOKENS` may raise that chunk to
+128K, but neither value creates a total task-output ceiling. Local/user-hosted
+runtimes use their conservative 4K reservation and the same continuation path.
+
+```sh
+bun test test/outputLimitRecovery.test.ts \
+  test/providerRequestTuning.test.ts test/providerContextWindow.test.ts
+```
+
 ### 0.0.1 Unavailable Ollama tools recover (1.80.7)
 
 With an Ollama model, ask for research that mentions WebSearch. If WebSearch is
@@ -198,8 +241,11 @@ NVIDIA NIM, Ollama, LM Studio, llama.cpp, vLLM, Unsloth, and generic OpenAI-comp
 request shapes.
 
 The NVIDIA fixture also verifies hosted/default and overridden endpoints,
-Bearer discovery, native dispatch, documented effort aliases, and no Ultra on
-an unknown model. In `/model`, select `openai-compatible` and verify `K` can
+Bearer discovery, intersection with account-active NVCF functions, removal of
+retired and non-agent models, selected-model doctor diagnostics, redaction of
+internal NVIDIA account/function IDs, endpoint-scoped invalidation, native
+dispatch, documented effort aliases, and no Ultra on an unknown model. In
+`/model`, select `openai-compatible` and verify `K` can
 add or replace its optional key while `E` continues to edit only its endpoint.
 
 ## 0.2 Permission safety and context pack (1.19.0)

package/docs/providers.md

@@ -263,10 +263,17 @@ shows pricing tier, context size, tool capability, reasoning capability, and
 the full, untruncated model ID immediately below the focused entry. Opening the
 OpenRouter catalog reuses its endpoint-scoped five-minute cache; Ctrl+R forces
 the current `/models` endpoint and never substitutes a cached list when that
-forced refresh fails. Interactive requests default to OpenRouter's latency
-sorting, promote UR's stable session ID for sticky routing, and preserve safe
-provider prompt-cache markers. Explicit routing preferences and the `:nitro`,
-`:floor`, and `:exacto` model variants remain authoritative. API-key entry for
+forced refresh fails. Tool requests preserve OpenRouter Auto Exacto so its live
+throughput, tool-call reliability, and benchmark signals choose the route;
+non-tool requests default to throughput sorting rather than TTFT-only latency
+sorting. UR promotes its stable session ID for prompt-cache affinity while
+retaining router fallback. Explicit request preferences, the `openrouter.*`
+configuration controls, and the `:nitro`, `:floor`, and `:exacto` model variants
+remain authoritative. See OpenRouter's
+[provider routing](https://openrouter.ai/docs/guides/routing/provider-selection),
+[Auto Exacto](https://openrouter.ai/docs/guides/routing/auto-exacto), and
+[prompt caching](https://openrouter.ai/docs/guides/best-practices/prompt-caching).
+API-key entry for
 OpenAI, Claude, Gemini, OpenRouter, NVIDIA NIM, and authenticated compatible
 endpoints is a single aligned masked row; the key is stored in the OS keychain
 flow and is never written to settings. On the model screen, `K` adds or
@@ -420,7 +427,7 @@ ur config set provider anthropic-api
 | --- | --- | --- |
 | API providers (openai-api, anthropic-api, gemini-api) | Live discovery from the provider's `/models` endpoint using your connected key (curated fallback until connected) | live |
 | OpenRouter | Live `/models` discovery with an endpoint-scoped five-minute cache; Ctrl+R forces a fresh request with no stale fallback | live/cache |
-| NVIDIA NIM | Live `/models` discovery from the hosted or configured NIM endpoint; no stale offline model catalog | live |
+| NVIDIA NIM | Hosted: live `/models` intersected with the connected account's ACTIVE NVCF functions, then restricted to agent/chat endpoints. Configured NIM gateway: its own live `/models` catalog | live |
 | Local/server providers (ollama, lmstudio, llama.cpp, vllm, unsloth) | Dynamic discovery from the selected provider endpoint | live |
 | OpenAI-compatible | Dynamic discovery from configured endpoint | live |
 | Subscription CLIs (codex-cli, claude-code-cli, gemini-cli, antigravity-cli) | Curated list (the official CLIs expose no models API); first-class in `/model`, dispatched via the official CLI. External CLI behavior depends on the vendor CLI. Log in with `ur auth <provider>` | static |
@@ -657,15 +664,28 @@ ur provider doctor nvidia-nim
 ur config set base_url nvidia-nim https://nim-gateway.example/v1
 ```
 
-The default is `https://integrate.api.nvidia.com/v1`. UR calls `/models`,
-`/chat/completions`, and, when available, `/messages/count_tokens`; native
+The default is `https://integrate.api.nvidia.com/v1`. NVIDIA's hosted
+`/v1/models` response can be broader than the functions that the connected
+account can actually invoke. UR therefore intersects it with the authenticated
+NVCF `GET /v2/nvcf/functions` inventory, keeps only `ACTIVE` matches, and
+removes embedding, guard, parser, translation, reward, and similar non-agent
+endpoints. A custom enterprise or self-hosted NIM remains independent and uses
+only that configured gateway's `/models` response.
+
+UR calls `/models`, `/chat/completions`, and, when available, `/messages/count_tokens`; native
 count failure falls back to a provider-wire estimate and never launches a
 hidden completion. Streaming, standard tool calls, and image input use the
 same OpenAI-compatible adapter. Vision and tools remain model-dependent. For
 documented Nemotron coding-agent models, UR includes NVIDIA's
 `force_nonempty_content` template option when tools are present. See NVIDIA's
 [NIM LLM API reference](https://docs.api.nvidia.com/nim/reference/llm-apis)
-and [NIM function-calling API](https://docs.nvidia.com/nim/large-language-models/latest/function-calling.html).
+and [NVCF API scope reference](https://docs.nvidia.com/nvcf/api#scope-reference).
+
+`ur provider doctor nvidia-nim` verifies both the hosted catalog and the
+selected model against the account-active inventory. If NVIDIA retires a
+function after selection, UR redacts NVIDIA's internal function/account IDs,
+removes that model from the current endpoint-scoped session catalog, and asks
+the user to select an active model. `Ctrl+R` explicitly retries discovery.
 
 Local/server providers use their normal endpoints:
 

package/documentation/index.html

@@ -45,7 +45,7 @@
     <main id="content" class="content">
       <header class="topbar">
         <div>
-          <p class="eyebrow">Version 1.84.3</p>
+          <p class="eyebrow">Version 1.84.4</p>
           <h1>UR-Nexus Documentation</h1>
           <p class="lead">A practical, tutorial-style reference for installing, configuring, automating, extending, and operating UR-Nexus.</p>
         </div>
@@ -187,7 +187,7 @@ ur --model kimi-k3:cloud --effort high
             <h3>OpenRouter responsive routing</h3>
             <pre><code>ur config set provider openrouter
 /model  # cached catalog; Ctrl+R forces live refresh</code></pre>
-            <p>The endpoint-scoped model catalog is reused for five minutes, while forced refresh never substitutes stale data. Interactive requests prefer OpenRouter latency routing, a stable session ID, and provider-authored prompt-cache markers; explicit routing preferences and model variants still win.</p>
+            <p>The endpoint-scoped model catalog is reused for five minutes, while forced refresh never substitutes stale data. Tool turns preserve OpenRouter Auto Exacto for live throughput and tool-call reliability; non-tool turns prefer end-to-end throughput. Stable session affinity keeps prompt caches warm, while configurable routing preferences and the <code>:nitro</code>, <code>:floor</code>, and <code>:exacto</code> variants remain authoritative.</p>
           </article>
           <article>
             <h3>NVIDIA NIM and compatible API keys</h3>

package/extensions/jetbrains-ur/build.gradle.kts

@@ -7,7 +7,7 @@ plugins {
 }
 
 group = "dev.urnexus"
-version = "1.84.3"
+version = "1.84.4"
 
 repositories {
     mavenCentral()

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

@@ -2,7 +2,7 @@
   "name": "ur-inline-diffs",
   "displayName": "UR Inline Diffs",
   "description": "Review, apply, and reject UR inline diff bundles from .ur/ide/diffs inside VS Code.",
-  "version": "1.84.3",
+  "version": "1.84.4",
   "publisher": "ur-nexus",
   "engines": {
     "vscode": "^1.92.0"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ur-agent",
-  "version": "1.84.3",
+  "version": "1.84.4",
   "description": "UR-Nexus — autonomous engineering workflow engine (plan, execute, test, verify, document, benchmark, reproduce)",
   "type": "module",
   "packageManager": "bun@1.3.14",