Error on `gemini -r`

[Danipulok]

What happened?

I started the chat via gemini -r

What did you expect to happen?

The old conversation from this directory to be loaded.

Client information

• CLI Version: 0.22.2
• Git Commit: 9bc9a31
• Sesion ID: 8a9eb15b-c9da-4974-9241-a270758749f4
• Operating System: win32 v22.16.0
• Sandbox Environment: no sandbox
• Model Version3A auto-gemini-3
• Memory Usage: 230.4 MB

Login information

Google Account

Anything else we need to know?

trace.md

I did not manually edited any chat info, if it's important. Closed the previous conversation via double Ctrl-C

[samucodesh]

What happened?

I started the chat via gemini -r

What did you expect to happen?

The old conversation from this directory to be loaded.

Client information

• CLI Version: 0.22.2
• Git Commit: 9bc9a31
• Sesion ID: 8a9eb15b-c9da-4974-9241-a270758749f4
• Operating System: win32 v22.16.0
• Sandbox Environment: no sandbox
• Model Version3A auto-gemini-3
• Memory Usage: 230.4 MB

Login information

Google Account

Anything else we need to know?

trace.md

I did not manually edited any chat info, if it's important. Closed the previous conversation via double Ctrl-C

Hi @Danipulok, thank you for reporting this issue. We're sorry to hear that the -r flag didn't load your
previous conversation as expected.

To help us investigate and as a workaround, could you please try the following:

1. Check your session history: Run gemini --list-sessions. This will show you a list of all saved
   conversations and confirm if your last session was correctly recorded after the double Ctrl-C closure.
2. Use the full command with an index: Once you identify your session in the list, try resuming it using the
   full flag and its index number:
   gemini --resume <index> (for example: gemini --resume 1 to load the most recent one).

Please let us know if the session appears in the list and if you are able to load it using these commands.

[Danipulok]

1. gemini --list-sessions
2. gemini --resume 1 was a success

3. gemini -r now works too

PS

I'm sorry, I didn't add the full context in initial description.
When I was loading gemini -r and a bug occurred, I still got a chat somehow at the end of the console.
Here's how it looked:

I still have the chat opened.

[Danipulok]

@samucodesh

[samucodesh]

@samucodesh

It is highly probable that the previous session was not saved because it was considered "empty" (no messages exchange) or, in a rarer case, the file was corrupted during the forced exit.

For future reference, we also recommend using the /quit command (or /exit) to close the Gemini CLI instead of using double Ctrl+C.

Using /quit ensures that the session is properly saved and all cleanup tasks are completed gracefully. Forcing
an exit with double Ctrl+C can sometimes bypass these checks, potentially leading to the issue you experienced
where the session isn't recorded correctly.

[samucodesh]

1. gemini --list-sessions
2. gemini --resume 1 was a success

3. `gemini -r` now works too

PS

I'm sorry, I didn't add the full context in initial description. When I was loading gemini -r and a bug occurred, I still got a chat somehow at the end of the console. Here's how it looked:

I still have the chat opened.

You can also just start the Gemini CLI normally by running gemini and then type the /resume slash command.

[Danipulok]

Got it, thank you! Will close this then, I guess