Feature/ChatCloudflareWorkersAI

[udaykumar-dhokia]

Summary

This PR adds support for Cloudflare Workers AI chat models with improved type safety, allowing you to use Cloudflare's serverless inference platform directly within your flows.

Flowise.mp4

Features

• Model Selection
  Defaults to @cf/meta/llama-3.1-8b-instruct-fast, with support for any chat model string compatible with Cloudflare Workers AI.

• Base URL Configuration
  Optional base URL for custom endpoints.
  Defaults to:
  https://api.cloudflare.com/client/v4/accounts

Changes

New Node

• Name: ChatCloudflareWorkersAI
• Location:
  packages/components/nodes/chatmodels/ChatCloudflareWorkersAI
• Description:
  Wraps ChatCloudflareWorkersAI from @langchain/cloudflare

New Credential

• Name: CloudflareApi
• Requirements:
  • Cloudflare Account ID
  • Cloudflare API Token

Dependency Update

• Added @langchain/cloudflare to:
  packages/components/package.json

[gemini-code-assist]

Summary of Changes

Hello @udaykumar-dhokia, 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 expands the platform's AI capabilities by integrating Cloudflare Workers AI chat models. It provides users with a new, type-safe way to connect to Cloudflare's serverless inference platform, complete with a dedicated node for chat models and a new credential for secure API access.

Highlights

• Cloudflare Workers AI Integration: Introduces support for Cloudflare Workers AI chat models, enabling serverless inference directly within flows with improved type safety.
• New Chat Model Node: A ChatCloudflareWorkersAI node has been added, defaulting to @cf/meta/llama-3.1-8b-instruct-fast and supporting custom base URLs.
• Dedicated Cloudflare Credential: A new CloudflareApi credential type is introduced to securely manage Cloudflare Account ID and API Token.
• Dependency Update: The @langchain/cloudflare package has been added to the project dependencies.

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 support for Cloudflare Workers AI chat models, including a new ChatCloudflareWorkersAI node and a CloudflareApi credential. The implementation is well-structured and aligns with the existing codebase patterns. The changes are clear and the feature is a valuable addition. I have one suggestion to enhance type safety in the new node implementation.