-
Notifications
You must be signed in to change notification settings - Fork 762
Open
Description
Problem
The desktop app currently assumes a local backend flow. That makes it harder to use the same T3 Code state across multiple machines or to point the desktop client at a backend that is already running elsewhere.
Proposal
Add a supported mode where the desktop app can connect to a remote T3 Code backend instead of always assuming a local one.
Why this would help
- lets a desktop client connect to an existing backend running on another machine
- improves continuity across laptop, desktop, phone, and web usage
- makes it easier to keep one shared session/state backend instead of treating each desktop app instance as isolated
Questions
- should remote backend support live behind an explicit opt-in desktop setting?
- what auth model would be expected for a remote desktop-to-backend connection?
- should the desktop app support switching between local and remote backends without restarting?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels