@gencode/agents 0.9.3 → 0.10.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # @gencode/agents
 
+## 0.10.0
+
+### Minor Changes
+
+- c0def9b: `runAgent` now accepts an optional `env` field on `AgentRunParams` for passing session-scoped environment variables that are isolated to the current run. When supplied, the map is merged into the environment of every child process spawned by the built-in `exec` and `process` tools, and is also exposed to plugin scripts through the read-only `api.runtime.session.env` accessor (carried in the plugin runtime context under `env`). When a single `exec` call also passes its own `env`, the merge order is `process.env` < run-level `env` < per-call `env`, so per-call values override the run-level ones. The map is held in memory only for the duration of the run; it is never written to disk and never crosses a session boundary. The `subagent_spawn` and `batch_subagent_spawn` tools now also forward `env` to child runs through the standard `InheritedRunParams` plumbing, so subagent sessions inherit the same session-scoped env without any extra configuration. Downstream entry points that pass `AgentRunParams` through to the runner (`@gencode/cli`, `@gencode/plugin-sdk`, `@gencode/console`, `@gencode/web`) need to be re-released to expose the new field; no other call-site changes are required.
+
+  The `aimax run` command now accepts a new `--env <kvlist>` flag for setting session-scoped env vars from the command line. The value is a comma-separated list of `KEY=VALUE` pairs (e.g. `--env TENANT=acme,TOKEN=secret`); backslash-escape `,` and `=` inside values if you need literal ones, and use `KEY=` to pass an empty string. The parsed map is forwarded as `AgentRunParams.env`, so the merge order, plugin visibility, and subagent inheritance described above all apply to CLI runs as well. The start banner shows only the number of keys injected — values are never printed.
+
+### Patch Changes
+
+- 364c7d9: Improves long-session context compaction stability. Session memory, automatic compaction, manual `/compact`, and context-limit recovery now build summarisation requests from bounded context views, so large historical turns are truncated or omitted before the summariser call instead of being sent as an oversized request. Default CLI behavior is unchanged; the fix applies automatically when continuing long sessions with the configured `--context-window` or `AIMAX_CONTEXT_WINDOW`.
+- 03c58de: Agent runs are now resilient to progress delivery failures that happen immediately after an `exec` tool finishes. If stdout rendering, callback delivery, or websocket progress handling fails while reporting a tool result, `aimax run` logs the progress failure and continues the agent run instead of treating the reporting failure as a fatal task error. Tool result progress output is also normalized to text before rendering, so unusual or empty tool result payloads no longer crash the CLI output path.
+- bcbb53f: Smart topic segmentation can now load its local embedding model from the installed CLI package. Set `AIMAX_EMBEDDING_MODEL_URL` during `@gencode/cli` installation to have the CLI `postinstall` download the model archive into `models/Xenova/bge-small-zh-v1.5/`; leave it unset to skip the download with no network access or install failure. Deployments may also set `AIMAX_EMBEDDING_MODEL_SHA256` to verify the archive. At runtime, `aimax run` and `aimax resume` automatically pass the installed `models/` directory to agents, while missing models continue to degrade without remote model downloads.
+- 379f84e: `AgentRunParams.projectDir` is now honored as the effective session workspace directory. When `aimax run` or `aimax resume` is started with `--project-dir <path>` (or the equivalent `projectDir` field passed through the plugin SDK, console, or web entry point), the agent operates directly on that directory instead of the default `<dataDir>/workspace` mount. When `projectDir` is empty or omitted, the previous `<dataDir>/workspace` layout is preserved unchanged. The `subagent_spawn` and `subagents` tools now also forward `projectDir` to child runs, so subagents started inside a `--project-dir` session share the same project workspace without any extra configuration. The new `resolveWorkspaceDir` helper in `@gencode/agents` is the single source of truth for this rule, used by the runner, the session lifecycle, and the tool factory.
+- d0edcb7: LLM provider errors returned inside an HTTP 200 stream now surface the provider's readable message directly, without the internal `LLM upstream returned an error payload in a 200 stream` prefix. Transient failures that only expose the generic `LLMRequestError` marker are also retried by the existing turn retry policy, while structured provider status codes such as `502`, `500`, and `429` keep the same retry behavior and non-retryable errors such as `404` still fail immediately.
+
 ## 0.9.3
 
 ### Patch Changes