Troubleshooting

Cause: LatentWork got no answer from the URL.

Fix: Check the URL is your LatentStack server's address, for example https://latentstack.dev, and that this computer can open it in a browser. On a company network, check your VPN.

Cause: Something answered at that address, but not successfully.

Fix: Check the URL points at your LatentStack server and not at another site on the same host.

Cause: The server refused the key.

Fix: Copy your key again from your Account page and paste it into API Key.

Cause: The server is reachable but your model list didn't load: usually a wrong or regenerated key, or no models available for your organization and team.

Fix: Open Settings → LatentRouter, paste your current key from your Account page, and select Save. If it still fails, try No team in the Teams menu, and ask your administrator which models your tier allows.

Cause: No models are available to LatentWork, so tasks can't run.

Fix: Select the message to open Settings → LatentRouter and check the URL and key, as for Gateway unreachable.

Cause: No API key is saved.

Fix: Enter the URL and key and select Save & Continue. It only closes once the connection works. If it keeps happening, contact your administrator.

Cause: The organization list couldn't be fetched, or your key isn't a member of any organization.

Fix: Check the connection as above. If you should be in an organization, ask its administrator to invite you.

Cause: It is usually waiting for you: an approval panel above the message box pauses the task until you answer.

Fix: Answer the panel with Deny, Allow once or Allow for session. To give up on the task, select Stop, or press Esc twice in the message box.

Cause: The agent is still working, so a new message must be steered or queued.

Fix: Choose Steer to send now or Queue to send when it finishes.

Cause: The task's model is no longer on your tier.

Fix: Select the model button under the message box and choose another model.

Cause: The task is using most of the model's context window, and Auto context compaction is off.

Fix: Send /compact to summarize the task, or turn on Auto context compaction in Settings → Preferences.

Cause: /compact only works in a task that has messages.

Fix: Open the task you want to compact first.

Cause: Tasks are listed under their workspace, and only workspaces in the sidebar are shown. It may also be archived.

Fix: Look in the workspace's collapsed Archived section. If you removed the workspace, add the same folder again with Add workspace; its tasks come back. ⌘/Ctrl+K → Search sessions finds tasks by title.

Cause: The task or workspace you opened no longer exists, for example it was deleted or removed.

Fix: Pick another task or workspace in the sidebar.

Cause: That file type isn't supported, for example PowerPoint or .doc.

Fix: Do what the message says, usually saving as PDF, .docx or .xlsx. The full list is in Attach files.

Cause: The file is over its size limit: 100 MB for PDFs, 10 MB for CSV and TSV, 5 MB for text and code, and 25 MB for everything else.

Fix: Split or shrink the file, or put it in the workspace folder and mention it instead of attaching it.

Cause: A message can carry up to 8 attachments.

Fix: Send the rest in a follow-up, or put them in the workspace folder.

Cause: Edit message isn't available for messages with attachments.

Fix: Use Revert on the message and send a new one.

The notice says why. The most common reasons:

• That folder has … files. The limit is 5,000 — try a subfolder. / That folder is …. The limit is 200 MB — try a subfolder. Upload a smaller subfolder instead, or several one at a time.
• "…" is …. Single files are limited to 100 MB. Move that file out of the folder, or split it, and try again.
• Every file in that folder was skipped (… ignored, such as .git or node_modules). The folder only held folders and files that are always skipped. Choose a folder with documents in it.

Cause: A file in the folder is locked, open in another app, blocked by permissions, or stored in the cloud and not downloaded yet. The message names the files.

Fix: Close the file, or download it to your computer first (or move it out of the folder), then upload the folder again.

Cause: You dragged more than one folder, or a folder together with loose files, onto the message box.

Fix: Drop each folder on its own. Each one is uploaded under its own name.

Cause: The folder is too big to read completely when dragged in.

Fix: Select Upload a folder next to the paperclip and choose the folder instead.

Cause: Some files failed partway through the upload. Nothing was saved, so the agent never sees a half-uploaded folder.

Fix: Upload the folder again.

Cause: The side panel can't show this file type.

Fix: Select Show in folder and open the file in another app.

Cause: LatentWork hadn't finished starting when you added the workspace.

Fix: Quit LatentWork completely and open it again, then add the workspace again.

Cause: The app needs your account, or your sign-in expired.

Fix: In Settings → Extensions, select the app under Your apps and choose Sign in.

Cause: New apps and skills are only picked up after a reload.

Fix: Select Reload now on the Reload required notice. If you chose Later, finish your task and reload from the next notice.

Cause: For a skill: it has no description. Its tile in Extensions shows Agent can't see this, and the agent never uses it.

Fix: Add a description to the skill. See Skills.

Cause: The folder is outside the workspace.

Fix: Authorize it in Settings → Permissions. See Folders outside the workspace.

Cause: The installed app was built for a different processor than your computer's.

Fix: Select Download correct version, install it, quit this copy and open LatentWork again. Your workspaces and settings are kept.

Cause: The app was downloaded with a browser instead of the install script.

Fix: Reinstall with the install script.

Cause: The downloaded app file can't start on some Linux systems.

Fix: Use the install script instead of opening the AppImage directly, then start LatentWork from the app menu.