Guides
Start here
- Update to the latest version. Many problems are already fixed in newer releases. For anything that involves your phone or another PC, the connected PC needs to be up to date as well.
- Read the error message carefully. The app gives different guidance depending on the cause.
Installing and updating
Windows shows a SmartScreen warning
You see this because the Windows installers don't have an Authenticode code signature yet. Make sure the file came from the official download page, then click More info → Run anyway. See Install and first run for more.
The Portable version doesn't update itself
Windows Portable can't install updates from inside the app. Download the new file from the download page and swap it in. If you want automatic updates, use the Setup version.
The app can't reach the update server
If the app can't reach the update address, it opens the releases page in your default browser. Download the installer from there. Updates don't need an account or access token.
You're not getting update notifications
- If you chose 나중에 (Later), you won't be reminded again for 4 hours while the app stays open.
- If you chose 이번 버전 건너뛰기 (Skip this version), you won't be notified about that version automatically.
- Check manually with the download icon at the top to see postponed and skipped versions again.
An update fails to install
The update window and the restart confirmation dialog show why it failed.
- macOS: If install verification hits an error or a 120-second timeout, you can try again.
- Linux .deb: An administrator authentication dialog should appear during install. If it doesn't show up within 3 minutes, the install stops and the app gives you a command to run in a terminal instead. You'll see different guidance depending on whether you canceled the dialog or the app couldn't get permission.
- Linux, when the app was launched from a sandboxed shell: The
NoNewPrivsrestriction can block privilege escalation. The app then opens an authentication dialog through your user systemd instance, and if that fails too, explains how to install withsudofrom a terminal outside the app.
Phone connection and QR codes
「연결 QR 만들기」 (Create connection QR) is grayed out
You can only create a QR code once the PC is connected to the relay server. Under 환경 설정 › 휴대폰 (Settings › Phone), check that 휴대폰 연결 켜기 (Turn on phone connection) is on and the status says connected.
You can't turn on phone connection
Phone connection needs the OS secure storage. If the PC can't use it, the option stays off, and the app won't fall back to storing anything in plain text. On Linux, turn on a keyring such as Secret Service and restart the app.
The QR code says it's expired or already used
Each QR code works once and expires after 5 minutes. Create a new one on your PC and connect again.
「연결 시도가 너무 잦습니다」 (Too many connection attempts)
When a connection fails authentication, the PC has the relay server block it for a short time (about a minute). Wait a minute, then try again with a new QR code.
「연결이 해제되었습니다」 (Disconnected)
This means the PC disconnected this phone or a new desktop identity was created. Create a new QR code on the PC and connect again. If you connected with a Google account, just allow it again in the PC's approval dialog.
The PC shows as off
Make sure the PC is on and Agent Switchboard is running. The connection comes back on its own once the PC is up.
The Android app only says 「네트워크 연결을 확인하세요」 (Check your network connection)
Android app 0.6.0 and later, signed with the release key, can only connect through a Google account to PC app 0.65.2 or later. Update the PC app.
「Google 계정을 확인하지 못했습니다」 (Couldn't verify your Google account)
If the PC's clock is behind, it may fail to verify the Google sign-in proof. PC app 0.65.3 fixed this for clocks that are only slightly off. Update the PC app and turn on automatic time sync in your OS.
The PC shows 「Google에 다시 로그인해 주세요」 (Please sign in to Google again)
The PC's Google sign-in has expired. Click Google 다시 로그인 (Sign in to Google again) under Settings › Phone. Until you do, no other device can make a new connection.
The Android app won't install
If you previously installed an APK signed with a different key, the new one can't install over it. Uninstall the old app, install the new APK, then reconnect to your PC and sign in with Google again.
Your PC list is empty after the web app moved
The phone web app now lives at https://app.switchboard.twentyoz.kr. Connection info from the old address doesn't carry over. Reconnect with a QR code, or if you were using a Google account, sign in again to load your PC list.
Keys and authentication
「저장 후 적용」 (Save and apply) is grayed out (Linux)
On a PC that can't use the OS secure storage (keyring), API keys can't be saved, and the reason appears above the button. Turn on a keyring and restart the app.
The model you picked isn't applied
Both the connection test and the apply step check that the model you picked actually works, and stop if it doesn't. Pick an available model from the list and try again.
The CLI fails with "credential is not configured"
This can happen if a CLI starts with an old launch profile after you changed the folder's connection. Apply that connection again in the tool settings and restart the CLI. If the folder still has its Codex settings but the folder connection profile has gone missing, the app rebuilds the profile from the saved settings.
"SECURE_STORAGE_BOOTSTRAP_FAILED" keeps coming back
- Make sure Agent Switchboard and every related process has exited.
- If a forced quit during setup left just the
.secure-storage-bootstrap.lockfile behind, copy that file somewhere safe, delete it, and start the app again. - Don't delete or edit the
Local Statefile or thecredentialsfolder. Leave the originals as they are and get in touch with us.
The app says it couldn't confirm support for a reasoning effort level
When support for a reasoning effort level can't be confirmed, the app sends the tool's default and tells you so. If this message stopped you from starting a chat in an older version, update the app.
On Windows, the OAuth sign-in window opens as an empty terminal
This was caused by a PowerShell startup profile blocking the sign-in command. Since 0.61.2, the sign-in window skips your startup profile. Update the app.
Contacting us
When you report a security issue, don't attach API keys, OAuth tokens, auth files, or whole settings files. Just send the connection address, your OS, the app version, steps to reproduce, and the error message with any sensitive values masked. Reach us at hello@twentyoz.kr.