chore: Update chat bot endpoint

[hetunandu]

Description

Updates the endpoint used to embed the Custom Widget Builder AI chat bot builder

Automation

/ok-to-test tags="@tag.Sanity"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/12645753810
Commit: 7856ee4
Cypress dashboard.
Tags: @tag.Sanity
Spec:

---

Tue, 07 Jan 2025 06:11:13 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Chores
  • Updated the AI bot URL endpoint for the custom widget chat interface
  • Replaced the existing bot identifier with a new one

[coderabbitai]

Walkthrough

The pull request involves updating the CUSTOM_WIDGET_AI_BOT_URL constant in the custom widget builder. The change modifies the bot endpoint URL, switching from a previous identifier to a new one. This update appears to be a targeted modification of the AI chat widget's backend connection point, maintaining the existing URL structure but pointing to a different service instance.

Changes

File	Change Summary
app/client/src/pages/Editor/CustomWidgetBuilder/constants.ts	Updated CUSTOM_WIDGET_AI_BOT_URL constant with a new bot endpoint URL

Possibly related PRs

• chore: fix custom widget 's updateModel #38129: Modifications to the handleModelUpdate function in a custom widget, potentially related to widget functionality updates

Suggested labels

skip-changelog, IDE Product, Task

Suggested reviewers

• sagar-qa007

Poem

🤖 A bot URL shifts its digital home,
Silently sliding to a new chrome,
From one endpoint to another it leaps,
Carrying whispers of code that it keeps,
A subtle dance of bits and bytes! 🌐

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[hetunandu]

/build-deploy-preview

[github-actions]

Deploying Your Preview: https://github.com/appsmithorg/appsmith/actions/runs/12645754638.
Workflow: On demand build Docker image and deploy preview.
skip-tests: . env: .
PR: 38513.
recreate: .

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

app/client/src/pages/Editor/CustomWidgetBuilder/constants.ts (1)

73-74: Consider adding a feature flag for gradual rollout.

Since this is a significant endpoint change, consider implementing a feature flag to enable gradual rollout and easy rollback if issues are discovered.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a75c530 and 7856ee4.

📒 Files selected for processing (1)

• app/client/src/pages/Editor/CustomWidgetBuilder/constants.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: perform-test / rts-build / build
• GitHub Check: client-unit-tests / client-unit-tests
• GitHub Check: client-build / client-build
• GitHub Check: client-lint / client-lint
• GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
• GitHub Check: client-prettier / prettier-check

🔇 Additional comments (1)

app/client/src/pages/Editor/CustomWidgetBuilder/constants.ts (1)

73-74: Verify the new endpoint availability and functionality.

The chat bot endpoint has been migrated from app-builder-bot/custom-widget-bot-* to ai-co-pilot/chat-widget-*.

Run this script to check the endpoint availability:

Additionally, please ensure:

1. The new endpoint supports all existing query parameters
2. The chat widget functionality remains unchanged
3. DevRel/Marketing teams are notified if this change affects end users

✅ Verification successful

Endpoint verification successful

The new chat bot endpoint is properly configured and accessible. The service migration appears to have been implemented correctly.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the new endpoint is accessible and returns expected status
curl -I "https://internal.appsmith.com/app/ai-co-pilot/chat-widget-675732c903bc2614401bd53b"

Length of output: 1430

[github-actions]

Deploy-Preview-URL: https://ce-38513.dp.appsmith.com