Skip to content

fix(server): stop OpenCode V2 descendant sessions - #9904

Closed
saphid wants to merge 390 commits into
pingdotgg:t3code/codex-turn-mappingfrom
saphid:fix/v2-opencode-stop-release-20260905
Closed

saphid wants to merge 390 commits into
pingdotgg:t3code/codex-turn-mappingfrom
saphid:fix/v2-opencode-stop-release-20260905

fix(server): keep SDK response bodies out of OpenCode failure details

5278d0f
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Sep 9, 2026 in 2m 9s

Effect Service Conventions: All clear

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.


🔍 Agent activity — 2 tool calls

💭 Investigating error handling I need to inspect the relevant files, particularly focusing on the Data.TaggedError legacy and any changes to fields. The convention indicates that Schema.TaggedError relates to service failures, but it seems the class definition itself hasn’t been altered significantly except for the fields and construction. I'm also considering adding structured fields, potentially as an optional new category, but need to understand the constructions better and address if the new timeout has any cause. Plus, I should check the Semaphore import as well.

1. browse_code — apps/server/src/provider/opencodeRuntime.ts

2. browse_code — apps/server/src/orchestration-v2/Adapters/OpenCodeAdapterV2.ts


Agent Credits: 16 credits

Token usage: 6 uncached input · 20,813 cache-read input · 24,634 cache-write input · 592 output
Agent Credits may also include non-token charges from external tools such as web research.