Adopt unified endpoint format in UI and environment variables

[Copilot]

Updates UI code examples and environment variable displays to use the unified endpoint format https://namespace:token@endpoint instead of separate RIVET_ENDPOINT, RIVET_NAMESPACE, and RIVET_TOKEN variables. Maintains full backward compatibility with existing separate variable format.

Changes

UI Code Examples (publishable-token-code-group.tsx)

• Code examples now generate unified endpoint URLs with embedded credentials
• Extracted URL construction into shared createUnifiedEndpoint() utility

Environment Variables (env-variables.tsx)

• New RivetEndpointEnvUnified component displays unified format by default
• Added unified prop (default: true) to toggle between formats

Frontend Dialogs (tokens-frame.tsx, tokens.tsx)

• Updated tokens dialog to display unified format in environment variable displays
• Updated Secret Token section on tokens page to show unified format
• Copy buttons now copy unified endpoint format

Documentation

• Updated connect-backend.mdx to document both unified and separate formats with examples
• Clarifies RIVET_ENGINE (legacy, endpoint-only) vs RIVET_ENDPOINT (supports unified format)
• Updated all deployment guides (Kubernetes, AWS ECS, GCP Cloud Run, VM/Bare Metal) to show unified format as recommended option
• Updated AI actors guide and React client documentation to note unified format support

Example

Before:

createClient<typeof registry>({
  endpoint: "https://api.rivet.dev",
  namespace: "my-namespace",
  token: "pub_abc123",
});

After:

createClient<typeof registry>({
  endpoint: "https://my-namespace:pub_abc123@api.rivet.dev",
});

Both formats are supported by the existing endpoint parser. All deployment documentation and UI displays now present the unified format as the recommended approach while maintaining backward compatibility examples.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[linear]

FRONT-904 Adopt unified config/token endpoint in UI and env vars

[vercel]

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

Project	Deployment	Review	Updated (UTC)
rivet-inspector	Ready	Preview, Comment	Jan 5, 2026 2:36pm

3 Skipped Deployments

Project	Deployment	Review	Updated (UTC)
rivet-cloud	Ignored		Jan 5, 2026 2:36pm
rivet-site	Ignored	Preview	Jan 5, 2026 2:36pm
rivetkit-serverless	Skipped		Jan 5, 2026 2:36pm

[jog1t]

@copilot pls check also all the docs in website if they need an update

[jog1t]

@copilot pls remove this file

[Copilot]

Done in f57fc58. Removed the UNIFIED_ENDPOINT_ROLLOUT.md file.

[Copilot]

@copilot pls check also all the docs in website if they need an update

Done in f57fc58. Updated all deployment documentation in the website:

• Kubernetes - Shows unified and separate formats in secrets
• AWS ECS - Shows both formats in task definitions
• GCP Cloud Run - Shows both formats in deployment commands
• VM/Bare Metal - Shows both formats in systemd services
• AI Actors - Added comments noting both formats work
• React Clients - Notes unified format support in endpoint parameter

All guides now present the unified endpoint format as the recommended approach while maintaining backward compatibility examples.

[jog1t]

amazing, @copilot pls make sure that internal docs also includes this change, double check if all code in the "frontend" folder contains this change.

[Copilot]

amazing, @copilot pls make sure that internal docs also includes this change, double check if all code in the "frontend" folder contains this change.

Done in 45491a8. Completed comprehensive review of frontend folder and internal docs:

Frontend Updates:

• ✅ env-variables.tsx - Unified format by default
• ✅ publishable-token-code-group.tsx - Code examples use unified format
• ✅ tokens-frame.tsx - Dialog displays unified format
• ✅ tokens.tsx - Page shows unified format in Secret Token section

Notes:

• Railway/Vercel template links kept as separate vars (external services require query params)
• Inspector data provider uses different API pattern (url/token)
• No env var references found in main README.md or CLAUDE.md

All user-facing environment variable displays in the frontend now use the unified endpoint format.