Before submitting
Area
apps/desktop, desktop settings, and T3 Connect
Problem or use case
T3 Code currently requires me to remember to launch the desktop app manually after restarting or signing into my computer.
This is especially inconvenient when I use that computer as a T3 Connect environment. The machine may be online, but T3 Code and its backend are unavailable remotely until I manually open the app.
Proposed solution
Add a desktop setting such as Launch T3 Code at login.
When enabled, T3 Code should register itself with the operating system and start automatically when the user signs in.
The setting should be managed from inside T3 Code rather than requiring users to configure startup behavior separately through Windows, macOS, or Linux settings.
Expected behavior
- Add a clear Launch at login toggle in desktop settings.
- Keep the setting synchronized with the operating system's actual login-item state.
- Support the desktop platforms T3 Code officially supports.
- Allow T3 Code's backend and T3 Connect environment to become available automatically after login.
- If tray/background support exists, allow startup without forcing the main window to appear.
- Disabling the setting should remove the corresponding login item cleanly.
- Surface an actionable error if the operating system prevents the setting from being applied.
Why this matters
For users who rely on T3 Connect, T3 Code behaves partly like a background service. Automatic startup makes remote access dependable after reboots and removes an easy-to-forget manual step.
It also makes the desktop app feel consistent with other communication, synchronization, and remote-access tools that can start automatically.
Smallest useful scope
A first version could provide one cross-platform Launch at login toggle and start T3 Code normally. Starting minimized or hidden could be added alongside system-tray support.
Related request
System tray or menu-bar presence would complement this feature by making it clear that T3 Code is running in the background and by allowing launch-at-login without opening a full window.
Before submitting
Area
apps/desktop, desktop settings, and T3 ConnectProblem or use case
T3 Code currently requires me to remember to launch the desktop app manually after restarting or signing into my computer.
This is especially inconvenient when I use that computer as a T3 Connect environment. The machine may be online, but T3 Code and its backend are unavailable remotely until I manually open the app.
Proposed solution
Add a desktop setting such as Launch T3 Code at login.
When enabled, T3 Code should register itself with the operating system and start automatically when the user signs in.
The setting should be managed from inside T3 Code rather than requiring users to configure startup behavior separately through Windows, macOS, or Linux settings.
Expected behavior
Why this matters
For users who rely on T3 Connect, T3 Code behaves partly like a background service. Automatic startup makes remote access dependable after reboots and removes an easy-to-forget manual step.
It also makes the desktop app feel consistent with other communication, synchronization, and remote-access tools that can start automatically.
Smallest useful scope
A first version could provide one cross-platform Launch at login toggle and start T3 Code normally. Starting minimized or hidden could be added alongside system-tray support.
Related request
System tray or menu-bar presence would complement this feature by making it clear that T3 Code is running in the background and by allowing launch-at-login without opening a full window.