@gencode/console 0.3.21 → 0.4.0

package/CHANGELOG.md

@@ -1,5 +1,37 @@
 # @gencode/console
 
+## 0.4.0
+
+### Minor Changes
+
+- 5af5e22: Add an opt-out switch for LLM session title generation. New sessions now generate a conversational title via the flash model by default (unchanged), but you can skip that LLM call for runs that don't need it — for example batch/one-shot jobs, embedded API usage, or CI.
+
+  - CLI: pass `--disable-title` on `aimax run` or `aimax resume`. It overrides the new env var `AIMAX_DISABLE_TITLE=true`.
+  - Programmatic: set `titleGeneration: { enabled: false }` on `AgentRunParams`.
+
+  When the switch is off, the session still gets a title — it falls back to a truncated version of the first user message, so the session list is never blank. No token cost and no network call happen. The switch controls only title generation; topic segmentation is unaffected. Start-up logs now show the resolved state as `titleGen: enabled|disabled`.
+
+### Patch Changes
+
+- cbd1dba: AIMax now treats `LLMRequestError` model failures as retryable transient LLM failures even when the upstream gateway also reports non-retryable-looking metadata such as `BadRequestError` or HTTP 400. Runs still avoid replaying an attempt after assistant text or tool results have already been produced, and the agent log now records why a retry was skipped with fields such as `reason`, `retryableError`, `attemptRecordCount`, `recordsWithToolResults`, and `recordsWithAssistantText`.
+- cbd1dba: AIMax now retries LLM turns when the streaming connection is torn down mid-response by the network or upstream, instead of failing the whole run on the first attempt.
+
+  Previously, if the HTTP socket was closed while the model was still streaming (for example an upstream gateway or load balancer dropping the connection, surfacing in logs as `streamErrorType="TypeError"`, `streamErrorMessage="terminated"`, `streamErrorCauseCode="UND_ERR_SOCKET"`, or Node errno codes such as `ECONNRESET`/`EPIPE`/`ETIMEDOUT`), the error reached the turn-retry loop without any retryable metadata, so it was treated as a final failure and the run stopped at `attempt=1` even though `maxAttempts` was higher.
+
+  Such transport-level failures are now recognized as transient and replayed within the existing turn-retry budget (default 3 attempts, exponential backoff). No configuration is required — the new behavior is on by default. User-initiated aborts and genuine non-retryable provider errors (e.g. HTTP 4xx with a real status code) are still not retried, and an attempt is still never replayed once assistant text or tool results have been produced.
+
+- Updated dependencies [cbd1dba]
+- Updated dependencies [cbd1dba]
+- Updated dependencies [5af5e22]
+  - @gencode/cli@0.13.0
+
+## 0.3.22
+
+### Patch Changes
+
+- Updated dependencies [8782104]
+  - @gencode/cli@0.12.1
+
 ## 0.3.21
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gencode/console",
-  "version": "0.3.21",
+  "version": "0.4.0",
   "type": "module",
   "bin": {
     "aimax-console": "./dist/server/index.js"
@@ -26,7 +26,7 @@
     "react": "^18.3.1",
     "react-dom": "^18.3.1",
     "ws": "^8.18.0",
-    "@gencode/cli": "0.12.0",
+    "@gencode/cli": "0.13.0",
     "@gencode/shared": "0.3.0"
   },
   "devDependencies": {