Architecture: Should developer-focused routes (control-center, agent mesh,...

Documentation for Sessions

🏗️ Architecture: Should developer-focused routes (control-center, agent mesh,...

Date: 2026-02-17
Time: 23:12:11 UTC
Session: gspace1-113.5
Agent: angular
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

Should developer-focused routes (control-center, agent mesh, platform intelligence, cursor agents, space assistants) stay in gograb-admin or move to gograb-dev?

Task: Session 114: Route migration admin to dev

🎯 Decision Made

Chosen:

Move all 5 developer routes and their mind sub-routes to gograb-dev, remove from gograb-admin

Options Considered:

Keep all in gograb-admin
Move all to gograb-dev
Duplicate in both apps

💭 Reasoning

gograb-admin is for business admins (usage, billing, users, spaces, modules). Developer tools like agent control center, mesh visualization, cursor agent management, and platform intelligence belong in gograb-dev which is purpose-built for developer workflows. Components live in shared @libs-ai/* libraries, so routes are just configuration. This gives admins a cleaner interface focused on business operations.

📁 Files Involved

apps/gograb-admin/src/app/app.routes.ts
apps/gograb-dev/src/app/app.routes.ts
apps/gograb-dev/src/app/app.ts
apps/gograb-admin/src/app/core/layout/admin-main-shell/admin-main-shell.component.ts

🔗 Related

Decision ID: dev_1771369931637_fv0xrz8
Session: 113
Workspace: gspace1

Auto-generated by MCP Smart Consolidation