feat(platform/library): Sort agents by "Last Executed"

[Pwuts]

• Fork of stale feat(platform/library): Allow sorting Agents by Last Execution Time #9871
• Resolves Order Agents in Library by "most recently ran" #9860

I'm re-creating #9871 because it isn't mergeable in its current state and I can't push changes to the author's fork.

Thanks @Keerthi421 for the initial implementation! :)

Changes 🏗️

• Add "Last Executed" sort option in Library
• Set lastExecuted as the default sort option in frontend and backend
• Improve LibrarySortMenu + useLibrarySortMenu implementations

TODO:

• Make the sort mechanism actually work. Prisma doesn't support sorting by fields of related entities.

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:
  • Go to /library
  • Default sort is "Last Executed"
  • "Last Executed" sort works
  • Other sort options still work

[netlify]

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

Name	Link
🔨 Latest commit	5f6cea2
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/68712042ada63e000869edc3

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	5f6cea2
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/68712042dc4fc2000772b199

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 9860 - PR Code Verified Compliant requirements: Order agents in library by "most recently ran" instead of last edit time Change default sorting from last edit to last execution time Requires further human verification: Count all executions, not just those manually triggered through GUI (requires testing to verify execution tracking works for all execution types)

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Complex Sorting The LAST_EXECUTED sorting implementation uses nested Prisma queries with cast operations that may have performance implications and could be fragile. The dual ordering fallback logic should be validated. elif sort_by == library_model.LibraryAgentSort.LAST_EXECUTED: # Sort by the most recent AgentGraph.Execution (startedAt) first. # If no executions exist, fall back to sorting by updatedAt. order_by = [ cast( prisma.types.LibraryAgentOrderByInput, {"AgentGraph": {"Executions": {"startedAt": "desc"}}}, ), {"updatedAt": "desc"}, ] Missing State The Select component uses defaultValue but doesn't maintain controlled state, which could lead to UI inconsistencies when the sort changes programmatically. <Select onValueChange={(value) => setLibrarySort(value as LibraryAgentSort)} defaultValue={defaultSort} >

[deepsource-io]

Here's the code health analysis summary for commits 4ffb99b..5f6cea2. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success	❗ 1 occurence introduced 🎯 1 occurence resolved	View Check ↗
Python	✅ Success		View Check ↗

---

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

[AutoGPT-Agent]

Thanks for contributing this PR to implement the "Last Executed" sort option for agents in the Library!

Your PR looks good overall - the implementation includes both frontend and backend changes needed to support this new sorting option, and the scope matches what's described in the title.

However, I noticed that while you've outlined a test plan, you haven't checked off the item indicating you've completed testing according to that plan. Could you please:

1. Complete the testing according to your outlined steps
2. Check off the relevant checklist item once testing is complete

Specifically, please verify that:

• Default sort is "Last Executed"
• "Last Executed" sort works correctly
• Other sort options still work as expected

Once you've completed testing and updated the checklist, this PR should be ready for review and merging. Thanks for your contribution!

[AutoGPT-Agent]

Thank you for your contribution! This is a useful addition to the library sorting functionality.

The implementation looks good overall, with proper handling of the new sort option in both frontend and backend. I particularly like the dual ordering approach for LAST_EXECUTED that falls back to updatedAt when no executions exist.

However, before we can merge this PR, could you please:

1. Complete the checklist by confirming you've tested the changes according to your test plan (check the box for "I have tested my changes according to the test plan")

2. Verify that:

   • Default sort is "Last Executed"
   • "Last Executed" sort works correctly
   • Other sort options still function as expected

Once you've completed the checklist indicating you've verified the functionality, this PR should be ready for final review and merging.

[AutoGPT-Agent]

Thanks for this contribution to improve the agent sorting functionality! The PR looks good overall, but there's one issue before we can merge:

Testing Completion

You've outlined a clear test plan, but it appears you haven't completed the testing yet - the checkboxes in your test plan are still unchecked. Please complete testing according to your plan and mark the checkboxes once verified.

Specifically, please test:

• Default sort is "Last Executed"
• "Last Executed" sort works properly
• Other sort options still work correctly

Once you've confirmed these items work as expected, please update the PR by checking those boxes.

Implementation Notes

The implementation looks solid:

• Backend changes properly handle the new sort option with appropriate fallback to updatedAt when no executions exist
• Frontend changes are consistent with the backend implementation
• Default sort option is correctly set in both frontend and backend

Just complete the testing and we should be good to go!

[Pwuts]

This doesn't actually work, because Prisma doesn't support this kind of sorting by attributes of related entities:

order_by = [
    {"AgentGraph": {"Executions": {"startedAt": "desc"}}},  # this is not supported
    {"updatedAt": "desc"},
]

Database error fetching library agents: Could not find field at `findManyLibraryAgent.orderBy.AgentGraph.Executions.startedAt`

[AutoGPT-Agent]

Thanks for working on this feature! Adding "Last Executed" sorting to the Library is a valuable improvement. I noticed a few items that need to be addressed before this can be merged:

1. Incomplete Implementation: You've noted in your TODO that the sort mechanism doesn't actually work yet because "Prisma doesn't support sorting by fields of related entities." This feature needs to be fully implemented before merging.

2. Uncompleted Testing: The testing section of your checklist remains unchecked, which means you haven't verified the functionality of your changes according to your test plan.

3. Implementation Questions: I notice you're trying to sort by AgentGraph.Executions.startedAt in the backend. Have you considered alternatives if Prisma doesn't directly support this? Perhaps:

   • Using a raw SQL query for this specific sort option
   • Adding a denormalized lastExecutedAt field to the LibraryAgent model
   • Implementing a post-query sort in the API layer

To move forward:

1. Complete the implementation so the sort functionality works correctly
2. Test the changes according to your test plan
3. Update the PR to indicate the implementation is complete and the tests have passed

Looking forward to seeing this feature completed!

[AutoGPT-Agent]

Thanks for your well-structured PR implementing the "Last Executed" sort option for agents in the library! A few notes:

1. You've clearly identified the implementation issue with a TODO item - Prisma not supporting sorting by fields of related entities. This needs to be resolved before merging.

2. I noticed you haven't checked off the testing part of your checklist, which aligns with your TODO note. Once you resolve the Prisma sorting issue, please test according to your plan and update the checklist.

3. The implementation looks good overall - you've added the new sort option consistently throughout the codebase (backend models, API definitions, frontend components).

4. Nice improvement with the getSortLabel implementation using an object lookup instead of a switch statement.

5. Good thinking on the fallback sort mechanism in the backend (falling back to updatedAt when no executions exist).

Please update the PR once you've solved the Prisma sorting limitation. You might need to consider alternative approaches like:

• Using a raw SQL query
• Adding a denormalized lastExecutedAt field to the LibraryAgent model
• Implementing the sorting in-memory if the result set is small enough

Looking forward to the completed implementation!