Troubleshooting

What you see when a login, connection or setup step goes wrong, what to do, and the page that covers it.

Find what you see in the list below, do what it says, and open the linked page for the full steps.

Claude and Codex logins

What you seeWhat to do
Logins and models still shows Sign in after Claude said you are signed inPaste the long code Claude shows after Authorize into the Laze terminal and wait for Login successful. Signing in on Claude's page alone saves nothing. Logins and models
"That code did not work"Copy the whole code from Claude's page, including the part after #, and paste it again. Logins and models
"That code is from another sign-in"Press Open the sign-in page in the same terminal and use the code from that page. Logins and models
Claude opened its chat instead of a codePress Open the sign-in page again in the same browser and press Authorize. Logins and models
You have a 6-digit code from Claude's emailEnter it on Claude's page. Laze wants the long code shown after Authorize. Logins and models
"The sign-in did not finish"Press Start again for a new link or code. Logins and models
A login reads Signed out, or an agent says its login is signed outPress Sign in again on the login in Settings, Logins and models. Logins and models
An agent says all of its logins are out of usagePress Wait until on its card, or Add a login. Messages wait. Logins and models

Connected agents

What you seeWhat to do
The link token was refused, or "This link is not valid any more"A token works once, for 30 minutes. Make a new prompt in Connect your agent and paste that. Connect your agent
You added Laze as a custom connector in Claude, and your hosted agents still need a Claude loginThe connector makes Claude a connected agent that talks to Laze. It does not sign Laze's agents in. Sign in under Settings, Logins and models. Logins and models
Laze's page asks which workspace when you connect Claude or ChatGPTPick the workspace the agent should join and press Allow. To reconnect an agent you already have, pick Reconnect with its name: same agent, new key. Connect your agent
Claude has no way to add a custom connector on a Team or Enterprise planAn owner adds it under Organization settings first. Connect your agent
Messages do not reach Claude Code, Codex, ChatGPT or ClaudeFollow the checks at the end of the Connect your agent page. Connect your agent

Hosted agents and the computer

What you seeWhat to do
"Waiting for Scout to pick this up" stays for a whileThe agent's computer is waking up. Laze tries again on its own for about 3 minutes before it reports a problem. Agent computer
"Scout could not start, so your message has not run yet"Press Retry on the card. The message is kept. If the restart fails, use the support link on the card with its reference code. Hosted agents
"Laze computers are busy right now. Please try again in a minute."Press Retry in a minute. Agent computer
"Many people are starting at once" while signing inThe dialog keeps trying. Yes, let me know emails you when your computer is ready. Logins and models

Credits and billing

What you seeWhat to do
"Out of credits. Agents on Laze models wait until you top up."Press Top up and pay the amount in Stripe Checkout. Messages wait and the agents answer after the top-up. Credits and billing
"Credits are running low. Top up so agents on Laze models keep working."Top up, or turn on auto-recharge in Settings, Billing. Credits and billing
"Auto-recharge reached this month's limit."Press Raise monthly limit to $100, or set a higher Monthly limit and press Save auto-recharge. Owners, Admins and Billing members can. Credits and billing
The last recharge failed, or "The last auto-recharge was declined."Top up with another card. Credits and billing
"Enter an amount from 10 to 5,000." or "Top up at least 10 at a time."A top-up and each auto-recharge are 10 to 5,000. Credits and billing
"Only admins and Billing members can change this."Ask one of the people it names, or top up yourself: everyone can. Credits and billing
A new workspace pauses at a balance of 0Verify your email in Settings, Profile. Only an account's first workspace may spend down to -1. Credits and billing
The last Team payment failedPress Pay the invoice, or update the card in Manage billing. Credits and billing
An invitation waits for TeamPress Upgrade to Team in Settings, Billing. Free holds 2 people. Credits and billing

Apps

What you seeWhat to do
You don't have access to this appPress Ask for access, or Switch account if the app was shared with another of your accounts. Apps
A message shows a Laze app card with Ask for accessThe app was not shared with you. Press Ask for access; its Builders get a card in their feed. Apps

Desktop app sign-in

What you seeWhat to do
The app reads Finish in your browserThe app signs in through your default browser. Sign in there and the app picks it up. Open the browser again opens the same page.
This sign-in took too longPress Start again for a fresh link.
"The sign-in link expired or was used already"Press Start again in the app.
"This sign-in was not started in this window"Start again from the same app window you began in.

Slack, Discord and WhatsApp

What you seeWhat to do
"That Slack link expired" or "That Discord link expired"Start again from Settings, Slack, Discord and WhatsApp. Slack, Discord
"Slack refused the Client ID or Client Secret"Copy them again from the Slack app's Basic Information page. Slack
"Slack did not grant" some scopesAdd them under OAuth & Permissions in the Slack app, then install again. Slack
"Discord refused the Client Secret"Copy it again from the Discord app's OAuth2 page. Discord
"Your Discord account is not a member of that server"Link the Discord account you use in that server. Discord
You cannot connect Slack or DiscordAn admin connects the Slack workspace or Discord server first. Then you link your own account. Slack
WhatsApp reads Coming soonWhatsApp is not offered to your account yet.
"Linking stopped" or "WhatsApp could not be linked"Press Link WhatsApp again and scan the new QR code from WhatsApp, under Linked Devices, Link a Device.
New WhatsApp messages are lateLaze checks WhatsApp in short visits. Press Check WhatsApp now in WhatsApp's settings.
"Checks stopped: they failed every time for a week."Press Check WhatsApp now to start the checks again.

Gmail, Google and other connectors

What you seeWhat to do
A connector reads Reconnect needed, or a card reads "Gmail needs attention"Press Reconnect on the row in Connectors or on the card, and sign in with the same account.
Reconnect for more on GmailPress it so agents can archive, label, trash and unsubscribe. Until then they can still read, draft and send.
"You signed in as a different account than this connection uses"Reconnect with the account the connection already holds. To add another account, use Connect: it becomes a second connection.
"The browser that opened the sign-in is signed in to Laze as someone else, or not at all"Sign in to Laze in that browser as yourself, or connect from the Laze app, and start again.
"That connect link expired or was already used"Start the connection again.
After connecting from the desktop app, the browser shows a purple pagePress Back to Laze, or Continue on the web to stay in the browser.

Vault approvals

What you seeWhat to do
An agent waits for a keyA card waits for the person who decides, in the thread, the feed and as a phone push. Answer Allow, Allow for this agent or Deny. Vault and access
The request was denied without anyone answeringAn unanswered card is denied after 24 hours. Ask the agent to try again. Vault and access
A command from Claude Code or Codex waits on laze vault runApprove its card in your feed or in the app's Approvals. Vault from Claude Code and Codex

Laze CLI

What you seeWhat to do
laze login does not finishCheck that the browser shows the same code as the terminal and approve it. The code lasts 10 minutes; run laze login again for a new one. CLI reference
No browser on the machineMake a key under Settings, CLI and API keys and run laze login --token lz_.... CLI reference
npm says ENOVERSIONS or ETARGETAdd --min-release-age=0 to the install command. Connect your agent
The CLI needs a newer Node.jsInstall Node.js 22 or later. CLI reference

Still stuck? Write in #laze-support in your workspace with what you see, word for word.