fix(parseProviderResponse): handle Google tool finish reason

[steebchen]

Summary

• Correctly handle the "tool_calls" finish reason returned by Google in the parseProviderResponse function
• Add explicit check for "tool_calls" to avoid misclassification as "stop"

Changes

Core Functionality

• Updated parseProviderResponse in parse-provider-response.ts to:
  • Check if googleFinishReason is "tool_calls" and return "tool_calls" as the finish reason
  • Retain existing handling for "length", "SAFETY" (mapped to "content_filter"), and fallback to "stop" for unknown reasons

Test plan

• Verify that responses with finish reason "tool_calls" are correctly identified and handled
• Ensure no regressions in handling other finish reasons
• Confirm that fallback to "stop" remains intact for unknown reasons

🌿 Generated by Terry

---

ℹ️ Tag @terragon-labs to ask questions and address PR feedback

📎 Task: https://www.terragonlabs.com/task/0405a65a-261f-45fb-a54d-5774436bfb02

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch terragon/fix-google-tool-finish-reason

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}