What happened
PS C:\Users> freebuff login
Freebuff Login
Generating login URL...
Open this URL in your browser to log in:
https://freebuff.com/login?auth_code=.......
Please open the URL above manually to complete login.
Waiting for login...
✓ Logged in as xxxxxxx (xxxxxx@xxxxxx.com)
You can now run freebuff to start.
PS D:\xxxg> cd D:\xxxg;freebuff
This directory is not registered.
PS D:> freebuff --version
0.0.150
Steps to reproduce
Completed reinstallation and verification:
- Reinstalled
freebuff@0.0.150 from the official npm registry, and re‑downloaded the CLI core.
- CLI login succeeded.
- CLI‑specific configuration has been cleared and rebuilt; the old configuration is backed up at
C:\Users\xxx\freebuff-cli-backup-20260820-095902.
- The desktop‑app configuration at
C:\Users\xxx\AppData\Roaming\Freebuff was not modified.
However, D:\xxxg still returns This directory is not registered. Both the old project ID and the new ID generated after re‑login are rejected, and the SHA‑256 hashes of the old and new core binaries are exactly identical. This indicates that the issue lies in Freebuff's server‑side directory registration validation, not in the local installation/configuration. The public CLI also does not provide a "register directory" command.
Where does this happen?
CLI (terminal client)
Operating system
Windows
Version
0.0.150
Model
No response
Logs or screenshots
What happened
PS C:\Users> freebuff login
Freebuff Login
Generating login URL...
Open this URL in your browser to log in:
https://freebuff.com/login?auth_code=.......
Please open the URL above manually to complete login.
Waiting for login...
✓ Logged in as xxxxxxx (xxxxxx@xxxxxx.com)
You can now run freebuff to start.
PS D:\xxxg> cd D:\xxxg;freebuff
This directory is not registered.
PS D:> freebuff --version
0.0.150
Steps to reproduce
Completed reinstallation and verification:
freebuff@0.0.150from the official npm registry, and re‑downloaded the CLI core.C:\Users\xxx\freebuff-cli-backup-20260820-095902.C:\Users\xxx\AppData\Roaming\Freebuffwas not modified.However,
D:\xxxgstill returnsThis directory is not registered.Both the old project ID and the new ID generated after re‑login are rejected, and the SHA‑256 hashes of the old and new core binaries are exactly identical. This indicates that the issue lies in Freebuff's server‑side directory registration validation, not in the local installation/configuration. The public CLI also does not provide a "register directory" command.Where does this happen?
CLI (terminal client)
Operating system
Windows
Version
0.0.150
Model
No response
Logs or screenshots