Investigation Complete

After comprehensive analysis of the oh-my-opencode codebase, here are my findings:

Symptoms Analysis

The reported behavior:

Can still type
Animation still works
Cannot send messages
No actual progress
Commands don't work

This pattern strongly suggests the issue is at the OpenCode core level, not oh-my-opencode. Here's why:

If you can type but can't send, the input handling layer (OpenCode core) is the bottleneck
oh-my-opencode hooks run AFTER OpenCode processes input, so they can't prevent message sending
Animation working means the UI event loop is fine - the issue is in the message processing pipeline

@code-yeongyu's Assessment is Likely Correct

This appears to be an OpenCode issue. However, I did find some potential blocking operations in oh-my-opencode that could contribute in edge cases:

oh-my-opencode Potential Issues Found

1. CRITICAL: `executeHookCommand` - No Timeout Protection

File: src/shared/command-executor.ts (lines 65-101)

If a user has Claude Code hooks configured (via settings.json) with commands that hang, the entire tool execution pipeline blocks indefinitely. No timeout is implemented.

return new Promise((resolve) => {
  const proc = spawn(finalCommand, { ... })
  // NO TIMEOUT - can hang forever
  proc.on("close", (code) => { resolve(...) })
})

Impact: Only affects users with custom PreToolUse/PostToolUse hooks configured.

2. HIGH: LSP Client Hardcoded Delays

File: src/tools/lsp/client.ts

Line 223: 100ms delay after spawn
Line 467: 300ms delay after initialize
Line 488: 1000ms delay in openFile
Line 535: 500ms delay before diagnostics
Line 368: 15-second request timeout

These accumulate to 2+ seconds per LSP operation chain.

3. HIGH: Blocking Wait in `background_output`

File: src/tools/background-task/tools.ts (lines 268-286)

When block=true, polls for up to 600 seconds with 1-second intervals, blocking the main session.

4. MEDIUM: Network Fetch Without Timeout

Files: src/tools/grep/downloader.ts, src/tools/ast-grep/downloader.ts

First-run binary downloads have no timeout - can hang on network issues.

5. MEDIUM: setInterval Without Cleanup

Files: src/hooks/comment-checker/index.ts, src/hooks/claude-code-hooks/tool-input-cache.ts

Global intervals that run forever without cleanup - potential memory leak over long sessions.

Recommendations

For @CloudWaddie:

Can you reproduce this consistently? If so, what triggers it?
Does it happen with a fresh session or after extended use?
Try running with --plugin "" (no plugins) to confirm it's OpenCode vs oh-my-opencode:
```
opencode --plugin ""
```
If it still freezes without plugins → confirmed OpenCode issue
Check if you have any custom hooks in ~/.claude/settings.json or .claude/settings.json

For oh-my-opencode improvements (tracked separately):

Add 5-second timeout to executeHookCommand
Add timeout to network fetch calls in downloaders
Replace hardcoded delays with event-driven waits
Add cleanup for global setInterval calls

Conclusion

Primary Cause: Most likely OpenCode core (based on symptom analysis)

Secondary Contributors (edge cases only):

Custom Claude Code hooks with hanging commands
First-time binary download on slow network
Extended LSP operations

If you can reproduce reliably, please file an issue on sst/opencode with reproduction steps. The oh-my-opencode issues I found are minor and unlikely to cause the described "freeze" symptom.

Random effective freezing #445

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions