-
Notifications
You must be signed in to change notification settings - Fork 6
Troubleshooting
This page covers common issues you might encounter while using LLMDog and provides solutions to resolve them.
Problem: Errors when building from source with go build
Solution:
-
Ensure you have Go 1.16 or higher installed:
go version
-
Check for missing dependencies:
go mod tidy
-
Try a clean build:
go clean go build -o llmdog ./cmd/llmdog
Problem: Error when installing via Homebrew
Solution:
-
Update Homebrew:
brew update
-
Check for conflicts:
brew doctor
-
Try with verbose output to see detailed errors:
brew install -v doganarif/LLMDog/LLMDog
Problem: Garbled text, missing UI elements, or display issues
Solution:
-
Ensure your terminal supports TUI applications and has proper UTF-8 support
-
Check terminal color support:
echo $TERM
It should be something like
xterm-256color -
Resize your terminal window to be at least 80x24 characters
-
If using Windows, try Windows Terminal instead of the traditional Command Prompt
Problem: llmdog command not found even after installation
Solution:
-
Verify the installation path is in your PATH environment variable:
# For Homebrew installation echo $PATH | grep -q "$(brew --prefix)/bin" && echo "In PATH" || echo "Not in PATH" # For manual installation to ~/bin echo $PATH | grep -q "$HOME/bin" && echo "In PATH" || echo "Not in PATH"
-
If installing from source, make sure you moved the binary to a directory in your PATH or added its location to your PATH
Problem: Content not copied to clipboard after pressing Enter
Solution:
-
Verify clipboard dependencies are installed:
-
On Linux, ensure you have
xcliporxselinstalled:# Debian/Ubuntu sudo apt install xclip # Fedora sudo dnf install xclip
-
On macOS, no additional dependencies are needed
-
On Windows, no additional dependencies are needed
-
-
Run the application with verbose output to see clipboard errors:
BUBBLES_DEBUG=1 llmdog
Problem: LLMDog launches but doesn't show any files
Solution:
- Check if the current directory is empty
- Verify file permissions:
ls -la
- If using a non-empty directory, check if all files are hidden (starting with
.) and toggle hidden files with the configuration option:# Edit config file nano ~/.config/llmdog/config.json # Set "showHiddenFiles": true
Problem: Gitignored files are not properly marked or Git information is missing
Solution:
-
Verify you're in a valid Git repository:
git status
-
Check if
.gitignorefile exists and is readable:cat .gitignore
-
Try running
git check-ignoreto test specific paths:git check-ignore -v path/to/file
Problem: Bookmarks not saving or loading correctly
Solution:
-
Check the bookmarks file for corruption:
cat ~/.config/llmdog/bookmarks.json -
If the file is corrupted, try backing it up and creating a new one:
mv ~/.config/llmdog/bookmarks.json ~/.config/llmdog/bookmarks.json.bak
-
Verify permissions on the config directory:
ls -la ~/.config/llmdog
Problem: Content search doesn't find text that you know exists in files
Solution:
- Verify content search mode is enabled (check status bar or toggle with
Ctrl+S) - Remember that content search has a file size limit (1MB by default) to maintain performance
- For binary files, content search may not work properly
- Try searching for a smaller, unique substring of the text you're looking for
Problem: LLMDog becomes very slow in repositories with many files
Solution:
- Navigate to a subdirectory with fewer files before launching LLMDog
- Use search functionality to filter to relevant files quickly
- Avoid expanding all directories at once
- Keep content search mode disabled until needed
Problem: LLMDog uses excessive memory
Solution:
- Avoid selecting too many large files at once
- Keep directory expansion minimal
- If you need to select many files, consider creating multiple smaller selections and processing them separately
Problem: Generated Markdown doesn't render correctly in the LLM chat
Solution:
- Verify the output with a Markdown previewer
- Check if the LLM chat interface has any Markdown rendering limitations
- For very large outputs, you might need to split them into multiple messages
Problem: LLM responds with a message about token limits being exceeded
Solution:
- Check the estimated token count in the status bar before confirming selection
- Select fewer files or smaller files
- Focus on only the most relevant code sections
- Consider using search to find and select only files containing specific keywords
Problem: Terminal rendering or clipboard issues in WSL
Solution:
- Ensure you're using Windows Terminal for better TUI support
- Install clipboard utilities in WSL:
sudo apt install xclip
- Use WSL2 instead of WSL1 for better performance and compatibility
Problem: Issues when running LLMDog over SSH
Solution:
- Ensure your terminal supports 256 colors:
export TERM=xterm-256color - For clipboard support, consider using X11 forwarding with your SSH connection:
ssh -X user@remote
If you encounter an issue not covered in this guide:
- Check the [GitHub Issues](https://github.com/doganarif/LLMDog/issues) to see if it's a known problem
- If not, create a new issue with:
- Detailed description of the problem
- Steps to reproduce
- Expected behavior
- Actual behavior
- System information (OS, terminal, Go version if applicable)
- Any error messages