When Ox Alpha appears stuck, first separate service-side errors from local scanning or MCP blocking, then use .ignore, snapshot: false, and temporary MCP removal to narrow the cause.
Suitable tasks: OpenCode becoming unresponsive after opening a large repository, repeated requests, or mid-run hangs.
Unsuitable tasks: Treating local troubleshooting settings as a model improvement, or deleting tool configuration in a production repository.
Applicable model version: Ox Alpha; for the corresponding OpenCode setup.
Applicable clients, agents, or APIs: OpenCode; the source discusses Ox Alpha sessions in OpenCode.
Recommended reasoning levels and parameters: Not disclosed; change one environment or configuration item at a time while keeping model parameters fixed.
The original source publishes troubleshooting steps rather than a prompt. The following workflow can be applied directly:
1. Check ~/.local/share/opencode/log/opencode.log and determine whether the problem is authentication/network-related or local scanning.
2. Check whether the project contains multi-GB asset directories. Add those directories to .ignore at the project root.
3. Temporarily set "snapshot": false in opencode.json, restart, and compare the result.
4. If the problem persists, temporarily rename .mcp.json and run once more. If the issue clears, restore MCP services one by one to identify the blocker.
5. Change one item at a time and record startup time, first-request latency, and the exact error text; restore unrelated settings after diagnosis..ignore and snapshot target the comment author's scanning/snapshot issue; they are not an official OpenCode guarantee.
Endpoint is unavailable may be caused by server overload; local configuration cannot repair provider rate limits.
Perform renames and ignore changes on a reversible branch and a redacted repository.
Ox Alpha