poc: Hono + Better Auth integration playground#450
Draft
nhyiramante1 wants to merge 2 commits into
Draft
Conversation
Proves Better Auth can be layered onto the Hono backend shape introduced in PR #448. All four milestones pass: server boots, Google OAuth completes, session verification works (cookie + Bearer), and the mock auth-gated SSE route works. Includes INTEGRATION.md mapping exactly how to add auth.ts, mount /api/auth/*, tighten CORS, and guard /api/openai/chat/completions in the PR #448 backend with minimal changes. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
A self-contained playground (playgrounds/better-auth-hono/) proving that Better Auth can be layered onto the Hono backend shape introduced in PR #448.
This does not modify any production code. No changes to backend/, frontend/, experiment/, or any deployment config.
Milestones - all passing
Why this matters for PR #448
PR #448 explicitly defers auth. This playground answers the follow-on question: when the team is ready to add auth to the Hono backend, what does that look like?
INTEGRATION.md maps the exact changes needed:
Not in scope
Logging, PostHog, Docker, real OpenAI calls, JWT plugin - PR #448 owns that territory.