fix(ssh): report remote package installation failures accurately - #10088
Effect Service Conventions: No issues found
All clear
Details
Note
Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.
In-scope changed files: packages/ssh/src/tunnel.ts (packages/ssh/src/runnerProcess.test.ts is excluded by the **/*.test.ts pattern).
The only in-scope change is inside the embedded REMOTE_RUNNER_SCRIPT shell template (require_installed_t3_cli), adding an explicit install-failure branch and diagnostic message. It touches no Effect imports, service definitions, layers, dependency acquisition, runtime boundaries, or error classes, so none of the Effect service conventions apply to the changed lines.
🔍 Agent activity — 1 tool call
💭 Only two files show up in the diff, and one's a test file I'm excluding. The other, tunnel.ts, just modifies shell script text rather than Effect service code, so this probably won't yield findings—but I want to check the context around that change to be certain.
1. browse_code — In packages/ssh/src/tunnel.ts, show the buildRemoteT3RunnerScript function and the require_installed_t3_cli shell snippet around line 400-470, including how @@T3_PACKAGE_SPEC@@ placeholder is substituted.
💭 This looks like shell script embedded in a TS file alongside a test file, and it follows Effect service conventions fine — with
set -eu, theif !pattern is safe. No issues to flag here.
Agent Credits: 44 credits
Token usage: 18 uncached input · 93,920 cache-read input · 40,951 cache-write input · 4,512 output
Agent Credits may also include non-token charges from external tools such as web research.