Troubleshooting

Errors shown in the sidebar

When a request fails, the sidebar names the problem. Each message has its own page:

What you see	Code	Page
"Sign in to OfficeLabs to continue."	sign_in_required	Sign-in needed
"Your OfficeLabs credit is used up."	quota_exhausted	Quota used up
"Please try again shortly."	rate_limited	Rate limited
"The assistant service is temporarily unavailable. Please try again in a moment."	inference_unavailable	Service unavailable
The sidebar never answers	none	Service not responding
No internet connection	none	Offline

Other messages in the sidebar

Some failures have no error code. The sidebar shows these sentences instead.

"OfficeLabs can't reach its assistant service. It may still be starting — try again in a moment."

Cause: The sidebar could not connect to the local assistant service on your computer. It may still be starting, or it is not running.

What to do: Wait a moment and send the request again. If it keeps appearing, follow Service not responding.

When to contact support: If the message stays after you restarted OfficeLabs, as described on that page.

"The assistant service returned an error (HTTP nnn). Try again."

Here nnn is a three-digit number.

Cause: The local assistant service answered, but with an error.

What to do: Send the request again. If it repeats, restart OfficeLabs.

When to contact support: If the same number appears every time after a restart. Include the number and the time it happened.

"The run ran out of time before it finished. Some changes may be incomplete." and "The run hit its step limit before finishing."

Cause: The request was too large to finish in one run.

What to do: Check the document for incomplete changes, then split the request into smaller steps and send them one at a time.

When to contact support: If small requests also hit these limits.

Install and launch problems

SmartScreen blocks the installer

Symptom: Running OfficeLabs-Setup.exe shows "Windows protected your PC."

Why: This alpha build isn't code-signed yet, so Windows doesn't recognize the publisher. This is expected right now, not a sign of a corrupted download.

Fix: Select More info, then Run anyway. See Install → About the unsigned installer.

Install fails or produces a broken copy

Symptom: The installer shows an error and stops, or (rarely, on older builds) appeared to succeed but OfficeLabs won't start afterward.

Why: The installer copies files into C:\Program Files\OfficeLabs. If a file it needs to replace is locked — most often because a previous OfficeLabs is still running, or your antivirus has the file open for a scan — the install can't proceed. Current builds fail loudly and write a line to %TEMP%\OfficeLabs-Setup.log when this happens, rather than silently leaving a mixed install.

Fix:

1. Close OfficeLabs completely. Check Task Manager for any lingering soffice.exe, soffice.bin, or python.exe processes and end them.
2. Temporarily allow the installer through your antivirus's real-time scanning, or wait for its scan to finish, then retry.
3. If it still fails, check %TEMP%\OfficeLabs-Setup.log for the reported reason and include it if you report the issue.

Nothing happens when you launch OfficeLabs

Symptom: You start OfficeLabs from the Start menu or desktop shortcut, and no window ever appears.

Why: The shortcut runs a launcher script that starts two local background services (the agent and app-backend) and waits up to 90 seconds for both to report healthy before it opens the LibreOffice window. If either service fails to start, or the window itself doesn't appear within a further 20 seconds, the launcher gives up and shuts everything back down — with nothing shown on screen.

Fix:

1. Open %LOCALAPPDATA%\OfficeLabs-launcher\launch.log in a text editor and look at the most recent run (the log is appended to, so scroll to the bottom).
2. A line like FAILURE: Timed out waiting for services to become healthy or Service <name> exited unexpectedly points at the agent or app-backend, not LibreOffice itself. Check the matching agent-*.log or app-backend-*.log file in the same folder for the underlying error.
3. A line like Soffice closed; stopping services. with no FAILURE line before it means the services started fine but the LibreOffice window itself closed or never appeared — try launching again, and report the run if it repeats.

Sidebar opens but never responds

See Service not responding.

Inline suggestions don't appear in Writer

See Inline suggestions don't appear. Inline suggestions run on your computer and need no sign-in; the most common cause is the switch being off.

Can't download — the button is disabled

Symptom: The Download for Windows button on the download page is greyed out.

Why: The button stays greyed out until you sign in. If you are signed in without a paid plan, the button works but the download is refused with a message.

Fix: Sign in first (or create an account and choose a plan if you haven't), then return to the download page.

Collecting logs for support

When you contact support, attach these files so we can see what happened:

• Windows launcher logs: everything in %LOCALAPPDATA%\OfficeLabs-launcher, in particular launch.log and the newest agent-*.log and agent-*.err.log. The launcher keeps the 10 newest per-run agent logs.
• Local traces: ~/.officelabs/traces (on Windows, %USERPROFILE%\.officelabs\traces) holds traces of your requests. Traces are kept on your computer; a normal install sends them nowhere. They may contain text from your documents. Open them and review them before sending, and send only what you are comfortable sharing.
• Setup log: %TEMP%\OfficeLabs-Setup.log, if the problem is with installing.

Reach support through the contact page on the OfficeLabs website. Never send your password.

Next

• Install
• Uninstall