Everything stays in context, making your workflow smoother and more powerful.

If you want to read more about it, check out this blog post: developers.googleblog.com/en/say-hello...

You need more than one knife in the kitchen! So awesome that the CLI is the one you grab every day!

It also provides a reliable point to restart from if any issues arise, especially when using an LLM, ensuring you can quickly get back on track.

Breaking down large tasks into smaller, manageable subtasks is a great way to stay organized. I recommend committing your changes after completing each subtask and frequently staging your changes. This approach keeps your work organized, separating finished code from what's still in progress.

Thanks for the feedback! If you haven't already, please file a bug or feedback report on the Gemini CLI repo. This is the best way to ensure the team gets this feedback.

That looping behavior is incredibly frustrating. You can set maxSessionTurns in your settings, which will stop after N turns. Additionally, we recently shipped an update with a specific loop check; it's designed to recognize when it's in a repetitive cycle and should automatically stop the process.

That loop is incredibly frustrating, you can set maxSessionTurns in your settings to help. This safety net automatically stops token-wasting requests after N turns. Also, clearing the context when starting a new task or subtask can improve response quality. Context rot has a big impact on quality.