"Your access to HQ as a@agency.com ended on this computer. Sign in again, or switch to another account."
That account was removed in HQ, or its access ended. Sign in again, or switch to another account.
"Too many HQ sign-ins were started from this network. Wait a minute and try again."
Wait a minute, then sign in again.
More than one account
Message
What to do
"Signed in to AI Workforce One HQ as owner@client.com. This window now uses it."
Not an error: the account was added and this window uses it.
"The browser approved this sign-in as a@agency.com, who is already signed in here, so it was not kept. To add another account, sign in to HQ in your browser as that account first."
The browser was signed in as an account you already have here. Sign the browser in as the account to add (or use a private window), then add it again.
A renewal was approved as another account; that approval was ended. Sign the browser in as a@agency.com and sign in again.
"HQ could not be reached to undo that sign-in. Remove the newest computer in HQ, under Account, Devices."
The extension could not end an approval it did not keep. Remove the newest entry in HQ, under Account, Devices.
"This sign-in could not be stored: another VS Code profile on this computer holds one for the same account. It was not kept."
Sign in again. If it repeats, email support.
"Sign out of a@agency.com? Its HQ terminals and port forwards close in every window."
Not an error: confirm to sign out of that account only.
"Signed out of a@agency.com. Other accounts stay signed in."
Not an error: only that account was signed out.
"You have other HQ accounts signed in on this computer."
This window's account was signed out. Press Switch Account or Add Another Account.
"Could not read your HQ sign-in for a@agency.com from the keychain. Unlock it and try again."
Unlock your system keychain, then try again. Nothing was signed out.
An account says "Sign in again" in the Account view
Its sign-in cannot be used on this computer. Click it and approve as that account.
"... is not an HQ address this editor may use. ..."
Set hq.host back to https://hq.aiworkforceone.com.
"The HQ address changed. Sign in again to use it."
hq.host changed. Sign in again.
"Your HQ sign-in is stored without the system keychain on this computer."
Not an error. On Linux, start a keyring (for example GNOME Keyring or KWallet) and sign in again if you prefer the keychain.
"This version of AI Workforce One HQ is no longer supported. Update it from the Extensions view."
Update the extension.
"HQ could not be reached. Check your connection and try again."
Check your network, then try again.
Teams and sessions
Message
What to do
A team shows off
Its AI Team Cloud Computer is not running. Press Wake Team, or open one of its sessions and press a key.
A team shows update needed
Its Cloud Computer needs an update for the extension. A team owner (or an organization owner or admin) presses Update Cloud Computer in HQ, under the team's Settings.
A team or session shows view only
You have viewer access to the team, or the session is someone else's. You can watch but not type or save.
"Could not load sessions"
Run HQ: Refresh. If it repeats, open the team in HQ.
"Backend team did not start within 3 minutes. Check it in HQ and try again." (4 minutes on the sizes from 80 GB)
Open the team in HQ to see its state, then try again.
"Backend team is stopped. Wake only resumes a sleeping team: start a session to start its Cloud Computer."
Press Start a Session in that message (or start one in HQ). Wake Team only resumes a team that went to sleep.
"Too many wake requests for this team. Wait a few minutes and try again."
Wait a few minutes.
"This team is at its session limit. Stop a session in HQ, then try again."
Stop a session you no longer need.
"Could not start a session: This AI Team's Cloud Computer is busy right now, so another session could not start. Stop a session you no longer need, or move the team to a bigger size, then try again."
The team's Cloud Computer is too busy for another session. Stop a session you no longer need, or ask an owner to give the team a bigger size.
"Your plan is read-only. Reactivate billing in HQ to save files or start sessions."
An owner updates billing in HQ. Reading still works.
"You can view this team but not start sessions on it."
You need editor or owner access to start a session.
Terminals
Message
What to do
"Backend team is off." / "Press any key to wake it."
Press a key to wake the Cloud Computer.
"Connection lost, reconnecting..."
Progress: the terminal reconnects on its own.
"The connection to HQ was lost." and "Press any key to reconnect."
Press a key in the terminal; it reconnects in the same tab. Opening the session again from the HQ panel also gives a fresh terminal.
"You can watch this session but not type in it."
Your access changed while the terminal was open. You can still watch.
"Your access to this session ended."
Your access changed, or the session was closed.
"You cannot open this session from this computer."
Your access to the team or to Developer access changed. Run HQ: Refresh.
"Instant local echo is off for Acme. ..."
An owner or admin turns on Instant local echo in HQ, under Settings, Security. The terminal works without it.
"Local echo is not available on this HQ yet."
The terminal works without local echo.
"HQ local echo is off in this terminal because VS Code's own local echo is on (terminal.integrated.localEchoEnabled)."
Set terminal.integrated.localEchoEnabled to off to use HQ's.
Files
Message
What to do
"Backend team is off. Wake it to open this file."
Press Wake Team, then open the file again. Files you already opened stay readable.
"Backend team is off. Wake it to save this file."
Press Wake Team, then save again.
"This file changed on the AI Team Cloud Computer. Save again to compare."
Save again, then compare or overwrite.
"You can view this team but not change its files."
You have viewer access to the team.
"This file came from an AI Workforce One HQ template, so it is read-only."
Template files on a template team cannot be changed.
"This file contains masked secret values. Edit it from an HQ terminal."
Change it from a session terminal, or the secret in HQ. After a secret is removed in HQ, the file unmasks by itself within about 15 seconds.
"This file is too large to open here. Open it in HQ or from a terminal."
Use HQ or a session terminal for that file.
"This file's name has control characters HQ can't open. Rename it on the Cloud Computer."
Rename the file from a session terminal.
"This team is not available on this sign-in. Sign in, or refresh the Teams view."
Run HQ: Refresh, or sign in again.
"This folder belongs to owner@client.com, who is not signed in on this computer."
Press Sign in as owner@client.com and approve as that account. The folder fills in.
"This folder belongs to an HQ account that is not signed in on this computer. Open it again from the Teams view."
Remove the folder and open the team again with Open Team Files.
"Backend team's Cloud Computer is updating. Its files are back once it is done. This usually takes about 5 to 6 minutes."
Wait for the update to finish.
"Live file updates for Acme are paused: ..."
Too many editor windows are open for this sign-in. Close other HQ windows. Files still refresh every minute.
"The search did not run: ..."
Read the reason, then search again.
Ports
Message
What to do
"Port 9229 cannot be forwarded: the AI Team Cloud Computer uses it itself."
Forward another port. HQ refuses the Docker API, the Node debugger and the Cloud Computer's own ports.
"Backend team started before Developer access was turned on. Restart it once (Restart Cloud Computer in HQ team settings) and ports will forward."
Developer access was turned on while the Cloud Computer was running. An organization owner or admin presses Restart Cloud Computer in the Cloud Computer section of the team's Settings in HQ. Sessions pause and come back where they were. This usually takes about 5 to 6 minutes.
"You cannot forward ports from Backend team."
You need editor or owner access and an active plan.
"Backend team is off. Wake it, then forward the port again."
Press Wake Team, then forward again.
"Backend team is stopped. Start it from the team page in HQ, then forward the port again."
Start the team in HQ.
"Could not forward the port: the port is already in use on this computer"
Something on this computer already uses that port. Forward again and pick another port on this computer.
"The forward of port 3000 ended."
HQ ended the forward. Click it in the Ports view to start it again.
The extension's log
View, Output, then pick AI Workforce One HQ in the list: the extension records its sign-ins,
accounts (by a short code, not your email) and sign-outs there. It never records a token, a key, a
sign-in code or the contents of a file.
Still stuck?
Email support@aiworkforceone.com with the extension's version
(in the Extensions view), your editor's name and version, the exact message, and the lines of the
extension's log from around that time.