Sandboxing isn't available
Bubblewrap and OverlayFS are Linux-only. On macOS (Weave Lite) they're absent by design. On
Linux, make sure bubblewrap is installed and your kernel allows unprivileged user
namespaces; otherwise turn the sandbox off under Settings → Security (weaker
isolation) or install the missing pieces.
A task or chat can't see a file
Tool access is limited to the project directory. If work needs a file outside it, add that directory to the project's, weave's, or task's allowed paths rather than moving the file.
A shell command timed out
Bash commands stop at 120 seconds by default. For a legitimately long build or test, the model can pass a larger timeout — but don't start dev servers or watchers as a tool call; they'll only hit the timeout.
A task needs (or shouldn't have) network
Shell network access follows the task's disable network setting. Leave it off
to let package managers and git reach the network; turn it on for stricter
isolation. File tools never use the network.
Weave DMABuf rendering is unavailable?
By default, Weave disables WebKit's DMABuf renderer on Linux to ensure compatibility with a broad range of GPU drivers. If you experience rendering issues or want to opt back in (e.g., for smoother compositing on a supported driver), you can re-enable it: WEBKIT_DISABLE_DMABUF_RENDERER=0 weave
Note that on some driver and WebKit2GTK version combinations, re-enabling DMABuf will cause Weave to crash at startup. If that happens, simply remove the variable.
The model list is empty / a provider won't connect
Check the provider's API key and base URL under Settings → Providers. For Ollama, make sure the local server is running and the base URL points at it.
A weave is stuck "running" after a crash
Interrupted runs are swept on the next launch — restart Weave and the affected tasks are marked failed so the weave can be run again.
Still stuck?
If none of the above sorts it out, we're happy to help. Drop an issue at Gitlab or email us [email protected] with a short description of the problem, what you expected, and the steps that led to it. Including your OS and Weave version helps us get you an answer faster.
Not responsible for bugs resulting in loss of data, incurred token charges, or other damages. Use at your own risk.
