You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Documented --non-interactive flag does not exist on bl text chat (v1.10.1) #120
The installation doc references a --non-interactive flag for bl text chat, but this flag does not exist in bl 1.10.1. Running the documented minimal verification command fails immediately with Unknown flag.
bl text chat --message "ping" --non-interactive --output json
Actual result
The command fails before making any request (exit code 2):
{
"error": {
"code": 2,
"message": "Unknown flag \"--non-interactive\". Run with --help to see available options."
}
}
bl text chat --help does not list a --non-interactive flag. Streaming is documented as "default: on in TTY", so non-TTY/CI usage works without this flag.
Workaround
Removing the flag works and returns a valid response:
bl text chat --message "ping" --output json
{
"content": "Pong!"
}
Expected resolution (either is fine)
Option A (preferred): Add --non-interactive support to bl text chat so the documented command works as written.
Option B: Update the doc to drop --non-interactive and use bl text chat --message "ping" --output json directly.
Additional note
Section "3. 鉴权" also references bl ... --non-interactive for CI/non-interactive environments. Worth verifying whether this flag is uniformly supported across subcommands, since the doc references it in multiple places but it does not currently exist on text chat.
Thanks for the feedback! We’ve updated the installation documentation to remove the unsupported --non-interactive option and clarified the recommended usage for automation. The corresponding static installation resource has also been updated.
The fix is available in PR #121. We’ll close this issue now and continue tracking the change through the PR.
Activity
XXPermanentXX commentedon Jul 24, 2026
Thanks for the feedback! We’ve updated the installation documentation to remove the unsupported
--non-interactiveoption and clarified the recommended usage for automation. The corresponding static installation resource has also been updated.The fix is available in PR #121. We’ll close this issue now and continue tracking the change through the PR.