Bug Description
When running the kilo CLI (v7.1.19), the following error appears:
log stream error: ENOENT: no such file or directory, open '/Users/hemanth/.local/share/kilo/log/Users/hemanth/.local/share/kilo/log/.log-history'
Root Cause
The log file path is being constructed incorrectly — the log directory path is being prepended twice, resulting in:
/Users/hemanth/.local/share/kilo/log/Users/hemanth/.local/share/kilo/log/.log-history
Instead of the correct path:
/Users/hemanth/.local/share/kilo/log/.log-history
This suggests a string concatenation bug where the full log directory path is used as both the base directory and the filename prefix.
Environment
- OS: macOS (darwin, arm64)
- Kilo version: 7.1.19
- Installation: Homebrew (
Kilo-Org/homebrew-tap/kilo)
- Log directory:
~/.local/share/kilo/log/
Workaround
Manually creating the duplicated directory structure suppresses the error:
mkdir -p ~/.local/share/kilo/log/Users/hemanth/.local/share/kilo/log
touch ~/.local/share/kilo/log/Users/hemanth/.local/share/kilo/log/.log-history
Expected Behavior
The .log-history file should be created/read at ~/.local/share/kilo/log/.log-history without path duplication.
Bug Description
When running the
kiloCLI (v7.1.19), the following error appears:Root Cause
The log file path is being constructed incorrectly — the log directory path is being prepended twice, resulting in:
Instead of the correct path:
This suggests a string concatenation bug where the full log directory path is used as both the base directory and the filename prefix.
Environment
Kilo-Org/homebrew-tap/kilo)~/.local/share/kilo/log/Workaround
Manually creating the duplicated directory structure suppresses the error:
Expected Behavior
The
.log-historyfile should be created/read at~/.local/share/kilo/log/.log-historywithout path duplication.