Skip to content

[codex] Add MCP-backed graph dashboard auth flow#320

Draft
elysemukamisha wants to merge 2 commits into
NateBJones-Projects:mainfrom
elysemukamisha:codex-open-brain-dashboard-auth-graph
Draft

[codex] Add MCP-backed graph dashboard auth flow#320
elysemukamisha wants to merge 2 commits into
NateBJones-Projects:mainfrom
elysemukamisha:codex-open-brain-dashboard-auth-graph

Conversation

@elysemukamisha
Copy link
Copy Markdown

What changed

  • added an MCP-backed graph experience to the Next dashboard, including graph routes, search, and the Graph explorer UI
  • rewired dashboard data access away from the missing open-brain-rest function and onto the deployed MCP-backed endpoints
  • replaced direct MCP-key login with Supabase Auth plumbing, including email/password plus Google and GitHub OAuth entry points and the auth callback flow
  • updated dashboard pages that depended on the old REST API so thoughts and related views work in MCP mode

Why

The deployed project does not expose the REST function this dashboard was originally built against, which caused 404 failures across login, dashboard, and thoughts flows. This PR moves the dashboard onto the backend that actually exists and adds the graph view the project wanted.

Impact

  • dashboard and thoughts load against the live MCP-backed backend instead of failing on missing REST endpoints
  • graph view is available in the sidebar and thought flow
  • login UI supports Supabase Auth-based sign-in flows instead of asking end users for the MCP access key

Validation

  • npm run lint
  • npx tsc --noEmit
  • verified local and deployed dashboard routes during implementation

Notes

  • GitHub and Google OAuth still require those providers to be enabled in the Supabase project before the social buttons can complete sign-in

@github-actions github-actions Bot added the dashboard Contribution: frontend template label May 18, 2026
@github-actions
Copy link
Copy Markdown

Hey @elysemukamisha — welcome to Open Brain Source! 👋

Thanks for submitting your first PR. The automated review will run shortly and check things like metadata, folder structure, and README completeness. If anything needs fixing, the review comment will tell you exactly what.

Once the automated checks pass, a human admin will review for quality and clarity. Expect a response within a few days.

If you have questions, check out CONTRIBUTING.md or open an issue.

@alanshurafa alanshurafa added area: dashboard Review area: dashboard/frontend risk: auth-security Touches auth, secrets, permissions, or security-sensitive behavior alan-reviewed Reviewed by Alan Shurafa in Community Reviewer role labels May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

alan-reviewed Reviewed by Alan Shurafa in Community Reviewer role area: dashboard Review area: dashboard/frontend dashboard Contribution: frontend template risk: auth-security Touches auth, secrets, permissions, or security-sensitive behavior

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants