Fix setup and sign-in problems

Match the message below to the one in Voyager. If the app opens, Settings → Accounts is the place to check your connections.

​

Complete signing in on the web

Voyager is waiting for the browser sign-in to finish.

1. Switch to the browser window opened by Voyager and finish signing in or creating your account.
2. If the page did not open, choose Reopen sign-in in Voyager.
3. Finish the browser flow on the same computer, then return to Voyager.
4. If you are asked to Choose a workspace, select the workspace you want to use.

Check: Voyager shows your account and lets you continue setup. Still stuck: Tell support whether the browser reported success and what Voyager shows afterward. Do not send the sign-in URL.

​

Voyager login timed out. Try connecting again.

The browser sign-in did not finish before the attempt expired.

1. Close the old sign-in tab.
2. Start a fresh sign-in from Voyager. In Settings → Accounts, use Sign in or Sign in again.
3. Complete the newest browser attempt, then choose a workspace if requested.

The messages The workspace choice timed out. Sign in again. and That workspace choice expired. Sign in again. need the same fix. Check: The Voyager card shows your account and workspace rather than a waiting message. Still stuck: Send the exact error and approximate time of the failed attempt to support.

​

Connect at least one agent to continue.

Voyager is signed in, but no chat agent is ready yet.

1. In Connect providers, connect Claude or ChatGPT, or set up Voyager models.
2. Finish the installation or sign-in requested by that row. If Voyager opens an installation terminal, press Enter to run the command shown and wait for it to finish.
3. Return to the setup screen and wait for the connection to be detected.

A paid Voyager plan is optional. Your own Claude or ChatGPT, signed in with a subscription or an API key, lets you finish setup. A media key alone does not connect a chat agent. Check: Continue becomes available. Still stuck: Send support the status shown next to the agent you connected and any installation error.

​

Voyager could not use your system’s secure storage. Unlock it and try again.

Voyager cannot read or save the credentials it needs. Check: The account no longer shows Credential storage unavailable. Still stuck: Send support the complete error and your operating system. Do not delete your saved profile to repair a sign-in.

​

Windows Smart App Control blocked Voyager’s credential storage component.

Windows has blocked part of the app; repeating sign-in will not remove that block.

1. Read the Windows Smart App Control guide for the Windows alpha.
2. If the message says A Windows Application Control policy blocked Voyager’s credential storage component., ask the administrator of the PC whether Voyager can be allowed.
3. Once the block has been resolved, reopen Voyager and try sign-in again.

Check: Voyager can save the sign-in without the same block message. Still stuck: Send support the exact Windows message and whether the PC is managed by your organization. Reinstalling the same blocked build does not change the policy.

​

Still connecting

Voyager has not been able to finish opening the workspace.

1. Choose Reload on the recovery screen.
2. If it returns, quit and reopen Voyager.
3. If startup fails with a dialog, follow Voyager could not start its local server. below.

Check: Your chats or the setup screen appear. Still stuck: Send support a screenshot of the recovery screen and your app version.

​

Could not read settings

Voyager could not load your saved settings.

1. Choose Retry.
2. If the same message returns, quit and reopen Voyager.
3. Contact support before deleting or resetting your profile.

Check: Settings and the main app open normally. Still stuck: Include the exact message and whether it began after an update, a restart, or a settings change.

​

Voyager could not start its local server.

Voyager could not open the local workspace it needs to run.

1. Read the details in the dialog and choose Try Again once.
2. If it fails again, choose Open Profile Folder to locate the saved data and the logs named in the dialog.
3. If Repair and Start is offered, read the repair confirmation before deciding whether to continue.

Check: Voyager opens and your expected chats are visible. Check your project folders separately if repair could not recover the app’s history. Still stuck: Email support@voyager.so with the dialog details and relevant logs. Do not send your entire profile unless support specifically asks for it.

​

ChatGPT usage limit reached

The selected ChatGPT account has reached a usage limit for Voyager.

1. Choose Manage usage and review that account’s usage and credit settings in ChatGPT.
2. Wait for available usage or make the change offered by ChatGPT.
3. Try the chat again, or deliberately choose another connected account or model.

Check: The next request completes using the account you selected. Voyager does not automatically retry this chat error with another payer. Still stuck: Use Get help… from the affected chat and include the account and model names.

​

Reconnect your ChatGPT account

Voyager needs a renewed sign-in for the ChatGPT account selected in this chat.

1. Open Settings → Accounts and select that ChatGPT account.
2. Choose Reconnect account and finish the browser flow.
3. If the browser does not return to Voyager, follow the sign-in panel’s instruction to paste the final page address there. Keep that address private.

Check: The account shows Signed in as with the expected account, and the chat can continue. Still stuck: Send the connection error through Get help… without including the sign-in address.

​

ChatGPT didn’t allow this request

Voyager’s access to your ChatGPT plan does not cover this request.

1. Choose another available model or account in the model picker.
2. Send the request using that selection. Signing in again does not change this permission.

Check: The request runs on your chosen model. Switching providers can continue in a new chat. Still stuck: Include the refused model and the full message in Get help….

​

ChatGPT plan unavailable for this account

The account, workspace, or its policy does not currently allow this use of the ChatGPT plan.

1. Check that you selected the intended ChatGPT account.
2. Choose another connected agent account to continue. If the message specifically suggests your existing Codex CLI, follow Connect ChatGPT to use that connection.

Check: The request runs using an available account. This message does not by itself mean your saved sign-in was lost. Still stuck: Send the full message, account type, and selected model through Get help….

​

A model is missing

The account’s model list depends on its plan, connection, installed version, and your display settings.

1. In Settings → Accounts, confirm the intended account is enabled and signed in.
2. Turn on Show advanced model choices if you need the full model list.
3. In the model picker, click Not seeing the models you expect? to open Model troubleshooting. Each account shows its status. If an account is out of date, click its Update to … button (or Copy update command and run it). Otherwise click Open in Accounts to check that account’s sign-in and plan.
4. Choose Check again after changing the connection or updating.

Check: The model appears under the intended account in the picker. Check the account before sending: the same model available through Voyager can use Voyager credits. Still stuck: Send support the missing model name, account type, and the status shown on Model troubleshooting.