Skip to content

fix(web): wait for a racing client's chat project before failing

MacroscopeApp / Macroscope - Effect Service Conventions completed Sep 17, 2026 in 3m 31s

Effect Service Conventions: 1 issue found

  • apps/server/src/ws.ts: Repository detection catches defects instead of only the typed failure channel.

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.

Reviewed 2 of 4 changed files β€” those modified since a8eff87 β€” each against the merge base


πŸ” Agent activity β€” 5 tool calls

1. browse_code β€” Review only Effect service convention implications of the PR changes in apps/server/src/ws.ts around resolveChatWorkspaceRoot. Determine the exact type/error behavior of gitWorkflow.isRepository, whether catching the full Cause (including defects) is established/appropriate, Effect.cached interruption semantics, and whether tests added in apps/server/src/server.test.ts cover outside repo, inside repo, and detection failure. Also identify any new Effect-service convention violation in apps/web/src/hooks/useChatProject.ts (likely none). Return concise evidence with paths.

2. modify_pr β€” Submitted review with 1 inline comment

3. modify_pr β€” Effect Service Conventions found one blocking issue: resolveChatWorkspaceRoot still catches defects instead of only the typed repository-detection failure. See the inline review comment on apps/server/src/ws.ts.

4. modify_pr β€” Resolved review thread

5. modify_pr β€” Effect Service Conventions found one blocking issue. β€” not performed: the agent's request was refused before it ran


Agent Credits: 70 credits

Token usage: 36 uncached input Β· 371,304 cache-read input Β· 92,654 cache-write input Β· 2,688 output
Agent Credits may also include non-token charges from external tools such as web research.