Composio tool auth fixes, no auth support and connected accounts selection.

[chiragjagga]

• Added support for no auth apps in composio.
• Added option to select connected account as user can have multiple connected accounts for the same app.
• Fixes [BUG] Composio - Auth Status fails to update to Connected #4570

Note:

• The currently used package composio-core is deprecated.
• Spent a couple days in dependency-hell trying to upgrade to the newer @composio/core package but that requires a lot of unrelated changes due to zod version being upgraded to 4.x which introduces major breaking changes in other unrelated areas as it is used as a peer dependency in the newer composio/core package.
• If we upgrade zod to 4.x version in the future, composio can be upgraded to the newer package.

No Auth:

No Connections Available:

Valid active connections:

Workflow:

Composio_fix.2.1.mp4

[gemini-code-assist]

Summary of Changes

Hello @chiragjagga, 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 significantly improves the Composio tool's integration capabilities by introducing support for applications that do not require authentication and allowing users to explicitly choose from multiple connected accounts for a given application. These changes enhance the tool's adaptability and user control, addressing a known issue and providing a more robust interaction model.

Highlights

• No-Auth App Support: The Composio tool now supports applications that do not require authentication, streamlining their integration and usage.
• Connected Account Selection: Users can now select a specific connected account when an application has multiple active connections, enhancing control and flexibility over which account is used.
• Dependency Update: The composio-core package has been updated to version ^0.5.39.
• Known Limitation: A full upgrade to the latest @composio/core is currently blocked by zod version conflicts, which would require significant unrelated changes across the codebase.

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 improvements to the Composio tool integration, including support for applications without authentication and allowing users to select from multiple connected accounts. The changes are well-implemented and address the described goals.

My review includes a few suggestions to enhance the code quality:

• Improving type safety by replacing any with specific interfaces for Composio API objects.
• Refactoring duplicated logic into a helper function for better maintainability.
• Adding a necessary check to prevent potential runtime errors when an application is not selected.

Overall, this is a great update that significantly improves the usability of the Composio tool.