triss-coworker 0.22.0 → 0.22.2

package/CHANGELOG.md

@@ -7,6 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.22.2] — 2026-07-04
+
+### Changed
+
+- `triss_coder_run` (MCP): the default timeout is now **1500s (25 min)**,
+  up from 300s and above the CLI's 900s, since GLM/opencode runs over MCP
+  are expected to be long. A stdio MCP server has no client-side per-call
+  cap (Claude Code's `MCP_TOOL_TIMEOUT` is effectively unlimited; the 300s
+  idle timeout applies only to remote transports), so triss's own timer is
+  the real bound. Override per call via the `timeout` arg.
+
+## [0.22.1] — 2026-07-04
+
+### Fixed
+
+- `triss config wizard` → coder: the Z.AI plan auto-detection now sees a
+  freshly-entered `ZHIPU_API_KEY` (the wizard saves the key to the env file
+  without touching `process.env`; `runCoderSetup` now reloads env files
+  itself). The direct `triss coder init` path was unaffected.
+
 ## [0.22.0] — 2026-07-04
 
 ### Added
@@ -519,7 +539,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Initial release of `triss-coworker`.
 
-[Unreleased]: https://github.com/ayleen/triss-coworker/compare/v0.22.0...HEAD
+[Unreleased]: https://github.com/ayleen/triss-coworker/compare/v0.22.2...HEAD
+[0.22.2]: https://github.com/ayleen/triss-coworker/compare/v0.22.1...v0.22.2
+[0.22.1]: https://github.com/ayleen/triss-coworker/compare/v0.22.0...v0.22.1
 [0.22.0]: https://github.com/ayleen/triss-coworker/compare/v0.21.0...v0.22.0
 [0.21.0]: https://github.com/ayleen/triss-coworker/compare/v0.20.1...v0.21.0
 [0.20.1]: https://github.com/ayleen/triss-coworker/compare/v0.20.0...v0.20.1

package/README.md

@@ -238,8 +238,9 @@ The exposed tool set is **filtered by configured credentials**:
 - **`triss_gitlab_*`** when `GITLAB_TOKEN` is set.
 - **`triss_coder_run` + `triss_coder_status`** when `ZHIPU_API_KEY` is set
   (setup: `triss coder init`). `triss_coder_run`'s timeout defaults to
-  300s over MCP, not the CLI's 900s — long tasks should go through
-  `triss coder run` on the CLI instead.
+  1500s (25 min) over MCP, above the CLI's 900s, since GLM runs are
+  expected to be long; override per call via the `timeout` arg. For
+  runs that may exceed it, use `triss coder run` on the CLI instead.
 
 Add credentials later → restart session → new tools appear automatically.
 

package/docs/coder-agent-plan.md

@@ -366,10 +366,11 @@ Phase 1; do NOT create a full `src/integrations/coder/` directory, this is
 not a tracker integration).
 Handlers in `src/mcp/handlers.js` call the same functions as the CLI.
 `triss_coder_run` in MCP mode must enforce the `safety.js` sandbox (Phase 2
-note 6). MCP hosts often time tool calls out before the CLI's 900 s
-default — use a lower MCP-side default timeout (300 s), document the
-constraint in `docs/mcp.md`, and point long tasks to the CLI-in-background
-path in the templates rule.
+note 6). GLM runs over MCP are expected to be long, and stdio MCP has no
+client-side per-call cap — use a generous MCP-side default timeout
+(1500 s), allow per-call override via the `timeout` arg, document the
+constraint in `docs/mcp.md`, and point runs that may exceed it to the
+CLI-in-background path in the templates rule.
 
 ## Phase 5 — docs lockstep + tests (definition of done)
 

package/docs/mcp.md

