feat(rivetkit): allow defining public namespace & token for client redirects via metadata endpoint

[NathanFlurry]

No description provided.

[railway-app]

🚅 Deployed to the rivet-pr-3891 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
frontend-inspector	😴 Sleeping (View Logs)	Web	Jan 14, 2026 at 8:46 am
website	😴 Sleeping (View Logs)	Web	Jan 14, 2026 at 8:46 am
frontend-cloud	😴 Sleeping (View Logs)	Web	Jan 14, 2026 at 8:45 am

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• doc: update railway integration guide for serverless #3897
• doc: configuring rivet endpoints #3895
• chore(rivetkit): validate incoming serverless request endpoint/namespace #3894
• chore(rivetkit): update welcome message #3893
• feat(rivetkit): allow defining public namespace & token for client redirects via metadata endpoint #3891 👈 (View in Graphite)
• chore(engine): provide detailed error for invalid serverless sse event #3881 : 1 other dependent PR (#3890 )
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

PR Review: feat(rivetkit): allow defining public namespace & token for client redirects via metadata endpoint

Overview

This PR enhances RivetKit's configuration system to support specifying public namespace and token credentials for client redirects through the metadata endpoint. The changes introduce cleaner URL-based auth syntax and better separation between backend and frontend credentials.

Positive Aspects

1. Well-Structured Configuration Flow

The refactoring significantly improves how endpoint parsing and configuration resolution works:

• Centralized endpoint parsing logic in tryParseEndpoint
• Clear separation between backend connection config and public client config
• Proper use of Zod transforms and refinement context for validation

2. Comprehensive URL Auth Support

The URL auth syntax is consistently supported across RIVET_ENDPOINT and RIVET_PUBLIC_ENDPOINT with proper handling of percent-encoded characters.

3. Good Documentation

• Clear JSDoc comments explaining config options
• Updated documentation in connect-backend.mdx with examples
• Comments explaining validation logic

4. Test Coverage

The endpoint parser tests are comprehensive covering basic parsing, error cases, duplicate credential detection, and edge cases.

Issues & Concerns

1. Critical: Potential Configuration Confusion

In registry/config/index.ts:214, the serveManager default logic could leave clients without a valid endpoint in edge cases. Add validation to ensure that if serveManager is false and not in dev mode, either endpoint or publicEndpoint must be specified.

2. Medium: Error Message Quality

In registry/config/index.ts:207-210, error messages for namespace mismatch could be more actionable with guidance on how to fix the issue.

3. Medium: Inconsistent Default Handling

Client and registry configs have different default endpoint logic that could cause confusion. Client uses window.location.origin while registry uses hardcoded localhost. Consider consolidating or documenting the differences.

4. Minor Issues

• Comment clarity in runtime/index.ts:85-89 about unreachable code could be improved
• Could combine duplicate credential errors in tryParseEndpoint for clarity
• Type safety improvements possible in api-utils.ts getEndpoint function

5. Documentation Typo

In connect-backend.mdx:3 - exlpicitly should be explicitly

Security Considerations

Good practices: No credential logging and proper URL encoding handling.

Important consideration: The metadata endpoint now returns clientToken. Add documentation clarifying that publicToken should be a limited-privilege token suitable for public exposure, not the backends privileged token.

Testing Recommendations

1. Add integration tests for client connection flow with URL-embedded credentials
2. Test default behaviors in dev vs prod mode
3. Test namespace validation between public and private endpoints

Summary

This is a solid PR that improves RivetKits configuration flexibility. The core implementation is sound with good structure and test coverage.

Recommendation: Approve with minor changes

The PR is functionally correct and safe to merge, but would benefit from:

• Adding validation for serveManager/publicEndpoint edge cases
• Improving error messages
• Adding security documentation for clientToken/publicToken
• Fixing the documentation typo

Suggested Follow-ups:

1. Add integration tests for metadata endpoint flow
2. Consolidate default endpoint logic between client and registry configs
3. Create configuration flow diagram
4. Consider removing getEndpoint per TODO in api-utils.ts

[pkg-pr-new]

More templates

• actor-actions
• example-ai-agent
• example-ai-and-user-generated-actors-freestyle
• chat-room
• example-cloudflare-workers
• example-cloudflare-workers-hono
• example-cloudflare-workers-inline-client
• cross-actor-actions
• example-cursors
• example-cursors-raw-websocket
• custom-serverless
• example-sqlite
• example-elysia
• example-experimental-durable-streams-ai-agent
• hello-world
• example-hono
• hono-react
• example-kitchen-sink
• multi-region
• native-websockets
• next-js
• example-raw-fetch-handler
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-react
• scheduling
• state
• example-stream
• example-trpc

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@3891

@rivetkit/db

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/db@3891

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@3891

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@3891

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@3891

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@3891

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@3891

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@3891

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@3891

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@3891

commit: a53dc0f

[graphite-app]

Merge activity

• Jan 14, 8:52 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Jan 14, 8:52 PM UTC: CI is running for this pull request on a draft pull request (#3898) due to your merge queue CI optimization settings.
• Jan 14, 8:53 PM UTC: Merged by the Graphite merge queue via draft PR: #3898.