@cubicecho/agent-core 2.2.3 → 2.2.4

package/README.md

@@ -82,6 +82,12 @@ again, with the setting still reading `high` and nothing anywhere saying it had
 So they hang off the endpoint under the name the endpoint knows the model by. Pass `model` and
 the same loop answers both levels; leave it out and nothing changes.
 
+A refusal of the *value* is not one of these, however alike the two read: an effort off a list
+this package does not know, a `max_tokens` larger than the model's ceiling, a temperature out of
+range. Dropping the field answers those too — at the model's own default, latched for the rest of
+the process, with the settings row still reading what was typed and nothing saying it had stopped
+meaning it. They are passed to the caller instead, where whoever typed the number can see it.
+
 ```ts
 const turn = await negotiate(supports, (supports, produced, model) =>
   streamTurn(

package/dist/capabilities.js

@@ -94,13 +94,37 @@ const rejectsEffort = (detail) => /reasoning_effort/i.test(detail) && !REFUSED_V
  * whoever typed the number can see it.
  */
 const wantsCompletionLimit = (detail) => /max_tokens/i.test(detail) && /max_completion_tokens/i.test(detail);
+/**
+ * Temperature named as the field being refused, rather than mentioned in passing.
+ *
+ * A bare search of the message is not that question. `Unsupported value: 'top_p' does not
+ * support 3 with this model. Adjust temperature instead.` refuses another field and merely says
+ * the word, and it disabled ours — the word is ordinary English about a model, so any advice,
+ * aside or list that reaches for it counted. OpenAI quotes the field it is refusing, which is
+ * the anchor; the second half is a server that writes the same clause without the quotes.
+ */
+const NAMES_TEMPERATURE = /(['"`])temperature\1|\btemperature\s+(?:is|does|must|can)\b/i;
 /**
  * `'temperature' does not support 0.7 with this model. Only the default (1) is supported.`
  *
- * The qualifier is load-bearing. A temperature out of range is the caller's mistake to see
- * rather than ours to work around, and dropping the field would hide it.
+ * The qualifier is load-bearing, and `does not support` is not the qualifier: that is how a
+ * server words a refusal of the *value* — `Invalid value: 'temperature' does not support 5.
+ * Supported values are between 0 and 2.` — which is the caller's mistake to see rather than
+ * ours to work around. Dropping the field there succeeds, at the model's own default, so a
+ * number the operator typed and can still read on a settings row is silently replaced by one
+ * nobody chose, for the life of the process. `only the default` is the whole of what separates
+ * the two: it says the field takes one value, where the generic phrasing says only that this
+ * value was the wrong one.
+ *
+ * `REFUSED_VALUE` cannot be borrowed from `rejectsEffort` to draw that line, which is why this
+ * has no such guard rather than having lost one — the genuine refusal above opens with
+ * `Unsupported value:` too, so the guard would reject the one message that has to latch.
+ *
+ * It under-matches an endpoint that refuses the field in some third wording, which is the
+ * direction this file argues for on `max_tokens` and on `reasoning_effort`: a false negative
+ * costs one visible error, and a false positive quietly changes what every later request means.
  */
-const refusesChosenTemperature = (detail) => /temperature/i.test(detail) && /only the default|does not support/i.test(detail);
+const refusesChosenTemperature = (detail) => NAMES_TEMPERATURE.test(detail) && /only the default/i.test(detail);
 /**
  * Sends a request, re-sending it each time the answer is this endpoint refusing something the
  * request can do without. Returns once the endpoint has answered, or throws if the refusal is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cubicecho/agent-core",
-  "version": "2.2.3",
+  "version": "2.2.4",
   "description": "The endpoint-agnostic half of an OpenAI-compatible agent loop: tool-schema compatibility, on-demand tool loading, one-shot side tasks, run events, and a pooled client.",
   "keywords": [
     "openai",