fix(cli): pass session id to interactive shell executions

[jasonmatthewsuhari]

Fixes #25111

Summary

• pass config.getSessionId() into interactive shell execution config
• add a targeted hook test asserting the session ID is propagated to ShellExecutionService.execute()

Why

Backgrounding an interactive shell currently goes through ShellExecutionService.background(pid). Recent shell background tracking expects executions to be associated with a session ID. The interactive UI path was not passing one into ShellExecutionService.execute(...), which made the runtime repro fail with Session ID is required for background operations.

Testing

• npm run test --workspace @google/gemini-cli -- src/ui/hooks/useExecutionLifecycle.test.tsx

[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 addresses an issue where interactive shell executions were failing to background properly due to a missing session ID. By ensuring the session ID is correctly propagated through the execution configuration, the system can now properly track and manage backgrounded shell processes.

Highlights

• Session ID Propagation: Updated the interactive shell execution configuration to include the session ID retrieved from the application configuration.
• Test Coverage: Added a new test case to verify that the session ID is correctly passed to the ShellExecutionService during command execution.

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 useExecutionLifecycle hook to include a session ID in the shell execution configuration. It also updates the corresponding tests to verify that the session ID is correctly passed from the configuration to the shell execution service. I have no feedback to provide.

[SH20RAJ]

Small follow-up: the regression test proves the session ID reaches ShellExecutionService.execute, but the failure mode happens later in background(pid). It would be useful to add a focused assertion that backgroundCurrentExecution() succeeds after the shell is backgrounded, so the test covers the end-to-end session lookup instead of only the config wiring.