[Bug]: Windows - comment-checker binary error

[BrianMSK]

Prerequisites

• I have searched existing issues to avoid duplicates
• I am using the latest version of oh-my-opencode
• I have read the documentation

Bug Description

Steps to Reproduce

1. Install oh-my-opencode on windows
2. Start opencode

Expected Behavior

Start without errors

Actual Behavior

Starts with errors provided above

Doctor Output

Bugs out on windows as it thinks its still in TUI mode

Error Logs

Configuration

Additional Context

No response

Operating System

Windows

OpenCode Version

1.1.34

[BrianMSK]

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned doesnt fix this

[BrianMSK]

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass fixed installation of the library for the error above ^

[FurryWolfX]

oh-my-opencode.jsonc

"disabled_hooks": ["comment-checker"]

it maybe helpful

[justsisyphus]

Analysis & Findings

Issue Summary

Windows users encounter comment-checker binary errors on startup (OpenCode v1.1.34).

Root Cause Investigation

Current Status:

• oh-my-opencode: v3.1.1 (latest)
• @code-yeongyu/comment-checker dependency: ^0.6.1
• Latest available: v0.7.0 (released 2025-12-28)

Binary Resolution Chain (src/hooks/comment-checker/cli.ts):

1. Checks cached binary first
2. Falls back to package resolution via require.resolve()
3. Triggers lazy download if not found

Potential Windows Issues Identified:

• import.meta.url may be undefined during plugin loading (guarded at line 34, but silently fails)
• require.resolve() may fail if @code-yeongyu/comment-checker not installed
• Network/extraction failures during lazy download
• PowerShell execution policy restrictions (as noted in comments)

Workarounds (from issue comments)

1. Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass - Works for some users
2. Disable hook: Add "disabled_hooks": ["comment-checker"] to config

Recommended Actions

1. Upgrade comment-checker to v0.7.0 - Latest version may include Windows fixes
2. Improve error visibility - Add explicit Windows error logging
3. Add fallback mechanisms - Better handling when binary unavailable

Next Steps

• Upgrade @code-yeongyu/comment-checker to v0.7.0
• Add Windows-specific error diagnostics
• Test on Windows environment
• Consider auto-disabling on Windows if binary unavailable

[code-yeongyu]

Closing as fixed - commit 1dd369f ("perf(comment-checker): lazy init for CLI path resolution") addresses the Windows binary detection issues. The current implementation uses lazy initialization, cached paths, and proper Windows .exe detection.