feat: add /new as alias for /clear and refine command description by ved015 · Pull Request #17865 · google-gemini/gemini-cli

ved015 · 2026-01-29T15:29:49Z

Summary

This PR adds /new as a command alias for the existing /clear command and updates the /clear description to clarify that it creates a new chat session.

Details

Added /new as an alias to the /clear command to provide a more intuitive way for users to start a fresh session.
Tweaked the description for the /clear command to explicitly state it "starts a new session" rather than just "clearing" the state.
Simplified the implementation by utilizing the existing /clear logic instead of introducing a separate command path.

Related Issues

Closes #16835

How to Validate

Pre-Merge Checklist

@jackwotherspoon please have a look

gemini-code-assist · 2026-01-29T15:30:11Z

Summary of Changes

Hello @ved015, 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 introduces a new /new command for the CLI, enabling users to start a fresh chat session while preserving the terminal's current content. Crucially, it also addresses and resolves a significant bug that could lead to the overwriting of existing chat session history files during session creation. The underlying session management logic has been refactored into a shared utility to improve maintainability and prevent future regressions.

Highlights

New '/new' Command Implementation: A new slash command /new has been added, allowing users to initiate a fresh chat session without clearing the terminal screen, providing a cleaner user experience for starting new conversations.
Critical Session Overwrite Bug Fix: Resolved a race condition where newly created sessions could overwrite existing session history files. This was due to the chat being reset before the new session ID was properly configured, leading to data loss. The fix ensures the new session ID is set before chat reset.
Session Creation Logic Refactoring: The logic for creating new sessions has been extracted into a standalone utility function, createNewSession, in sessionUtils.ts. This promotes code reuse and simplifies the implementation of both /clear and /new commands.
Comprehensive Unit Testing: New unit tests have been added for the /new command (newCommand.test.ts) to ensure its correct functionality, particularly regarding session ID assignment and service initialization.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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 introduces a new /new command and refactors the session creation logic into a shared createNewSession utility. This is a great improvement that not only adds a useful feature but also fixes a critical race condition that could lead to session data loss. The code is well-structured and the changes are clear. I've added a couple of high-severity comments regarding the test setup to prevent mock leaking, which could cause issues in the test suite.

ved015 · 2026-01-29T15:38:10Z

/gemini review

gemini-code-assist

Code Review

This pull request introduces a new /new command to start a fresh chat session and, more importantly, fixes a critical bug related to session overwrites. The refactoring of session creation logic into a reusable createNewSession function is a good approach that improves code clarity and maintainability. The fix for the session overwrite bug, which ensures the new session ID is set before the chat is reset, is correctly implemented. My review includes one high-severity suggestion to enhance the new unit test to explicitly verify the order of operations, ensuring this critical bug fix does not regress in the future.

gemini-code-assist · 2026-01-29T15:39:50Z

+      SessionEndReason.Clear,
+    );
+    expect(mockGeminiClient.resetChat).toHaveBeenCalled();
+    expect(mockConfig.setSessionId).toHaveBeenCalledWith('new-session-id');


To ensure the critical session overwrite bug doesn't regress, it's important to verify the order of operations. Please add an assertion here to confirm that setSessionId is called before resetChat.

expect(mockConfig.setSessionId).toHaveBeenCalledWith('new-session-id'); // Verify the order of operations to prevent session overwrite bugs. const setSessionIdOrder = (mockConfig.setSessionId as Mock).mock.invocationCallOrder[0]; const resetChatOrder = (mockGeminiClient.resetChat as Mock).mock.invocationCallOrder[0]; expect(setSessionIdOrder).toBeLessThan(resetChatOrder);

@jackwotherspoon i was thinking of adding these lines in sessionUtils.test.ts instead of here if you agree i can proceed with that

jackwotherspoon · 2026-01-29T16:29:50Z

There is already a PR open for this... #16848

I lean towards closing this in favor of the other one as it was opened first.

ved015 · 2026-01-29T16:38:39Z

There is already a PR open for this... #16848

I lean towards closing this in favor of the other one as it was opened first.

hi @jackwotherspoon Last time i checked that PR was closed with unmerged commits so i raised it no issue if you want to favour that but can you please review that bug which i am reffering to if that sound logical i will close this PR and raise a pr just for those changes

The bug was a race condition in the session initialization sequence within sessionUtils.ts in PR #16848

geminiClient.resetChat() was being called before the new session ID was generated and set in the configuration.
resetChat() initializes a new ChatRecordingService, which reads the current sessionId from the Config at startup. Since the ID hadn't been updated yet, the new service inherited the previous session's ID.
The new chat session saved to the same history file as the previous one, leading to data overwrites and the appearance of "disappearing" sessions in the /resume list.
Reordered the logic to update the Config with a new randomUUID() before triggering the chat reset. This ensures the newly instantiated recording service always starts with a unique identifier.

ved015 · 2026-02-01T13:29:28Z

There is already a PR open for this... #16848
I lean towards closing this in favor of the other one as it was opened first.

hi @jackwotherspoon Last time i checked that PR was closed with unmerged commits so i raised it no issue if you want to favour that but can you please review that bug which i am reffering to if that sound logical i will close this PR and raise a pr just for those changes

The bug was a race condition in the session initialization sequence within sessionUtils.ts in PR #16848

geminiClient.resetChat() was being called before the new session ID was generated and set in the configuration.

resetChat() initializes a new ChatRecordingService, which reads the current sessionId from the Config at startup. Since the ID hadn't been updated yet, the new service inherited the previous session's ID.

The new chat session saved to the same history file as the previous one, leading to data overwrites and the appearance of "disappearing" sessions in the /resume list.

Reordered the logic to update the Config with a new randomUUID() before triggering the chat reset. This ensures the newly instantiated recording service always starts with a unique identifier.

hi @jackwotherspoon any views on this

jackwotherspoon · 2026-02-01T16:12:02Z

want to favour that but can you please review that bug which i am reffering to if that sound logical i will close this PR and raise a pr just for those changes

@ved015 what bug are you referring to?

Going to close this PR, if there is a race condition in session resuming please check if there is an existing issue or raise a new one in which you can create a PR for 👍

ved015 · 2026-02-01T16:20:26Z

want to favour that but can you please review that bug which i am reffering to if that sound logical i will close this PR and raise a pr just for those changes

@ved015 what bug are you referring to?

Going to close this PR, if there is a race condition in session resuming please check if there is an existing issue or raise a new one in which you can create a PR for 👍

@jackwotherspoon I was referring a bug in the other PR which you mentioned above #16848 i think that PR will introduce a bug whose full details i have written in the above msg

jackwotherspoon · 2026-02-01T16:35:32Z

@ved015 Feel free to comment on the other PR then 🙏

Let's all help one another in the the open-source community. 😄

ved015 · 2026-02-01T18:17:03Z

@ved015 Feel free to comment on the other PR then 🙏

Let's all help one another in the the open-source community. 😄

sure no issue will comment on that

ved015 · 2026-02-06T19:00:10Z

Hi @jackwotherspoon, just a quick headsup I have left a couple of comments on the other PR #16848 highlighting some issues i noticed while working on the same change. I haven’t seen any updates there yet regarding the bug, and it looks like a recent merge on that branch accidentally reverted some changes, so it is currently broken/regressed so just wanted to check if there is anything I can do to help move it forward and avoid blocking the feature.

ved015 · 2026-02-21T18:18:45Z

Hi @jackwotherspoon, just a quick headsup I have left a couple of comments on the other PR #16848 highlighting some issues i noticed while working on the same change. I haven’t seen any updates there yet regarding the bug, and it looks like a recent merge on that branch accidentally reverted some changes, so it is currently broken/regressed so just wanted to check if there is anything I can do to help move it forward and avoid blocking the feature.

hi @jackwotherspoon awaiting your review on this

jackwotherspoon · 2026-02-26T13:25:16Z

Sounds good, I can re-open this if the user does not respond shortly. Will try one more ping.

Thanks @ved015 👏

ved015 · 2026-03-02T19:51:31Z

Sounds good, I can re-open this if the user does not respond shortly. Will try one more ping.

Thanks @ved015 👏

hi @jackwotherspoon no response on the other PR i think we should close this issue as multiple PR are opening for the same issue

ved015 · 2026-03-10T12:08:42Z

hi @jackwotherspoon awaiting for your review on this😁

jackwotherspoon · 2026-03-10T12:38:57Z

@ved015 you have my go ahead 👍

Looks like some conflicts to resolve.

jackwotherspoon · 2026-03-10T12:46:21Z

Looks like CC and Opencode just use /new as an alias for /clear.

Should we just do the same here and make this an easier change? 😄

ved015 · 2026-03-10T15:32:26Z

Looks like CC and Opencode just use /new as an alias for /clear.

Should we just do the same here and make this an easier change? 😄

@jackwotherspoon I tested cc /new, and it actually behaves a bit differently.

cc /new creates a new session with a fresh context, while also clearing the screen. Because the screen is cleared, users lose the ability to visually reference the previous conversation, even though the previous session is still saved under the hood.

This is slightly confusing because the UI message says “clear conversation history”, but in reality it also creates a new session and stores the previous one. So their /new (which looks like a clear command) behaves differently from how /clear works in Gemini CLI.

I think adding /new here would still be useful because it gives users clearer intent:

/new → start a new session with fresh context
/clear → clear history but stay in the same session

That separation makes the workflow easier to understand and avoids ambiguity about whether the session itself changed.

Whats your take on this

ved015 · 2026-03-10T18:01:57Z

@jackwotherspoon Conflicts resolved checked npm run preflight locally

jackwotherspoon · 2026-03-11T08:06:01Z

Looks like CC and Opencode just use /new as an alias for /clear.
Should we just do the same here and make this an easier change? 😄

I think adding /new here would still be useful because it gives users clearer intent:

/new → start a new session with fresh context

/clear → clear history but stay in the same session

Let me chat with the team. I feel like maybe this is a bug in our /clear and not sure if clearing the session should wipe the session data. Atleast for me i would like to be able to resume a session that i have cleared later...

ved015 · 2026-03-11T08:22:41Z

Looks like CC and Opencode just use /new as an alias for /clear.
Should we just do the same here and make this an easier change? 😄

I think adding /new here would still be useful because it gives users clearer intent:

/new → start a new session with fresh context

/clear → clear history but stay in the same session

Let me chat with the team. I feel like maybe this is a bug in our /clear and not sure if clearing the session should wipe the session data. Atleast for me i would like to be able to resume a session that i have cleared later...

I think there is a confusion you can resume that session later on which you entered /clear it only clears the history but /new will help users create a new session while saving the previous one just like claude code they create a new session save the preivous one

The feature which is implemented in this PR will do the same create a new session save the previous one and will not clear the screen

jackwotherspoon · 2026-03-11T08:41:18Z

I think there is a confusion you can resume that session later on which you entered /clear it only clears the history but /new will help users create a new session while saving the previous one just like claude code they create a new session save the preivous one

The feature which is implemented in this PR will do the same create a new session save the previous one and will not clear the screen

@ved015 Sorry let me explain more. To me our current /clear is not as I would expect from a UX point of view. But I need to chat with folks to see if it is purposeful.

Let's say I have a session on building feature A. I do /clear in the session and begin working on feature B.

I can now never recover the session for feature A. In /resume it will only have feature B as it has overwritten the existing session. From a UX point of view, what is the use-case for this? I can't think of one. I personally would always like to be able to go back and resume previous work.

It seems to me like the ideal UX would be for /clear to end a session and a start a new one, that way I can still resume it later if I need.

If this is agreed as the ideal UX then it probably makes sense to fix /clear and then maybe add an alias for /new.

I can see a bit of value in keeping the UI history and creating a new session for /new but I could also see it leading to confusion for users potentially.

Let me know if this chain of thought makes sense. We should let ideal UX dictate our decision making here. Would love your input on the user experience you would expect 😄

ved015 · 2026-03-11T08:55:18Z

I think there is a confusion you can resume that session later on which you entered /clear it only clears the history but /new will help users create a new session while saving the previous one just like claude code they create a new session save the preivous one
The feature which is implemented in this PR will do the same create a new session save the previous one and will not clear the screen

@ved015 Sorry let me explain more. To me our current /clear is not as I would expect from a UX point of view. But I need to chat with folks to see if it is purposeful.

Let's say I have a session on building feature A. I do /clear in the session and begin working on feature B.

I can now never recover the session for feature A. In /resume it will only have feature B as it has overwritten the existing session. From a UX point of view, what is the use-case for this? I can't think of one. I personally would always like to be able to go back and resume previous work.

It seems to me like the ideal UX would be for /clear to end a session and a start a new one, that way I can still resume it later if I need.

If this is agreed as the ideal UX then it probably makes sense to fix /clear and then maybe add an alias for /new.

I can see a bit of value in keeping the UI history and creating a new session for /new but I could also see it leading to confusion for users potentially.

Let me know if this chain of thought makes sense. We should let ideal UX dictate our decision making here. Would love your input on the user experience you would expect 😄

From my point of view i belive the best flow would be lets say you are woking on a feature A in one session and you want to do new feature so you do /new it should clear the screen save your current session (Feature A one) and start a fresh session where you can start with feature B

Now okay clear does that but i think its explanation and intent seems to be unclear from its name so one workaround is just rename it and improve its explanation maybe

sry i got confused earlier with its scope indeed an alias could be added but yeah one thing that part where the previous session is visible ie screen is not cleared that is debatble would love your view on that😁

ved015 · 2026-03-11T10:36:13Z

Working on a fix for the above bug, then your PR should just be able to create an alias for /new 👍

sure will wait till your PR gets merged and then do the alias part

jackwotherspoon · 2026-03-11T14:23:36Z

sure will wait till your PR gets merged and then do the alias part

Perfect, should get it in today hopefully: #22007

ved015 · 2026-03-12T14:39:57Z

Hi @jackwotherspoon since your PR is merged can you please tell what all changes needs to be done just to clarify what i will be doing in my PR aligns with whats in your mind thanks

ved015 · 2026-03-16T13:32:39Z

Hi @jackwotherspoon since your PR is merged can you please tell what all changes needs to be done just to clarify what i will be doing in my PR aligns with whats in your mind thanks

@jackwotherspoon awaiting your review

jackwotherspoon · 2026-03-16T13:48:55Z

@ved015 i think we just want to add /new as an alias now to existing /clear.

Probably also want to tweak the description of /clear to be a bit more clear that it creates a new session.

ved015 · 2026-03-16T13:50:47Z

ok sure will do that and update you

ved015 · 2026-03-16T18:35:53Z

@jackwotherspoon i think this new desc and altname will suffice and user will now have the same behaviour which they have while using cc now

Screen.Recording.2026-03-16.at.8.01.27.PM.mov

ved015 · 2026-03-19T19:02:05Z

@jackwotherspoon i think this new desc and altname will suffice and user will now have the same behaviour which they have while using cc now

Screen.Recording.2026-03-16.at.8.01.27.PM.mov

@jackwotherspoon awaiting your review

ved015 · 2026-04-10T03:26:28Z

hi @jackwotherspoon awaiting your review on this

jackwotherspoon

LGTM, want to just quickly update the PR description accordingly @ved015 👏

ved015 · 2026-04-16T13:24:14Z

LGTM, want to just quickly update the PR description accordingly @ved015 👏

@jackwotherspoon done updated the PR desc and title

ved015 · 2026-04-21T18:37:31Z

@scidomino e2e failed does something needs to be done from my end

