AutoGPT icon indicating copy to clipboard operation
AutoGPT copied to clipboard

fix(backend): use marketplace name/description for downloaded agents in library

Open Bentlybro opened this issue 3 weeks ago β€’ 5 comments

Changes

Fixes agents downloaded from marketplace showing creator's graph name instead of marketplace name in user's library.

Problem: When downloading a marketplace agent, the library entry used AgentGraph.name/description (creator's version) instead of the marketplace listing name/description.

Solution: Added optional name and description override fields to LibraryAgent. When adding store agents, these are populated from the marketplace listing. The model layer falls back to graph values if not set (backward compatible).

Modified Files

  • schema.prisma: Added optional name/description to LibraryAgent
  • backend/server/v2/library/db.py: Set marketplace name/description when adding store agents
  • backend/server/v2/library/model.py: Use override fields with fallback to graph values

I still need to fully test this

For code changes:

  • [x] I have clearly listed my changes in the PR description
  • [x] I have made a test plan
  • [x] I have tested my changes according to the test plan:
    • [ ] Upload a agent to the marketplace with a custom name and description and its stored with that info
    • [ ] download that agent and the file name should be the same as the agent name from the marketplace

Bentlybro avatar Nov 10 '25 16:11 Bentlybro

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

Name Link
Latest commit b4714750a7356d8fe1dfaa9b63a4312f1093b04d
Latest deploy log https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/69133c8ba91e900008c184e9

netlify[bot] avatar Nov 10 '25 16:11 netlify[bot]

Deploy Preview for auto-gpt-docs canceled.

Name Link
Latest commit b4714750a7356d8fe1dfaa9b63a4312f1093b04d
Latest deploy log https://app.netlify.com/projects/auto-gpt-docs/deploys/69133c8b91d14a000801c664

netlify[bot] avatar Nov 10 '25 16:11 netlify[bot]

[!IMPORTANT]

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
πŸ§ͺ Generate unit tests (beta)
  • [ ] Create PR with unit tests
  • [ ] Post copyable unit tests in a comment
  • [ ] Commit unit tests in branch bently/open-2299-name-of-downloaded-agent-in-library-is-different-from-name

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

coderabbitai[bot] avatar Nov 10 '25 16:11 coderabbitai[bot]

Here's the code health analysis summary for commits 9371528..b471475. View details on DeepSourceΒ β†—.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScriptβœ…Β SuccessView CheckΒ β†—
DeepSource Python LogoPythonβœ…Β SuccessView CheckΒ β†—

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

deepsource-io[bot] avatar Nov 10 '25 16:11 deepsource-io[bot]

Thank you for this PR that fixes agents downloaded from the marketplace showing the creator's graph name instead of the marketplace name in the user's library. The implementation approach looks solid!

A few notes:

  1. Your PR is well-documented, clearly explaining both the problem and solution.

  2. I notice that you mentioned "I still need to fully test this" and your test plan checkboxes aren't all checked. Please complete your testing before this PR can be merged:

    • Upload an agent to the marketplace with a custom name/description and verify it's stored correctly
    • Download that agent and verify the file name matches the agent name from the marketplace
  3. The schema changes look appropriate with good comments explaining the purpose of the new fields.

  4. The implementation logic in both db.py and model.py correctly implements the fallback pattern where the override fields take precedence if available.

Once you've completed your testing plan and checked those boxes, this PR should be ready for merging.

AutoGPT-Agent avatar Nov 11 '25 13:11 AutoGPT-Agent