@gencode/web 0.3.22 → 0.5.0

package/CHANGELOG.md

@@ -1,5 +1,49 @@
 # @gencode/web
 
+## 0.5.0
+
+### Minor Changes
+
+- 40ba841: Thread Goal now exposes a single minimal `goal` model tool by default. Users still manage goals through CLI commands and Console `/goal`; the model-facing tool is only used to submit terminal `complete` or `blocked` status, while task planning, evidence recording, and workflow repair stay internal to the runtime and no longer appear in the default tool list or session tool snapshots.
+- 32c7221: Agents can now publish lightweight task plans with the built-in `update_task` tool during multi-step work. Agents are instructed to publish an initial plan before substantive multi-step work, advance it after user-visible steps, and, for explicit numbered or bulleted user steps, update the completed step before starting the next one so several completed steps are not batched into one late update. Callback and websocket consumers receive these snapshots as normal progress events with `event.type: "task_updated"`, including `toolCallId`, optional `explanation`, `updatedAt`, and ordered task items whose status is `pending`, `in_progress`, or `completed`. Console displays the latest task snapshot in the event timeline, while dependency-chain entrypoints are versioned so installing the latest CLI, Web bridge, server, or plugin SDK packages picks up the new runtime and shared progress protocol. AIMax does not create a separate task-plan store, so reconnect/resume behavior continues to rely on the transcript and progress stream.
+
+### Patch Changes
+
+- 132ee84: CRON channel runs now keep their session data, logs, and subagent outputs under `<dataDir>/.aimax/crons/<sessionId>/`. Root CRON logs are written to `<dataDir>/.aimax/crons/<sessionId>/logs/<messageId>/`, and subagents spawned by the CRON run are nested under `<dataDir>/.aimax/crons/<sessionId>/subagents/<childSessionId>/` with their own logs, transcript, context, and tool-results. This prevents CRON diagnostics and subagent files from escaping into the default `.aimax/sessions/` store or into top-level sibling `crons` sessions.
+- 89f1931: AIMax now protects agent runs from stalled plugin hooks. Hooks that only observe lifecycle events, such as session, turn, LLM, agent-end, and memory change notifications, run with a per-plugin timeout and report a plugin diagnostic if one plugin hangs or fails, while the main run continues toward its normal done or error callback. Hooks whose return values control the run, such as prompt, model, tool, context, resource, and compaction hooks, also run with a timeout but surface a clear failure to the run instead of hanging indefinitely.
+- Updated dependencies [32c7221]
+- Updated dependencies [132ee84]
+- Updated dependencies [89f1931]
+- Updated dependencies [40ba841]
+- Updated dependencies [32c7221]
+  - @gencode/console@0.5.0
+  - @gencode/shared@0.4.0
+
+## 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/console@0.4.0
+
 ## 0.3.22
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gencode/web",
-  "version": "0.3.22",
+  "version": "0.5.0",
   "type": "module",
   "exports": {
     ".": {
@@ -13,8 +13,8 @@
     "CHANGELOG.md"
   ],
   "dependencies": {
-    "@gencode/console": "0.3.22",
-    "@gencode/shared": "0.3.0"
+    "@gencode/console": "0.5.0",
+    "@gencode/shared": "0.4.0"
   },
   "devDependencies": {},
   "scripts": {