fix errors of claude4.5

[tastelikefeet]

Change Summary

Related issue number

Checklist

• The pull request title is a good summary of the changes - it will be used in the changelog
• Unit tests for the changes exist
• Run pre-commit install and pre-commit run --all-files before git commit, and passed lint check.
• Documentation reflects the changes where applicable

[gemini-code-assist]

Summary of Changes

Hello @tastelikefeet, 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 focuses on enhancing the system's compatibility and robustness with the Claude 4.5 model. Key changes include updating the Claude model version, implementing more resilient JSON parsing for tool arguments, and addressing specific model output behaviors. Additionally, it streamlines the FileSystemTool by removing unnecessary components and expands the architect agent's capabilities to cover both frontend and backend project architectures.

Highlights

• Claude Model Update: The LLM model configuration has been updated across architecture.yaml, coding.yaml, and refine.yaml to use claude-sonnet-4-5-20250929, upgrading from an older version.
• Robust JSON Parsing for Tool Calls: Error handling for JSON parsing of tool call arguments has been significantly improved in llm_agent.py and tool_manager.py. try-except blocks now catch JSONDecodeError to prevent crashes and provide informative error messages when invalid JSON is encountered.
• Tool Call Content Default: A specific fix was added to llm_agent.py to assign a default content message ('Let me do a tool calling.') when an assistant response includes tool calls but no explicit content, addressing a potential behavior of the Claude model.
• Filesystem Tool Cleanup: The filesystem_tool.py file has been refactored to remove an unused omegaconf.DictConfig import and the call_history tracking mechanism, simplifying the tool's implementation.
• Expanded Architect Agent Scope: The system prompt in architecture.yaml has been updated to broaden the architect agent's responsibilities to include both frontend and backend projects, specifically mentioning Node.js for backend development.

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.

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 introduces several fixes and improvements, primarily aimed at increasing robustness when interacting with LLMs. The changes include better handling of JSON decoding errors and ensuring compatibility with models that might not provide content alongside tool calls. Additionally, the PR cleans up some unused code and updates model configurations. I've identified a minor typo in a configuration file that could be corrected.