Feature request
Remote control (/rc) is per-session and stops when the session ends (laptop shutdown/restart). After boot, users must reopen a session and run /rc again before the Telegram/Discord bridge comes back. The Desktop app's Remote control status likewise resets to Off after relaunch.
Please consider an option to auto-reconnect /rc when the app or a session starts (or when a session is resumed). Credentials are already persisted in ~/.commandcode/auth.json, so the automatic reconnect is the only missing piece.
Environment
- Command Code CLI: v1.74.3
- OS: Windows
- Shell: cmd.exe
- Terminal: Windows Terminal
Reactions are currently unavailable
Feature request
Remote control (/rc) is per-session and stops when the session ends (laptop shutdown/restart). After boot, users must reopen a session and run /rc again before the Telegram/Discord bridge comes back. The Desktop app's Remote control status likewise resets to Off after relaunch.
Please consider an option to auto-reconnect /rc when the app or a session starts (or when a session is resumed). Credentials are already persisted in ~/.commandcode/auth.json, so the automatic reconnect is the only missing piece.
Environment