Troubleshooting
This guide explains potential issues when using Kirox CLI and their solutions.
Installation and Execution
Node.js Version Error
Error Message:
Error: Kirox requires Node.js 18.0.0 or higherCause: Node.js version is outdated
Solution:
# Check Node.js version
node --version
# Upgrade to Node.js 18 or higher
# Download the latest version from https://nodejs.org/
# Using nvm
nvm install 18
nvm use 18npx Command Not Found
Error Message:
command not found: npxCause: npm is outdated or not installed
Solution:
# Check npm version
npm --version
# Upgrade npm
npm install -g npm@latestGitHub API Related
Rate Limit Error
Error Message:
Error: GitHub API rate limit exceededCause: Reached GitHub API rate limit (without authentication: 60 requests/hour)
Solution:
- Set GitHub Personal Access Token (PAT):
export GITHUB_TOKEN=ghp_your_token_hereAfter configuration, rate limit is relaxed to 5,000 requests/hour
Check current rate limit status:
npx kirox owner/repo -p project --verboseAuthentication Error
Error Message:
Error: Bad credentialsCause: Invalid GitHub Personal Access Token
Solution:
- Verify PAT is correct:
echo $GITHUB_TOKENVerify PAT scope (requires
public_repoorrepo)Generate a new PAT:
Repository Not Found
Error Message:
Error: Repository not found: owner/repoCause: Repository does not exist or no access permission
Solution:
- Verify repository name spelling
- For private repositories, set
GITHUB_TOKEN - Verify access permissions to the repository
File Fetching Related
File Not Found
Error Message:
Warning: .kiro/specs/project-name/ not found in repositoryCause: Specified project does not exist in the repository
Solution:
- Verify project name spelling
- Check branch (may exist in a different branch):
npx kirox owner/repo#develop -p project-name- Check subdirectory (for monorepos):
npx kirox owner/repo -p project-name --subdirectory path/to/subdir- Check available projects in the repository:
# Auto-detect in interactive mode
npx kiroxFile Size Limit Error
Error Message:
Error: File too large (max 1MB via GitHub API)Cause: GitHub's Content API cannot fetch files larger than 1MB
Solution:
- Check file size and split if necessary
- Do not include large binary files in the
.kiro/directory - When using Git LFS, fetching via API may be difficult
Local Filesystem Related
Write Permission Error
Error Message:
Error: EACCES: permission deniedCause: No write permission to the directory
Solution:
- Check directory permissions:
ls -la .kiro/- Correct permissions:
chmod -R u+w .kiro/- Running with sudo is not recommended (security risk)
Existing File Overwrite Confirmation
Behavior: Asked to confirm overwriting existing files
Solutions:
Select in confirmation prompt:
y: Overwriten: Skipa: Overwrite all
Skip confirmation (
--forceoption):
npx kirox owner/repo -p project --forceWarning
The --force option overwrites existing files without warning.
- Preview beforehand with dry run:
npx kirox owner/repo -p project --dry-runNetwork Related
Timeout Error
Error Message:
Error: Request timeoutCause: Network connection is slow or unstable
Solution:
- Check internet connection
- Check firewall or proxy settings
- Retry:
npx kirox owner/repo -p projectProxy Configuration
When accessing GitHub API through a proxy:
# HTTP proxy
export HTTP_PROXY=http://proxy.example.com:8080
export HTTPS_PROXY=http://proxy.example.com:8080
# Authenticated proxy
export HTTP_PROXY=http://user:pass@proxy.example.com:8080Other Issues
Unexpected Errors
Solutions:
- Enable verbose logging:
npx kirox owner/repo -p project --verbose- Check debug logs:
DEBUG=kirox:* npx kirox owner/repo -p projectUse the latest version (npx automatically uses the latest)
If the issue persists, report an issue on the GitHub repository
Displaying Help
To get hints for problem-solving:
# General help
npx kirox --help
# Subcommand help
npx kirox add --help
npx kirox completion --helpFurther Support
- GitHub Issues: Bug reports and feature requests
- GitHub Discussions: Questions and discussions
- CLI Reference: Details on commands and options
