I installed it but the command still fails
Start with command-not-found or Homebrew command-not-found if the binary is missing from your shell path.
Go to command fixTroubleshooting
Most CodeWhale issues still trace back to install, auth, or workflow-baseline mistakes first
This hub keeps the old DeepSeek TUI search intent in view, but the fixes now need to be explained under the current CodeWhale product name and command path.
Choose the troubleshooting path by question type
Use this hub as the troubleshooting list first. Decide whether the failure is install, provider, binary, or MCP related before opening the detail fix.
I can launch it but the provider flow is broken
Start with provider troubleshooting if the install works but auth, endpoint, or provider behavior still fails.
Go to provider troubleshootingI think MCP or binaries are the issue
Start with release binaries or MCP troubleshooting if the basic command path already looks correct.
Go to MCP troubleshootingTroubleshooting article list
Open the exact fix page you need instead of mixing shell-path problems with provider or MCP debugging.
CodeWhale command not found
Start here if the install finished but your shell still cannot see the current command.
Open fix pageHomebrew command not found
Use this page when brew says install succeeded but your shell still cannot find the command.
Open Homebrew fixProvider troubleshooting
Use this page when your install succeeds but auth, endpoint, or provider behavior still does not line up.
Open provider troubleshootingRelease binaries
If package-manager friction is the issue, the release-binary route may be the cleaner path.
Open release binaries guideMCP troubleshooting
Use this page when MCP feels broken and you need to separate server-level failures from basic config mistakes.
Open MCP troubleshooting