Refactor dashboard to dedicated pages for connections, settings, and API keys

[zonlabs]

Motivation

• Move the single monolithic dashboard UI into per-route pages to follow Next.js app routing best practices and make individual dashboard sections addressable by URL.
• Provide clear dedicated pages for connection management, per-connection settings, and gateway LLM API key management for improved navigation and bookmarking.

Description

• Extracted the workspace UI into app/dashboard/app/dashboard/connections/page.tsx so the connections UI lives on /dashboard/connections and retains the original client behavior and components.
• Changed app/dashboard/app/dashboard/page.tsx to redirect to /dashboard/connections to make /dashboard an entrypoint that routes to the connections page.
• Added app/dashboard/app/dashboard/api-keys/page.tsx which renders LLMKeySettings with a page header to expose /dashboard/api-keys for gateway API key management.
• Simplified the dynamic settings route in app/dashboard/app/dashboard/settings/[...id]/page.tsx to read the first path segment and render ConnectionSettings, and updated the connections view to use router.push('/dashboard/settings/{id}') and router.push('/dashboard/api-keys') for navigation instead of in-page tab-only state.

Testing

• Ran targeted ESLint on the new route files with pnpm -s exec eslint app/dashboard/page.tsx app/dashboard/api-keys/page.tsx app/dashboard/settings/[...id]/page.tsx which passed for those files.
• Running pnpm -s exec eslint app/dashboard/connections/page.tsx surfaced pre-existing lint errors (legacy any types and other client-page issues) which are unrelated to the routing refactor and remain to be addressed separately.
• Attempted full pnpm -s lint which failed due to existing repository lint rules across multiple files (not introduced by this refactor).
• Started the dev server with pnpm dev --port 3005 and exercised the /dashboard route via an automated Playwright script which produced a screenshot showing the redirected routing flow, though local Supabase env vars were not present in this environment (middleware reported missing SUPABASE values).

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
linkos	Ready	Preview, Comment	Feb 22, 2026 10:48am

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.