[Agent Builder] New navigation foundation#257858
[Agent Builder] New navigation foundation#257858chrisbmar merged 13 commits intoelastic:ab-agent-centric-ux-feature-branchfrom
Conversation
| @@ -0,0 +1,54 @@ | |||
| /* | |||
There was a problem hiding this comment.
This component will be deleted entirely when the migration is complete. Right now, this renders for every route. When every route has been successfully migrated, this won't be imported by any route anymore and can be deleted.
| @@ -0,0 +1,56 @@ | |||
| /* | |||
There was a problem hiding this comment.
We have 1 unified sidebar so the content can be changed inside of it with a nice transition to be defined by design.
| @@ -0,0 +1,198 @@ | |||
| /* | |||
There was a problem hiding this comment.
This file is new. It centralises routes, navLabels, and isExperimental in a single definition. It makes it easy for making any updates in future, either add a new object or edit an existing one - in one place!
There was a problem hiding this comment.
It was surprising to me that we didn't use RBAC to guard against rendering specific routes in production today. If a user doesn't have manageAgents I'm surprised that we still render /manage/agents
| { | ||
| path: '/agents/:agentId/conversations/:conversationId', | ||
| sidebarView: 'conversation', | ||
| element: <RouteDisplay />, |
There was a problem hiding this comment.
Notice that we render RouteDisplay for every route. This is to help with the migration aspect of realising once we have successfully migrated every route - at that point, we can delete this component entirely. Future PRs into the feature branch will handle the individual route migrations, it's out-of-scope for this PR.
| </Route> | ||
| </Routes> | ||
| return ( | ||
| <AppLayout> |
There was a problem hiding this comment.
AppLayout is new and contains the persisted sidebar on all routes.
|
The types failing in the CI check above are great! That's what will be handled in https://github.com/elastic/search-team/issues/13361 😄 but FYI this is being merged into the feature branch, so almost all branches that are going to get merged into the feature branch will have CI failing - this isn't cause for concern. |
⏳ Build in-progress, with failures
Failed CI Steps
Test Failures
History
cc @chrisbmar |
SiddharthMantri
left a comment
There was a problem hiding this comment.
LGTM overall. I expect things will change as we start using this as the base for the rest of the pages.
bc3d6a9
into
elastic:ab-agent-centric-ux-feature-branch
Summary
closes https://github.com/elastic/search-team/issues/13360
Introduces an agent-centric navigation structure for Agent Builder with a unified sidebar that adapts based on the current route.
Key changes:
route_config.tsxdefinition/agents/:agentId/*) with legacy URL redirects for backward compatibilityConversation Routes are now:
Agent Settings Routes:
Manage Routes (global CRUD, no agent context):
Redirects:
/→/agents/:lastAgentId(last used agent from local storage, or elastic-default)/conversations/new→ /agents/:lastAgentId/conversations/:id→ fetch conversation, get agent_id, redirect to/agents/:agentId/conversations/:idScreen.Recording.2026-03-13.at.16.48.25.mov