No Custom Fetch/Transport Seam for better-auth Infra HTTP Clients
Developers self-hosting the better-auth infra plugin cannot supply a custom fetch implementation for its internal apiUrl and kvUrl HTTP clients, forcing JWKS verification requests over the network even when the same key set already exists in-process. The underlying option types and connection resolver provide no way to pass through a custom transport, mirroring the same limitation reported for a sibling plugin.
Signal
Visibility
Sign in free to unlock the full scoring breakdown, root-cause analysis, and solution blueprint.
Sign up freeAlready have an account? Sign in
Deep Analysis
Root causes, cross-domain patterns, and opportunity mapping
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Solution Blueprint
Tech stack, MVP scope, go-to-market strategy, and competitive landscape
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Similar Problems
surfaced semanticallyBetter Auth Rate Limiting Incompatible with Cloudflare Edge Storage
Better Auth's rate limiting system assumes simple key-value storage patterns, making it incompatible with strongly consistent or coordination-based backends like Cloudflare Durable Objects. Developers building on edge runtimes (Cloudflare Workers) cannot implement reliable strict rate limiting because the library offers no pluggable storage adapter interface for this layer. This is a specific gap in one open-source library affecting a niche but growing segment of edge-deployed applications.
Kiro MCP Host Lacks Remote OAuth Support, Forcing Local Workarounds
Kiro cannot run the browser-based OAuth authorization-code flow required by official remote MCP servers such as Google Workspace's, while other hosts like Antigravity and Claude do support it. Power/plugin authors are forced to ship local stdio servers with manual one-time OAuth setup instead of pointing directly at first-party remote endpoints.
Custom auth query hook lacks revalidation and caching features
A custom auth query implementation lacks features like revalidation on focus, deduplication, and caching that mature query libraries provide.
Client Ignores Custom ANTHROPIC_BASE_URL for Self-Hosted Models
Users want a setting to point an AI client at a self-hosted or third-party model endpoint, but the app keeps using the default Anthropic URL even when the environment setting is changed. This blocks use of alternative hosted models.
AI Provider Plugins Lack Support for Region-Locked Dual-Host Endpoints
AI-provider integration plugins often hardcode a single regional API host, so a valid key issued for one region (such as mainland China vs. international) gets rejected as invalid when used against the other host, with no indication that endpoint mismatch, not the key, is the cause. This creates confusing failures for developers integrating vendors that operate separate regional account systems.
Problem descriptions, scores, analysis, and solution blueprints may be updated as new community data becomes available.