* refactor(plan): simplify policy priorities and consolidate read-only rules (google-gemini#24849) * feat(test-utils): add memory usage integration test harness (google-gemini#24876) * feat(memory): add /memory inbox command for reviewing extracted skills (google-gemini#24544) * chore(release): bump version to 0.39.0-nightly.20260408.e77b22e63 (google-gemini#24939) * fix(core): ensure robust sandbox cleanup in all process execution paths (google-gemini#24763) Co-authored-by: Spencer <spencertang@google.com> * chore: update ink version to 6.6.8 (google-gemini#24934) * Changelog for v0.38.0-preview.0 (google-gemini#24938) Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> Co-authored-by: g-samroberts <samroberts@google.com> * chore: ignore conductor directory (google-gemini#22128) Co-authored-by: Coco Sheng <cocosheng@google.com> * Changelog for v0.37.0 (google-gemini#24940) Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> Co-authored-by: Sam Roberts <158088236+g-samroberts@users.noreply.github.com> * feat(plan): require user confirmation for activate_skill in Plan Mode (google-gemini#24946) * feat(test-utils): add CPU performance integration test harness (google-gemini#24951) * fix(core): resolve windows symlink bypass and stabilize sandbox integration tests (google-gemini#24834) * test(sdk): add unit tests for GeminiCliSession (google-gemini#21897) * fix(cli): restore file path display in edit and write tool confirmations (google-gemini#24974) * fix(cli-ui): enable Ctrl+Backspace for word deletion in Windows Terminal (google-gemini#21447) * fix(core): dynamic session ID injection to resolve resume bugs (google-gemini#24972) * Update ink version to 6.6.9 (google-gemini#24980) * feat(core): refine shell tool description display logic (google-gemini#24903) * Generalize evals infra to support more types of evals, organization and queuing of named suites (google-gemini#24941) * fix(cli): optimize startup with lightweight parent process (google-gemini#24667) * refactor(sandbox): use centralized sandbox paths in macOS Seatbelt implementation (google-gemini#24984) * feat(cli): refine tool output formatting for compact mode (google-gemini#24677) * fix(sdk): skip broken sendStream tests to unblock nightly (google-gemini#25000) * refactor(core): use centralized path resolution for Linux sandbox (google-gemini#24985) * Support ctrl+shift+g (google-gemini#25035) * feat(core): refactor subagent tool to unified invoke_subagent tool (google-gemini#24489) * fix(core): add explicit git identity env vars to prevent sandbox checkpointing error (google-gemini#19775) Co-authored-by: David Pierce <davidapierce@google.com> * fix: respect hideContextPercentage when FooterConfigDialog is closed without changes (google-gemini#24773) Co-authored-by: Coco Sheng <cocosheng@google.com> * fix(cli): suppress unhandled AbortError logs during request cancellation (google-gemini#22621) * Automated documentation audit (google-gemini#24567) * feat(cli): implement useAgentStream hook (google-gemini#24292) Co-authored-by: Adam Weidman <adamfweidman@gmail.com> Co-authored-by: Adam Weidman <adamfweidman@google.com> * refactor(core): remove legacy subagent wrapping tools (google-gemini#25053) * refactor(plan) Clean default plan toml (google-gemini#25037) * fix(core): honor retryDelay in RetryInfo for 503 errors (google-gemini#25057) * fix(core): remediate subagent memory leaks using AbortSignal in MessageBus (google-gemini#25048) * feat(cli): wire up useAgentStream in AppContainer (google-gemini#24297) Co-authored-by: Adam Weidman <adamfweidman@gmail.com> Co-authored-by: Adam Weidman <adamfweidman@google.com> * feat(core): migrate chat recording to JSONL streaming (google-gemini#23749) * fix(core): clear 5-minute timeouts in oauth flow to prevent memory leaks (google-gemini#24968) * fix(sandbox): centralize async git worktree resolution and enforce read-only security (google-gemini#25040) * feat(test): add high-volume shell test and refine perf harness (google-gemini#24983) * fix(core): silently handle EPERM when listing dir structure (google-gemini#25066) * Changelog for v0.37.1 (google-gemini#25055) Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> * fix: decode Uint8Array and multi-byte UTF-8 in API error messages (google-gemini#23341) Co-authored-by: Coco Sheng <cocosheng@google.com> * Automated documentation audit results (google-gemini#22755) * debugging(ui): add optional debugRainbow setting (google-gemini#25088) * fix: resolve lifecycle memory leaks by cleaning up listeners and root closures (google-gemini#25049) * docs(cli): updates f12 description to be more precise (google-gemini#15816) * fix(cli): mark /settings as unsafe to run concurrently (google-gemini#25061) * fix(core): remove buffer slice to prevent OOM on large output streams (google-gemini#25094) * feat(core): persist subagent agentId in tool call records (google-gemini#25092) * chore(core): increase codebase investigator turn limits to 50 (google-gemini#25125) * refactor(core): consolidate execute() arguments into ExecuteOptions (google-gemini#25101) * feat(core): add Strategic Re-evaluation guidance to system prompt (google-gemini#25062) * fix(core): preserve shell execution config fields on update (google-gemini#25113) * docs: add vi shortcuts and clarify MCP sandbox setup (google-gemini#21679) Co-authored-by: Jenna Inouye <jinouye@google.com> * fix(cli): pass session id to interactive shell executions (google-gemini#25114) * fix(cli): resolve text sanitization data loss due to C1 control characters (google-gemini#22624) * feat(core): add large memory regression test (google-gemini#25059) * fix(core): resolve PTY exhaustion and orphan MCP subprocess leaks (google-gemini#25079) * chore: switch from keytar to @github/keytar (google-gemini#25143) * chore(deps): update vulnerable dependencies via npm audit fix (google-gemini#25140) * perf(sandbox): optimize Windows sandbox initialization via native ACL application (google-gemini#25077) * fix: improve audio MIME normalization and validation in file reads (google-gemini#21636) Co-authored-by: Coco Sheng <cocosheng@google.com> * docs: Update docs-audit to include changes in PR body (google-gemini#25153) * docs: correct documentation for enforced authentication type (google-gemini#25142) * fix(cli): exclude update_topic from confirmation queue count (google-gemini#24945) * Memory fix for trace's streamWrapper. (google-gemini#25089) * fix(core): fix quota footer for non-auto models and improve display (google-gemini#25121) * docs(contributing): clarify self-assignment policy for issues (google-gemini#23087) * feat(core): add skill patching support with /memory inbox integration (google-gemini#25148) * Stop suppressing thoughts and text in model response (google-gemini#25073) * fix(release): prefix git hash in nightly versions to prevent semver normalization (google-gemini#25304) * feat(cli): extract QuotaContext and resolve infinite render loop (google-gemini#24959) * refactor(core): extract and centralize sandbox path utilities (google-gemini#25305) Co-authored-by: David Pierce <davidapierce@google.com> * feat(ui): added enhancements to scroll momentum (google-gemini#24447) * fix(core): replace custom binary detection with isbinaryfile to correctly handle UTF-8 (U+FFFD) (google-gemini#25297) * feat(agent): implement tool-controlled display protocol (Steps 2-3) (google-gemini#25134) * Stop showing scrollbar unless we are in terminalBuffer mode (google-gemini#25320) * fix(core): expose GEMINI_PLANS_DIR to hook environment (google-gemini#25296) Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> * feat: support auth block in MCP servers config in agents (google-gemini#24770) * feat(core): implement silent fallback for Plan Mode model routing (google-gemini#25317) * fix: correct redirect count increment in fetchJson (google-gemini#24896) Co-authored-by: Tommaso Sciortino <sciortino@gmail.com> * fix(core): prevent secondary crash in ModelRouterService finally block (google-gemini#25333) * feat(core): introduce decoupled ContextManager and Sidecar architecture (google-gemini#24752) * docs(core): update generalist agent documentation (google-gemini#25325) * chore(mcp): check MCP error code over brittle string match (google-gemini#25381) * test(core): improve sandbox integration test coverage and fix OS-specific failures (google-gemini#25307) Co-authored-by: David Pierce <davidapierce@google.com> * feat(plan): update plan mode prompt to allow showing plan content (google-gemini#25058) * fix(core): use debug level for keychain fallback logging (google-gemini#25398) * feat(test): add a performance test in asian language (google-gemini#25392) * feat(cli): enable mouse clicking for cursor positioning in AskUser multi-line answers (google-gemini#24630) * fix(core): detect kmscon terminal as supporting true color (google-gemini#25282) Co-authored-by: Adib234 <30782825+Adib234@users.noreply.github.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> * ci: add agent session drift check workflow (google-gemini#25389) * use macos-latest-large runner where applicable. (google-gemini#25413) * Changelog for v0.37.2 (google-gemini#25336) Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> * chore(release): bump version to 0.40.0-nightly.20260414.g5b1f7375a (google-gemini#25420) * Fix(core): retry additional OpenSSL 3.x SSL errors during streaming (google-gemini#16075) (google-gemini#25187) * fix(core): prevent YOLO mode from being downgraded (google-gemini#25341) * feat: bundle ripgrep binaries into SEA for offline support (google-gemini#25342) * Changelog for v0.39.0-preview.0 (google-gemini#25417) Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> Co-authored-by: Sam Roberts <158088236+g-samroberts@users.noreply.github.com> * feat(test): add large conversation scenario for performance test (google-gemini#25331) * improve(core): require recurrence evidence before extracting skills (google-gemini#25147) * test(evals): add subagent delegation evaluation tests (google-gemini#24619) * feat: add github colorblind themes (google-gemini#15504) Co-authored-by: Coco Sheng <cocosheng@google.com> * fix(core): honor GOOGLE_GEMINI_BASE_URL and GOOGLE_VERTEX_BASE_URL (google-gemini#25357) * fix(cli): clean up slash command IDE listeners (google-gemini#24397) Co-authored-by: Tommaso Sciortino <sciortino@gmail.com> * Changelog for v0.38.0 (google-gemini#25470) Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> * fix(evals): update eval tests for invoke_agent telemetry and project-scoped memory (google-gemini#25502) * Changelog for v0.38.1 (google-gemini#25476) Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> Co-authored-by: Sam Roberts <158088236+g-samroberts@users.noreply.github.com> * feat(core): integrate skill-creator into skill extraction agent (google-gemini#25421) * feat(cli): provide default post-submit prompt for skill command (google-gemini#25327) * feat(core): add tools to list and read MCP resources (google-gemini#25395) * fix(evals): add typecheck coverage for evals, integration-tests, and memory-tests (google-gemini#25480) * Use OSC 777 for terminal notifications (google-gemini#25300) * fix(extensions): fix bundling for examples (google-gemini#25542) * fix(cli): reset plan session state on /clear (google-gemini#25515) * feat(core): add .mdx support to get-internal-docs tool (google-gemini#25090) * docs(policy): mention that workspace policies are broken (google-gemini#24367) Co-authored-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org> * fix(core): allow explicit write permissions to override governance file protections in sandboxes (google-gemini#25338) * feat(sandbox): resolve custom seatbelt profiles from $HOME/.gemini first (google-gemini#25427) Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com> * Reduce blank lines. (google-gemini#25563) * fix(ui): revert preview theme on dialog unmount (google-gemini#22542) Co-authored-by: Jack Wotherspoon <jackwoth@google.com> * fix(core): fix ShellExecutionConfig spread and add ProjectRegistry save backoff (google-gemini#25382) * feat(core): Disable topic updates for subagents (google-gemini#25567) * feat(core): enable topic update narration by default and promote to general (google-gemini#25586) Co-authored-by: JAYADITYA <96861162+JayadityaGit@users.noreply.github.com> Co-authored-by: Jack Wotherspoon <jackwoth@google.com> * docs: migrate installation and authentication to mdx with tabbed layouts (google-gemini#25155) * feat(config): split memoryManager flag into autoMemory (google-gemini#25601) * fix(core): allow Cloud Shell users to use PRO_MODEL_NO_ACCESS experiment (google-gemini#25702) * fix(cli): round slow render latency to avoid opentelemetry float warning (google-gemini#25709) * docs(tracker): introduce experimental task tracker feature (google-gemini#24556) * docs(cli): fix inconsistent system.md casing in system prompt docs (google-gemini#25414) Co-authored-by: cynthialong0-0 <82900738+cynthialong0-0@users.noreply.github.com> * feat(cli): add streamlined `gemini gemma` local model setup (google-gemini#25498) Co-authored-by: Abhijit Balaji <abhijitbalaji@google.com> Co-authored-by: Samee Zahid <sameez@google.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> * Changelog for v0.38.2 (google-gemini#25593) Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> * Fix: Disallow overriding IDE stdio via workspace .env (RCE) (google-gemini#25022) Co-authored-by: Tommaso Sciortino <sciortino@gmail.com> * feat(test): refactor the memory usage test to use metrics from CLI process instead of test runner (google-gemini#25708) * feat(vertex): add settings for Vertex AI request routing (google-gemini#25513) * Fix/allow for session persistence (google-gemini#25176) * fix(core): resolve nested plan directory duplication and relative path policies (google-gemini#25138) * feat: detect new files in @ recommendations with watcher based updates (google-gemini#25256) * Allow dots on GEMINI_API_KEY (google-gemini#25497) * feat(telemetry): add flag for enabling traces specifically (google-gemini#25343) * fix(cli): use newline in shell command wrapping to avoid breaking heredocs (google-gemini#25537) * fix(cli): ensure theme dialog labels are rendered for all themes (google-gemini#24599) Co-authored-by: cynthialong0-0 <82900738+cynthialong0-0@users.noreply.github.com> * fix(core): disable detached mode in Bun to prevent immediate SIGHUP of child processes (google-gemini#22620) * feat: add /new as alias for /clear and refine command description (google-gemini#17865) * fix(cli): start auto memory in ACP sessions (google-gemini#25626) * fix(core): remove duplicate initialize call on agents refreshed (google-gemini#25670) * test(e2e): default integration tests to Flash Preview (google-gemini#25753) * refactor(memory): replace MemoryManagerAgent with prompt-driven memory editing across four tiers (google-gemini#25716) * fix(cli): fix "/clear (new)" command (google-gemini#25801) * fix(core): use dynamic CLI version for IDE client instead of hardcoded '1.0.0' (google-gemini#24414) Co-authored-by: cynthialong0-0 <82900738+cynthialong0-0@users.noreply.github.com> * fix(core): handle line endings in ignore file parsing (google-gemini#23895) Co-authored-by: cynthialong0-0 <82900738+cynthialong0-0@users.noreply.github.com> * Fix/command injection shell (google-gemini#24170) Co-authored-by: David Pierce <davidapierce@google.com> * fix(ui): removed background color for input (google-gemini#25339) * fix(devtools): reduce memory usage and defer connection (google-gemini#24496) * fix(core): support jsonl session logs in memory and summary services (google-gemini#25816) * fix(release): exclude ripgrep binaries from npm tarballs (google-gemini#25841) * chore(release): v0.40.0-preview.2 * feat(cli): secure .env loading and enforce workspace trust in headless mode (google-gemini#25814) Co-authored-by: galz10 <galzahavi@google.com> Co-authored-by: davidapierce <davidapierce@google.com> * feat(core): enhance shell command validation and add core tools allowlist (google-gemini#25720) Co-authored-by: David Pierce <davidapierce@google.com> Co-authored-by: Keith Schaab <keithsc@google.com> Co-authored-by: Keith Schaab <keith.schaab@gmail.com> Co-authored-by: Emily Hedlund <ehedlund@google.com> * update FatalUntrustedWorkspaceError message to include doc link (google-gemini#25874) * chore(release): v0.40.0-preview.3 * fix(patch): cherry-pick 048bf6e to release/v0.40.0-preview.3-pr-25941 to patch version v0.40.0-preview.3 and create version 0.40.0-preview.4 (google-gemini#25942) Co-authored-by: Tommaso Sciortino <sciortino@gmail.com> * chore(release): v0.40.0-preview.4 * fix(patch): cherry-pick 54b7586 to release/v0.40.0-preview.4-pr-26066 [CONFLICTS] (google-gemini#26124) Co-authored-by: David Pierce <davidapierce@google.com> * chore(release): v0.40.0-preview.5 * chore(release): v0.40.0 * Remove temporary commit message file from tracking This cleans the repository after the upstream merge and ignores the helper file so future local commits do not pollute branch diffs. * Add optional image build trigger to fork resync skill Document the final workflow trigger step for cases where a new container image is required, including the exact workflow name and inputs, and warn against passing the branch name as the version. * Clarify fork bump behavior in resync skill Document that the fork should be bumped from upstream without applying fork patches back onto the upstream release branch, keeping fork-specific changes isolated to the fork resync workflow. --------- Co-authored-by: ruomeng <ruomeng@google.com> Co-authored-by: Sri Pasumarthi <111310667+sripasg@users.noreply.github.com> Co-authored-by: Sandy Tao <sandytao520@icloud.com> Co-authored-by: gemini-cli-robot <gemini-cli-robot@google.com> Co-authored-by: Emily Hedlund <ehedlund@google.com> Co-authored-by: Spencer <spencertang@google.com> Co-authored-by: Jacob Richman <jacob314@gmail.com> Co-authored-by: gemini-cli-robot <224641728+gemini-cli-robot@users.noreply.github.com> Co-authored-by: g-samroberts <samroberts@google.com> Co-authored-by: JAYADITYA <96861162+JayadityaGit@users.noreply.github.com> Co-authored-by: Coco Sheng <cocosheng@google.com> Co-authored-by: Sam Roberts <158088236+g-samroberts@users.noreply.github.com> Co-authored-by: Adamya Singh <adamyasingh54@gmail.com> Co-authored-by: Jarrod Whelan <150866123+jwhelangoog@users.noreply.github.com> Co-authored-by: dogukanozen <dogukannozen@hotmail.com> Co-authored-by: Tommaso Sciortino <sciortino@gmail.com> Co-authored-by: Christian Gunderman <gundermanc@google.com> Co-authored-by: Sehoon Shon <sshon@google.com> Co-authored-by: Abhi <43648792+abhipatel12@users.noreply.github.com> Co-authored-by: MD. MOHIBUR RAHMAN <35300157+mrpmohiburrahman@users.noreply.github.com> Co-authored-by: David Pierce <davidapierce@google.com> Co-authored-by: chernistry <73943355+chernistry@users.noreply.github.com> Co-authored-by: euxaristia <25621994+euxaristia@users.noreply.github.com> Co-authored-by: Michael Bleigh <mbleigh@mbleigh.com> Co-authored-by: Adam Weidman <adamfweidman@gmail.com> Co-authored-by: Adam Weidman <adamfweidman@google.com> Co-authored-by: Yuna Seol <yunaseol@gmail.com> Co-authored-by: June <kimjune01@gmail.com> Co-authored-by: Aishanee Shah <aishaneeshah@google.com> Co-authored-by: Jason Matthew Suhari <jasonmatthewsuhari@gmail.com> Co-authored-by: Christopher Thomas <cobekgn@gmail.com> Co-authored-by: Jenna Inouye <jinouye@google.com> Co-authored-by: cynthialong0-0 <82900738+cynthialong0-0@users.noreply.github.com> Co-authored-by: M Junaid Shaukat <154750865+junaiddshaukat@users.noreply.github.com> Co-authored-by: Abhijit Balaji <abhijitbalaji@google.com> Co-authored-by: Mark Griffith <anthraxmilkshake@hotmail.com> Co-authored-by: Jack Wotherspoon <jackwoth@google.com> Co-authored-by: Jesse Rosenstock <jesse.rosenstock@gmail.com> Co-authored-by: Adib234 <30782825+Adib234@users.noreply.github.com> Co-authored-by: Dev Randalpura <devrandalpura@google.com> Co-authored-by: Anjaligarhwal <anjaligarhwal1610@gmail.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Co-authored-by: Tanmay Vartak <9002434+TanmayVartak@users.noreply.github.com> Co-authored-by: Jerop Kipruto <jerop@google.com> Co-authored-by: Kevin Zhao <kevin8093@126.com> Co-authored-by: joshualitt <joshualitt@google.com> Co-authored-by: Clay <claygeo6@gmail.com> Co-authored-by: Adam Weidman <65992621+adamfweidman@users.noreply.github.com> Co-authored-by: Rob Clevenger <rcleveng@users.noreply.github.com> Co-authored-by: Gal Zahavi <38544478+galz10@users.noreply.github.com> Co-authored-by: anj-s <32556631+anj-s@users.noreply.github.com> Co-authored-by: Z1xus <40185941+Z1xus@users.noreply.github.com> Co-authored-by: jackyliuxx <jackyliuxx@gmail.com> Co-authored-by: Nicolas Ouellet-Payeur <nicolaso@google.com> Co-authored-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Co-authored-by: Matt Van Horn <mvanhorn@users.noreply.github.com> Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com> Co-authored-by: Mahima Shanware <mahima.shanware@gmail.com> Co-authored-by: Timo <36011879+Bodlux@users.noreply.github.com> Co-authored-by: Samee Zahid <sameescouser24@gmail.com> Co-authored-by: Samee Zahid <sameez@google.com> Co-authored-by: Mundur <150439604+M0nd0R@users.noreply.github.com> Co-authored-by: Gordon Hui <125633533+gordonhwc@users.noreply.github.com> Co-authored-by: Muhammad Ahsan Farooq <ahsanfarooq210@gmail.com> Co-authored-by: PRAS Samin <103464543+prassamin@users.noreply.github.com> Co-authored-by: Danyel Cabello <danyel.nerv@gmail.com> Co-authored-by: Vedant Mahajan <vedant.04.mahajan@gmail.com> Co-authored-by: mini2s <143020328+mini2s@users.noreply.github.com> Co-authored-by: Kishan Patel <132991737+thekishandev@users.noreply.github.com> Co-authored-by: xoma-zver <maxidiplomat@gmail.com> Co-authored-by: Horizon_Architect_07 <famousrajbhatt@gmail.com> Co-authored-by: galz10 <galzahavi@google.com> Co-authored-by: Keith Schaab <keithsc@google.com> Co-authored-by: Keith Schaab <keith.schaab@gmail.com> Co-authored-by: codex-bot <spigelly+gh-bot@gmail.com>

ved015 requested a review from a team as a code owner January 29, 2026 15:29

gemini-code-assist Bot reviewed Jan 29, 2026

View reviewed changes

Comment thread packages/cli/src/ui/commands/newCommand.test.ts Outdated

Comment thread packages/cli/src/ui/commands/newCommand.test.ts Outdated

gemini-code-assist Bot reviewed Jan 29, 2026

View reviewed changes

jackwotherspoon closed this Feb 1, 2026

jackwotherspoon reopened this Mar 10, 2026

add alias for clear

72d9917

ved015 force-pushed the feat/add_command branch from 561b637 to 72d9917 Compare March 16, 2026 14:17

ved015 added 2 commits March 16, 2026 19:57

add altname

ef790eb

Merge branch 'main' into feat/add_command

c23429b

ved015 added 3 commits March 20, 2026 00:32

Merge branch 'main' into feat/add_command

ad50cb4

Merge branch 'main' into feat/add_command

b486c39

Merge branch 'main' into feat/add_command

84124cd

ved015 added 2 commits April 14, 2026 18:58

Merge branch 'main' into feat/add_command

5a0b50e

Merge branch 'main' into feat/add_command

fd115e0

jackwotherspoon approved these changes Apr 16, 2026

View reviewed changes

ved015 changed the title ~~add new command to create new session without clearing context of previous~~ feat: add /new as alias for /clear and refine command description Apr 16, 2026

Merge branch 'main' into feat/add_command

70a8458

scidomino enabled auto-merge April 21, 2026 18:11

scidomino added this pull request to the merge queue Apr 21, 2026

Merged via the queue into google-gemini:main with commit 189c0ac Apr 21, 2026
27 checks passed

github-actions Bot mentioned this pull request Apr 29, 2026

Tool release: Gemini CLI v0.40.0 (was v0.39.1) agent-sh/agnix#844

Closed

zbynekwinkler mentioned this pull request Apr 29, 2026

Add /new command equivalent to starting gemini cli #16835

Closed

Conversation

ved015 commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Details

Related Issues

How to Validate

Pre-Merge Checklist

Uh oh!

gemini-code-assist Bot commented Jan 29, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

ved015 commented Jan 29, 2026

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist Bot Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

ved015 Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

jackwotherspoon commented Jan 29, 2026

Uh oh!

ved015 commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ved015 commented Feb 1, 2026

Uh oh!

jackwotherspoon commented Feb 1, 2026

Uh oh!

ved015 commented Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jackwotherspoon commented Feb 1, 2026

Uh oh!

ved015 commented Feb 1, 2026

Uh oh!

ved015 commented Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ved015 commented Feb 21, 2026

Uh oh!

jackwotherspoon commented Feb 26, 2026

Uh oh!

ved015 commented Mar 2, 2026

Uh oh!

ved015 commented Mar 10, 2026

Uh oh!

jackwotherspoon commented Mar 10, 2026

Uh oh!

jackwotherspoon commented Mar 10, 2026

Uh oh!

ved015 commented Mar 10, 2026

Uh oh!

ved015 commented Mar 10, 2026

Uh oh!

jackwotherspoon commented Mar 11, 2026

Uh oh!

ved015 commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jackwotherspoon commented Mar 11, 2026

Uh oh!

ved015 commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ved015 commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ved015 commented Jan 29, 2026 •

edited

Loading

ved015 commented Jan 29, 2026 •

edited

Loading

ved015 commented Feb 1, 2026 •

edited

Loading

ved015 commented Feb 6, 2026 •

edited

Loading

ved015 commented Mar 11, 2026 •

edited

Loading

ved015 commented Mar 11, 2026 •

edited

Loading

ved015 commented Mar 11, 2026 •

edited

Loading