summaryrefslogtreecommitdiff
path: root/packages/server/src/utils
AgeCommit message (Collapse)Author
2025-05-02Cleanup low value comments. (#248)Jacob Richman
2025-05-01Support escaping spaces in file paths. (#241)Jacob Richman
2025-04-26Prevent console.warn's for tool calls.Taylor Mullen
- Added helper for extracting text content from responses without warning. See fixed issue for more detail: https://b.corp.google.com/issues/414005146
2025-04-23remove dead code (#131)Olcan
2025-04-22Initiate the GeminiClient with a configJaana Dogan
Also address the open readability improvement comments from #104.
2025-04-21Simplify GeminiClient (#101)Jaana Dogan
Doing some more clean-up: * Remove confusing continue/break * Handle empty result * Rename the file just client.js
2025-04-21fix: remove circular dependency in background terminal analyzer (#94)Brandon Keiji
2025-04-21Remove duplicate CLI tools module, remove the global tool registry (#89)Jaana Dogan
2025-04-21Remove redundant else branches (#86)Jaana Dogan
Else branches are an anti pattern especially if you can easily return from the previous branch. Over time, else branches cause deep nesting and make code unreadable and unmaintainable. Remove elses where possible.
2025-04-21Fix 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-19Starting 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.