-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Description
I've installed the Qoder CLI on my macOS system using the official installation method (e.g., npm install -g @qoder-ai/qodercli), which correctly places the executable as qodercli in /usr/local/bin.
However, when running speckit.specify, the tool performs a check for the presence of a binary named qoder (not qodercli). This causes the check to fail with a "qwen not found" (or likely "qoder not found") error, even though Qoder is properly installed.
As a temporary workaround, I created a symbolic link:
sudo ln -s /usr/local/bin/qodercli /usr/local/bin/qoder
After this, speckit.specify works as expected.
Suggested fix:
The Spec Kit should either:
Check for qodercli instead of qoder, or Support both qoder and qodercli as valid executable names during the tool detection step.
This would avoid requiring users to manually create symlinks or modify their system just to satisfy the checker.
Thanks for building Spec Kit — it’s a great tool! Let me know if you need more details.