@@ -283,10 +283,13 @@ Exposed **only when ZHIPU_API_KEY is set** (setup: `triss coder init` or
   `ZHIPU_API_KEY` presence (never the value), which `opencode.json` files
   exist, and how many isolation worktrees are live.
 
-**Timeout is lower over MCP than on the CLI: 300s, not 900s.** MCP hosts
-commonly time out a tool call before a long coding task finishes. For
-anything that might run long, use `triss coder run` on the CLI instead
-(optionally backgrounded) rather than `triss_coder_run`.
+**Timeout defaults to 1500s (25 min) over MCP**, above the CLI's 900s,
+since GLM runs over MCP are expected to be long. Override per call via
+the `timeout` arg. Stdio MCP has no client-side per-call cap of its own
+(Claude Code's `MCP_TOOL_TIMEOUT` is effectively unlimited, and the 300s
+idle timeout applies only to remote transports), so this value is the
+real bound. For runs that may exceed it, use `triss coder run` on the
+CLI instead (optionally backgrounded) rather than `triss_coder_run`.
 
 **Sandbox:** an explicit `cwd`, and (with `isolate`) the git repository
 root that `.triss/wt/<slug>` will be created under, are both checked

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "triss-coworker",
-  "version": "0.22.0",
+  "version": "0.22.2",
   "description": "Give your AI coding agent a cheap DeepSeek coworker. Delegate bulk reads, boilerplate, and doc updates to save 60-70% of your token budget.",
   "type": "module",
   "bin": {

package/src/commands/coder.js

@@ -277,6 +277,17 @@ async function setupKey(path) {
 // instead of driving real stdin. `deps.fetch` / `deps.promptChoice` let
 // tests stub the provider probe and the interactive model pick.
 export async function runCoderSetup({ scope } = {}, deps = {}) {
+  // `triss coder init` calls loadEnvFiles() itself before setupKey() runs,
+  // so ZHIPU_API_KEY is already in process.env by the time this function
+  // is reached from that path. But CODER_MANIFEST.postSetup (the
+  // `triss config wizard` path) calls runCoderSetup directly: the
+  // generic env-var loop writes the key to the .env FILE via setVar(),
+  // never to process.env. Without reloading here, detectAndReportZaiProvider
+  // below reads an unset ZHIPU_API_KEY on a first-time wizard setup,
+  // silently skips detection, and falls back to the default provider
+  // prefix. override:false + uncached (see config.js) makes this a safe,
+  // idempotent no-op when the key is already loaded.
+  loadEnvFiles();
   const resolvedScope = scope || 'global';
   const sh = deps.spawnSync || nodeSpawnSync;
   process.stderr.write('\n' + pc.bold('── coder (opencode engine) ──') + '\n');

package/src/mcp/handlers.js

@@ -856,11 +856,13 @@ export async function gitlabCommentHandler({ project, iid, body }) {
 
 // ─── coder ──────────────────────────────────────────────────────────────────
 
-// MCP hosts commonly time out a tool call well before the CLI's 900s
-// default — 300s here, documented in docs/mcp.md. Long tasks should go
-// through `triss coder run` on the CLI (optionally backgrounded), not
-// this tool.
-const CODER_MCP_DEFAULT_TIMEOUT = 300;
+// GLM/opencode runs over MCP are expected to be long, so the default is
+// generous — 1500s (25 min), above the CLI's 900s, documented in
+// docs/mcp.md. Stdio MCP has no client-side per-call cap (Claude Code's
+// MCP_TOOL_TIMEOUT is effectively unlimited, and the 300s idle timeout
+// only applies to remote transports), so triss's own timeout is the
+// real bound. Callers can override per request via the `timeout` arg.
+const CODER_MCP_DEFAULT_TIMEOUT = 1500;
 
 // `deps` (spawn/spawnSync) is only ever populated by tests — production
 // calls always fall through to the real subprocess machinery inside

package/src/mcp/tools.js

@@ -817,9 +817,10 @@ const CODER_TOOLS = [
       'engine, set up via `triss coder init`). Returns a JSON envelope: ' +
       '{engine, engine_version, session_id, exit_reason, final_text, ' +
       'files_changed, diff_stat, worktree, usage, warnings}. This tool\'s ' +
-      'timeout defaults to 300s (vs 900s on the CLI) since MCP hosts often ' +
-      'time out long tool calls — for anything that might run long, use ' +
-      '`triss coder run` on the CLI instead (optionally backgrounded).',
+      'timeout defaults to 1500s (25 min) since GLM runs over MCP are ' +
+      'expected to be long; override per call via the `timeout` arg. For ' +
+      'runs that may exceed that, use `triss coder run` on the CLI ' +
+      '(optionally backgrounded).',
     inputSchema: {
       type: 'object',
       properties: {
@@ -834,7 +835,7 @@ const CODER_TOOLS = [
         model: { type: 'string', description: 'Override the model for this run only' },
         isolate: { type: 'boolean', description: 'Run in a disposable git worktree under .triss/wt/<slug>' },
         cwd: { type: 'string', description: 'Working directory (ignored with isolate; sandboxed under MCP)' },
-        timeout: { type: 'number', description: 'Seconds before the engine is killed (default 300 over MCP)' },
+        timeout: { type: 'number', description: 'Seconds before the engine is killed (default 1500 over MCP)' },
       },
       required: ['prompt'],
     },