dev/gemini-cli - [no description]

Age	Commit message (Collapse)	Author
2025-05-22	fix: forward entire tool call confirmation object through useToolScheduler ↵	Brandon Keiji
	(#481)
2025-05-21	feat: useToolScheduler hook to manage parallel tool calls (#448)	Brandon Keiji

2025-05-20	Support Images and PDFs (#447)	Jacob Richman

2025-05-16	fix: Ensure filename is available for diff rendering in write-file	Taylor Mullen
	This commit resolves a bug where the `write-file` operation could fail to render content due to a missing filename. The fix involves: - Ensuring `fileName` is consistently passed to `DiffRenderer.tsx` through `ToolConfirmationMessage.tsx`, `ToolMessage.tsx`, and `useGeminiStream.ts`. - Modifying `edit.ts` and `write-file.ts` to include `fileName` in the `FileDiff` object. - Expanding the `FileDiff` interface in `tools.ts` to include `fileName`. Additionally, this commit enhances the diff rendering by: - Adding syntax highlighting based on file extension in `DiffRenderer.tsx`. - Adding more language mappings to `getLanguageFromExtension` in `DiffRenderer.tsx`. - Added lots of tests for all the above. Fixes https://b.corp.google.com/issues/418125982
2025-05-10	Enable tools to cancel active execution.	Taylor Mullen
	- Plumbed abort signals through to tools - Updated the shell tool to properly cancel active requests by killing the entire child process tree of the underlying shell process and then report that the shell itself was canceled. Fixes https://b.corp.google.com/issues/416829935
2025-05-02	Cleanup low value comments. (#248)	Jacob Richman

2025-04-27	don't confirm invalid params in terminal tool, or in general (added comments ↵	Olcan
	to base class) (#187)
2025-04-25	more consistent confirmations, TODO to improve write confirmations, drop ↵	Olcan
	"description" from execution confirmation, add confirmation to new (still dummy) shell tool (#176)
2025-04-21	Fix Gemini Code's (GC) smarts.	Taylor Mullen
	- The tl;dr; is that GC couldn't see what the user was saying when tool call events happened in response. The rason why this was happening was because we were instantly invoking tools that the model told us to invoke and then instantly re-requesting. This resulted in the bug because the genai APIs can't update the chat history before a full response has been completed (doesn't know how to update if it's incomplete). - To address the above issue I had to do quite the large refactor. The gist is that now turns truly drive everything on the server (vs. a server client split). This ensured that when we got tool invocations we could control when/how re-requesting would happen and then also ensure that history was updated. This change also meant that the server would act as an event publisher to enable the client to react to events rather than try and weave in complex logic between the events. - A BIG change that this changeset incudes is the removal of all of the CLI tools in favor of the server tools. - Removed some dead code as part of this - NOTE: Confirmations are still broken (they were broken prior to this); however, I've set them up to be able to work in the future, I'll dot hat in a follow up to be less breaking to others. Fixes https://b.corp.google.com/issues/412320087
2025-04-19	Starting to modularize into separate cli / server packages. (#55)	Evan Senter
	* Starting to move a lot of code into packages/server * More of the massive refactor, builds and runs, some issues though. * Fixing outstanding issue with double messages. * Fixing a minor UI issue. * Fixing the build post-merge. * Running formatting. * Addressing comments.