docs(cli): clarify /clear resets active context

[SH20RAJ]

This PR adds clarification that the /clear command resets the active context in the CLI, ensuring users understand it results in a fresh conversation thread.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances user understanding of the /clear command within the CLI by explicitly documenting and updating its description to include the fact that it resets the active conversation context. This change ensures that users are aware that executing /clear will initiate a new conversation thread, preventing previous interactions from influencing subsequent responses.

Highlights

• Documentation Update: Clarified the description of the /clear command in the CLI documentation to explicitly state that it resets the active conversation context, ensuring users understand it leads to a fresh conversation thread.
• Command Description Update: Updated the internal description of the clear command in the CLI's source code to reflect that it clears the screen and resets the active conversation context.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the description of the /clear command in both the documentation and the CLI's command definition. The changes clarify that the command resets the active conversation context, allowing for fresh threads, in addition to clearing the screen. The documentation also notes that underlying session data for history recall might still be preserved. There is no feedback to provide on the review comments as none were submitted.

[SH20RAJ]

Hi maintainers, checking in on this small documentation update.

This clarifies that the /clear command resets the active context in the CLI, which is a frequent point of confusion for new users trying to manage multiple threads.

Please let me know if the phrasing works or if you'd like it adjusted!

[SH20RAJ]

Docs updated and rebased. Clarifies the behavior of the /clear command. Ready to merge. @skeshive @mrpmohiburrahman

[gemini-cli]

Hi there! Thank you for your interest in contributing to Gemini CLI.

To ensure we maintain high code quality and focus on our prioritized roadmap, we have updated our contribution policy (see Discussion #17383).

We only guarantee review and consideration of pull requests for issues that are explicitly labeled as 'help wanted'. All other community pull requests are subject to closure after 14 days if they do not align with our current focus areas. For this reason, we strongly recommend that contributors only submit pull requests against issues explicitly labeled as 'help-wanted'.

This pull request is being closed as it has been open for 14 days without a 'help wanted' designation. We encourage you to find and contribute to existing 'help wanted' issues in our backlog! Thank you for your understanding and for being part of our community!