Troubleshooting
Common issues and solutions for nokey.ai
Common Issues
Find solutions to the most common problems users encounter with nokey.ai.
Installation fails with "command not found"
After installation, running nokey shows "command not found".
Solution:
The installation directory is not in your PATH. Add it manually:
For macOS/Linux (bash/zsh):
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc source ~/.bashrc For Windows (PowerShell):
$env:Path += ";$env:LOCALAPPDATA\nokey\bin" AI assistant still accessing protected files
Your AI coding assistant seems to bypass nokey protection.
Solution:
- Verify nokey is running:
nokey status - Check if the file pattern is protected:
nokey config show - Ensure your AI assistant is configured to work with nokey
- Restart your AI assistant after installing nokey
Some AI assistants may need additional configuration. Check your AI assistant's documentation for proxy or security tool integration.
Permission denied errors
Getting "permission denied" when running nokey commands.
Solution:
The nokey binary may not have execute permissions. Fix with:
chmod +x ~/.local/bin/nokey Audit logs not appearing
Running nokey logs shows no entries.
Solution:
- Check if audit logging is enabled:
nokey config show - Verify log file location has write permissions
- Ensure AI has actually attempted to access files
- Check for errors:
nokey status --verbose
High CPU or memory usage
nokey is consuming excessive system resources.
Solution:
- Check audit log size: large logs can slow down operations
- Reduce retention period in config:
retention_days - Add more patterns to
ignored_patternsto reduce monitoring overhead
nokey config set audit_log.retention_days 30 Configuration changes not taking effect
Updated configuration but nokey still uses old settings.
Solution:
- Validate your config file:
nokey config validate - Check for YAML syntax errors
- Ensure you're editing the correct config file (project vs global)
- Restart nokey after configuration changes
Frequently Asked Questions
Does nokey work with all AI coding assistants?
nokey is designed to work with most AI coding assistants including Claude Code, Cursor, GitHub Copilot, and others. However, some assistants may require additional configuration. Check the Configuration Guide for specific setups.
Will nokey slow down my AI assistant?
nokey is designed to have minimal performance impact. File access checks are extremely fast, typically adding less than 1ms per request. You shouldn't notice any slowdown in normal usage.
Can I use nokey in a team/enterprise setting?
Yes! nokey is perfect for teams. Commit your .nokey.yaml configuration
to version control so all team members use the same protection policies.
For enterprise deployments, you can also set up centralized audit log collection and monitoring.
What happens if I temporarily need to allow AI access?
Use the nokey allow command to temporarily grant access:
nokey allow .env.development --duration 1h Is nokey open source?
Yes! nokey is fully open source under the MIT license. You can audit the code, contribute improvements, or fork it for your own needs on GitHub.
Can I disable nokey temporarily?
Yes, set the environment variable:
export NOKEY_DISABLE=true
Or unset it to re-enable: unset NOKEY_DISABLE
How do I update nokey?
Run the installation command again - it will download and install the latest version:
curl -fsSL https://nokey.ai/install.sh | bash How do I uninstall nokey?
Remove the binary and configuration:
rm ~/.local/bin/nokey rm -rf ~/.config/nokey
On Windows: Remove-Item -Recurse $env:LOCALAPPDATA\nokey
Debug Mode
For troubleshooting complex issues, enable debug mode:
export NOKEY_LOG_LEVEL=debug nokey status --verbose This provides detailed output about what nokey is doing, which is helpful when reporting issues.
Still Having Issues?
If you can't find a solution here, we're here to help:
When reporting issues, include your OS, nokey version, and any error messages from debug mode.