Applications list page (/apps) with route drill-down #54

New Issue

claude · 2026-03-14T21:37:09+01:00

claude commented

2026-03-14 21:37:09 +01:00

Context

The plan identifies /apps as a Phase 2 entry point for browsing applications and their routes. Currently the only way to reach the route diagram page is via Ctrl+Click from ExecutionExplorer or direct URL.

What's needed

GET /apps page listing all unique application groups from the agent registry
Each group card shows: group name, agent count, route count, live/stale status
Clicking a group drills down to a routes list for that application
Each route links to /apps/{group}/routes/{routeId}
Add "Apps" nav link to TopNav

URL scheme

/apps                              — application list
/apps/{group}                      — routes list for an application
/apps/{group}/routes/{routeId}     — route detail (already exists)

## Context The plan identifies `/apps` as a Phase 2 entry point for browsing applications and their routes. Currently the only way to reach the route diagram page is via Ctrl+Click from ExecutionExplorer or direct URL. ## What's needed - `GET /apps` page listing all unique application groups from the agent registry - Each group card shows: group name, agent count, route count, live/stale status - Clicking a group drills down to a routes list for that application - Each route links to `/apps/{group}/routes/{routeId}` - Add "Apps" nav link to TopNav ## URL scheme ``` /apps — application list /apps/{group} — routes list for an application /apps/{group}/routes/{routeId} — route detail (already exists) ```

claude added the feature ui labels 2026-03-14 21:40:27 +01:00

claude referenced this issue

2026-03-14 22:34:42 +01:00

UX overhaul: streamline navigation from search results to route diagram #69

claude commented

2026-03-14 22:34:51 +01:00

This is now Phase 4 of the UX navigation overhaul (#69).

The /apps page is critical for making route diagrams discoverable without going through the search-first flow. Users need a topology-first entry point.

Updated scope — the Applications page should:

List all known groups (from agent registry)
Under each group, list routes with their diagrams
Clicking a route navigates to RoutePage without ?exec= (diagram-only mode)
Show route health indicators (success rate, throughput) inline
TopNav gets an "Applications" link pointing here

This is now Phase 4 of the UX navigation overhaul (#69). The `/apps` page is critical for making route diagrams discoverable without going through the search-first flow. Users need a topology-first entry point. **Updated scope** — the Applications page should: 1. List all known groups (from agent registry) 2. Under each group, list routes with their diagrams 3. Clicking a route navigates to `RoutePage` without `?exec=` (diagram-only mode) 4. Show route health indicators (success rate, throughput) inline 5. TopNav gets an "Applications" link pointing here

claude commented

2026-03-15 10:12:59 +01:00

Terminology clarification: The /apps page lists applications (groups), not individual agent instances.

A group is the application name (e.g. order-service-eu) — all instances of the same Camel app
An agentId is one running instance of that application

So the hierarchy is:

/apps
  └── order-service-eu        (group = application)
        ├── content-based-routing    (route)
        ├── order-validation         (route)
        └── ...
  └── payment-gateway
        └── ...

Each application card could show instance count (e.g. "3 instances") as secondary info.

**Terminology clarification**: The `/apps` page lists **applications** (groups), not individual agent instances. - A **group** is the application name (e.g. `order-service-eu`) — all instances of the same Camel app - An **agentId** is one running instance of that application So the hierarchy is: ``` /apps └── order-service-eu (group = application) ├── content-based-routing (route) ├── order-validation (route) └── ... └── payment-gateway └── ... ``` Each application card could show instance count (e.g. "3 instances") as secondary info.

claude closed this issue

2026-04-01 22:23:56 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cameleer/cameleer-server#54