🐞 Bug: CLI hangs on "Thinking..." then exits without execution
Description:
Whenever I run a command using forq-cli, the terminal displays Thinking..., waits for a few seconds, and then exits without performing any visible action or executing the intended command. There is no error, no output, and no logs that indicate what went wrong.
Steps to Reproduce:
Install forq-cli globally (or run locally).
Run any command like:
forq> "create a new react component"
Observe the terminal shows:
Thinking...
After a short delay, it simply exits — no output, no result.
Expected Behavior:
The CLI should either:
Execute the command and show the output, OR
Return an informative error/log if something fails internally.
Actual Behavior:
Just prints Thinking... and then silently dies.
No visible errors or debugging output.
Environment:
OS: Windows
Possible Causes / Notes:
It seems like it’s failing silently during the request to the backend/LLM API (maybe auth issue, invalid key, or timeout).
Lack of error handling/logging makes debugging impossible as an end-user.
If it requires an API key/config, it should prompt or error clearly.
Suggested Fix:
Add error logs when the CLI fails to process a command.
Gracefully handle API issues and display proper error messages.
Optionally add a --debug flag to see what's happening internally.
🐞 Bug: CLI hangs on "Thinking..." then exits without execution
Description:
Whenever I run a command using forq-cli, the terminal displays Thinking..., waits for a few seconds, and then exits without performing any visible action or executing the intended command. There is no error, no output, and no logs that indicate what went wrong.
Steps to Reproduce:
Install forq-cli globally (or run locally).
Run any command like:
forq> "create a new react component"
Observe the terminal shows:
Thinking...
After a short delay, it simply exits — no output, no result.
Expected Behavior:
The CLI should either:
Execute the command and show the output, OR
Return an informative error/log if something fails internally.
Actual Behavior:
Just prints Thinking... and then silently dies.
No visible errors or debugging output.
Environment:
OS: Windows
Possible Causes / Notes:
It seems like it’s failing silently during the request to the backend/LLM API (maybe auth issue, invalid key, or timeout).
Lack of error handling/logging makes debugging impossible as an end-user.
If it requires an API key/config, it should prompt or error clearly.
Suggested Fix:
Add error logs when the CLI fails to process a command.
Gracefully handle API issues and display proper error messages.
Optionally add a --debug flag to see what's happening internally.