Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat(Otto) Add Initial Otto Chat Bot code #9266

Merged
merged 70 commits into from
Mar 6, 2025
Merged

Conversation

Bentlybro
Copy link
Member

@Bentlybro Bentlybro commented Jan 14, 2025

Changes 🏗️

This is to add the Otto chat bot to the frontend UI.

The changes i have made for this goes as follows:

  • I have made and added a basic chat UI widget to the build page, this will become the main UI for Otto, this will be getting updates in the future.
  • I have made an API route /api/otto/ask that will receive the message from the frontend and pass it to the Otto API that we have setup on GCP.

I already have plans for how we can improve the UI and make it more modular, this way we can add more features to Otto down the line!

Config Changes

When we merge this, we will need to add the ENV var for otto_api_url that will be the URL from GCP where the API is being hosted!

This is now ready for a review as the backend API is up and running, to who ever does test this, if you want the API url please DM me 😄

image

Checklist 📋

For code changes:

  • I have clearly listed my changes in the PR description
  • I have made a test plan
  • I have tested my changes according to the test plan:
    • Set the ENV var for otto_api_url - ask @Bentlybro for this
    • Set the ENV var for NEXT_PUBLIC_BEHAVE_AS to CLOUD
    • Send otto a message from the build page frontend
    • Send otto a message that contains graph data to see if the sending graph data works

@github-actions github-actions bot added platform/frontend AutoGPT Platform - Front end conflicts Automatically applied to PRs with merge conflicts platform/backend AutoGPT Platform - Back end labels Jan 14, 2025
Copy link
Contributor

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

Copy link

netlify bot commented Jan 14, 2025

Deploy Preview for auto-gpt-docs-dev canceled.

Name Link
🔨 Latest commit ff1224b
🔍 Latest deploy log https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/67c9dc2d6944850008d02657

Copy link

netlify bot commented Jan 14, 2025

Deploy Preview for auto-gpt-docs canceled.

Name Link
🔨 Latest commit ff1224b
🔍 Latest deploy log https://app.netlify.com/sites/auto-gpt-docs/deploys/67c9dc2d45568b0008e3da1d

@Bentlybro Bentlybro force-pushed the add-Otto-chat-bot-UI branch from c3fe0a5 to b055d16 Compare January 14, 2025 17:22
Copy link
Contributor

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

@github-actions github-actions bot added size/xl and removed conflicts Automatically applied to PRs with merge conflicts size/l labels Jan 14, 2025
@github-actions github-actions bot added the conflicts Automatically applied to PRs with merge conflicts label Jan 28, 2025
Copy link
Contributor

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

@github-actions github-actions bot removed the conflicts Automatically applied to PRs with merge conflicts label Feb 7, 2025
Copy link
Contributor

github-actions bot commented Feb 7, 2025

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

Copy link

deepsource-io bot commented Feb 7, 2025

Here's the code health analysis summary for commits 7eb0466..ff1224b. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ Success
❗ 66 occurences introduced
🎯 59 occurences resolved
View Check ↗
DeepSource Python LogoPython✅ Success
❗ 13 occurences introduced
🎯 6 occurences resolved
View Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

@github-actions github-actions bot added size/l size/xl conflicts Automatically applied to PRs with merge conflicts and removed size/xl size/l labels Feb 7, 2025
Copy link
Contributor

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

Copy link
Contributor

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

@github-actions github-actions bot removed the conflicts Automatically applied to PRs with merge conflicts label Feb 14, 2025
Copy link
Contributor

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

@github-actions github-actions bot added the conflicts Automatically applied to PRs with merge conflicts label Feb 25, 2025
@github-actions github-actions bot removed the conflicts Automatically applied to PRs with merge conflicts label Mar 6, 2025
Copy link
Contributor

github-actions bot commented Mar 6, 2025

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

@AutoGPT-Agent
Copy link

The PR appears to be well structured with several good practices, but has some issues that need attention: 1) The PR template checklist is missing configuration changes section which should be filled since a new ENV variable is being added (otto_api_url) 2) Though they have a test plan, it could be more comprehensive to include error cases and authentication testing 3) The code changes properly handle user_id in the backend routes which is good

@Bentlybro Bentlybro enabled auto-merge March 6, 2025 17:21
@Bentlybro Bentlybro added this pull request to the merge queue Mar 6, 2025
Merged via the queue into dev with commit a0ecb96 Mar 6, 2025
28 checks passed
@Bentlybro Bentlybro deleted the add-Otto-chat-bot-UI branch March 6, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform/backend AutoGPT Platform - Back end platform/frontend AutoGPT Platform - Front end size/xl
Projects
Status: Done
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants