Is your feature request related to a problem? Please describe.
Currently entering interactive mode requires using -i (--interactive) CLI option, or not passing query in CLI params.
In 95% case I want to enter interactive mode to be able to ask follow-up questions but sometimes forget to add -i. This is annoying, since exiting interactive mode is relatively effortless with a simple Ctrl+C.
Describe the solution you'd like
Make interactive mode default
Remove -i / --interactive CLI option
Add a new --batch CLI option. This should behave somewhat similar to --non-interactive mode with following changes:
a. in batch mode there is a single question to be asked to AI (in CLI params, not read during the session, there is no session)
b. users question is not repeated as is in interactive mode
c. the only thing outputted is the AI answer. No costs, no stats, not event "ai: " prefix.
Batch mode should be auto-detected by usingprocess.stdout.isTTY (enable batch if output is not a TTY=terminal)
Describe alternatives you've considered
Current solution.
Additional context
Updated the related documentation and examples.
Is your feature request related to a problem? Please describe. Currently entering interactive mode requires using
-i
(--interactive
) CLI option, or not passing query in CLI params.In 95% case I want to enter interactive mode to be able to ask follow-up questions but sometimes forget to add
-i
. This is annoying, since exiting interactive mode is relatively effortless with a simpleCtrl+C
.Describe the solution you'd like
-i
/--interactive
CLI option--batch
CLI option. This should behave somewhat similar to--non-interactive
mode with following changes: a. in batch mode there is a single question to be asked to AI (in CLI params, not read during the session, there is no session) b. users question is not repeated as is in interactive mode c. the only thing outputted is the AI answer. No costs, no stats, not event"ai: "
prefix.process.stdout.isTTY
(enable batch if output is not a TTY=terminal)Describe alternatives you've considered Current solution.
Additional context Updated the related documentation and examples.