Problem
Sometimes the Freebuff CLI closes unexpectedly while a 1-hour session is still active, for example because of a crash, terminal closing, or an update.
Proposed solution
It would be really useful to have a way to continue that session instead of wasting the remaining time.
Both of these should work:
freebuff -c
freebuff --continue
They should resume the most recently active session if it hasn't expired or been explicitly ended, including its existing conversation/state and remaining session time.
If there is no active session to resume, Freebuff should clearly tell the user that there is nothing to continue.
Benefit
This would prevent users from losing the rest of their session just because the CLI happened to close or restart.
Problem
Sometimes the Freebuff CLI closes unexpectedly while a 1-hour session is still active, for example because of a crash, terminal closing, or an update.
Proposed solution
It would be really useful to have a way to continue that session instead of wasting the remaining time.
Both of these should work:
They should resume the most recently active session if it hasn't expired or been explicitly ended, including its existing conversation/state and remaining session time.
Benefit
This would prevent users from losing the rest of their session just because the CLI happened to close or restart.