Greptile Summary

This PR fixes a cross-platform exec host=node issue where the gateway was injecting its own process.cwd() as the default working directory for a remote node, causing a SYSTEM_RUN_DENIED error when the gateway and node run on different OS platforms (e.g. Linux gateway + Windows node). The fix correctly tracks whether a workdir was explicitly provided, and only forwards it to the remote node when it was — passing undefined otherwise so the node uses its own default.

The logic in bash-tools.exec.ts and bash-tools.exec-host-node.ts is sound. One issue was found: the RequestExecApprovalDecisionParams.cwd field in bash-tools.exec-approval-request.ts was not updated from string to string | undefined alongside HostExecApprovalParams.workdir, creating a TypeScript type mismatch in buildHostApprovalDecisionParams where cwd: params.workdir (string | undefined) is assigned to a cwd: string field.

Confidence Score: 4/5

Mostly safe, but a TypeScript type mismatch in the approval-request types should be fixed before merging to avoid a build failure.

The core fix is correct and well-scoped. However, RequestExecApprovalDecisionParams.cwd was not widened to string | undefined alongside HostExecApprovalParams.workdir, causing buildHostApprovalDecisionParams to produce a type error. This is a P1 build-time issue that needs to be resolved before the PR is ready to merge.

src/agents/bash-tools.exec-approval-request.ts — the RequestExecApprovalDecisionParams.cwd field (line 14) needs to be updated to string | undefined.

This is a comment left during a code review.
Path: src/agents/bash-tools.exec-approval-request.ts
Line: 14

Comment:
**`RequestExecApprovalDecisionParams.cwd` not updated to match**

`buildHostApprovalDecisionParams` (line 213) sets `cwd: params.workdir`, where `params.workdir` is now `string | undefined`. However, `RequestExecApprovalDecisionParams.cwd` is still typed as `cwd: string` — a non-optional, non-undefined string. This is a TypeScript type error: assigning `string | undefined` to a `string` field will fail a strict-mode compile.

The `cwd` field here should be updated to `string | undefined` (or `cwd?: string`) to propagate the fix consistently, mirroring what was done to `HostExecApprovalParams.workdir`.

```suggestion
  cwd: string | undefined;
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: src/agents/bash-tools.exec-host-node.ts
Line: 123

Comment:
**Redundant `?? undefined` tail**

`params.workdir` is already typed as `string | undefined`, so the trailing `?? undefined` is a no-op — `undefined ?? undefined` just yields `undefined`.

```suggestion
  const runCwd = prepared.plan.cwd ?? params.workdir;
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(exec): skip gateway cwd injection fo..." | Re-trigger Greptile}

Landed via temp rebase onto main.

• Gate: pnpm check; pnpm test -- src/agents/bash-tools.exec.approval-id.test.ts; pnpm test -- src/node-host/invoke-system-run.test.ts; pnpm test -- src/tasks/task-registry.test.ts
• PR CI: bypassed on maintainer request; follow-up validation on main
• Land commit: 2a1ecdab17
• Merge commit: fc76f667c23b63ffa19029a406d61016dd694343

Thanks @Starhappysh!