[CLEANUP] Remove Memory sections from UI following v1alpha2 API migration

[ashleywang1]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct
• I am using the latest version of the software
• I have tried to clear cache/cookies or used incognito mode (if ui-related)
• I can consistently reproduce this issue

🎯 Affected Service(s)

UI Service

🚦 Impact/Severity

Minor inconvenience

🐛 Bug Description

With the migration from v1alpha1 to v1alpha2 API, the Memory field has been completely removed from the AgentSpec. This means:

1. Agents can no longer be linked to Memory objects in the v1alpha2 API
2. The Memory resource type itself is no longer present in v1alpha2
3. The UI still contains Memory-related sections and pages that are now obsolete

🔄 Steps To Reproduce

1. Spin up the UI
2. Attempt to create an Agent linked to a Memory
3. See that the link never materializes and no error ever shows up anywhere

🤔 Expected Behavior

Required Changes

The following UI components need to be removed or updated:

1. Memory Pages/Routes

• Remove memory listing page (/memories)
• Remove memory creation page (/memories/new)
• Remove memory detail/edit pages

2. Agent Creation/Edit Forms

• Remove memory selection section from agent creation forms
• Remove memory configuration options from agent edit forms
• Update agent form validation to remove memory-related checks

3. Agent Display Components

• Remove memory references from agent detail views
• Remove memory status indicators from agent cards/lists
• Update agent tooltips/help text that mention memory

4. Navigation & Routing

• Remove memory-related navigation items
• Clean up routing configuration
• Update breadcrumbs and navigation flows

5. Types & Interfaces

• Update TypeScript interfaces to remove memory-related fields
• Clean up API client methods related to memory
• Remove memory-related actions and reducers

Acceptance Criteria

• All memory-related UI pages are removed
• Agent creation/editing no longer shows memory options
• Agent displays no longer reference memory objects
• Navigation is updated to remove memory links
• TypeScript types are cleaned up
• No broken links or dead code remains
• UI tests are updated accordingly

📱 Actual Behavior

No response

💻 Environment

No response

🔧 CLI Bug Report

No response

🔍 Additional Context

No one in the community discord seems to be using Memory, so these pages should be safe to remove.

This API change was a part of a larger migration to Google's ADK, which does have the concept of Memory, just not the RAG style memory we have in the v1alpha1 API.

📋 Logs

📷 Screenshots

No response

🙋 Are you willing to contribute?

• I am willing to submit a PR to fix this issue

[tanuj-rai]

Hey @ashleywang1, can I work on this issue?

[ashleywang1]

Hey @ashleywang1, can I work on this issue?

Go for it!

[tanuj-rai]

Hi @ashleywang1. I have opened a PR for this issue. Please take a look at it when you have time and let me know if anything needs to be updated.