Guide / Troubleshooting
Find the blocker.
Keep the next step clear.
Start with the current task state and the visible error. A specific cause is easier to fix than a chain of repeated requests.
An agent went quiet
Open the task and its conversation. Check whether it is running, waiting for a decision, blocked, or ready for review. Look for a failed tool call, model error, or missing prerequisite.
- Confirm the host is awake and connected.
- Check the model provider’s available credit and limits.
- Look for an approval request or a question that needs your answer.
- Check whether the expected output already exists in the project.
Once the cause is resolved, give a concrete continuation instruction. Avoid starting multiple copies of the same task while the original is still active.
A model request failed
Check the selected provider and model in the app. Confirm the account has access to that model and can make requests. A depleted balance or rate limit can interrupt otherwise valid work.
If the error is about credentials, update the connection in account settings. Keep keys out of chat, screenshots, and bug reports. If the provider is unavailable, wait for recovery or choose another supported connection.
A teammate cannot find a file
Ask the sender for the exact path and the host where it was written. Ask the recipient to check that location. A file in an agent’s private workspace is not automatically a shared project deliverable.
- Confirm both agents are working in the intended company and project.
- Use the shared project folder for handoffs.
- Verify the file exists before asking another agent to continue.
- Name one owner when integrating simultaneous changes.
An agent computer will not start
Read the startup error before retrying. Check that setup completed and the host is available. A local port conflict, missing runtime prerequisite, or interrupted download each calls for a different next step.
Record the build version, OS version, and the last visible setup step. Share only the relevant error text after removing private paths and credentials.
A task stopped overnight
Check whether the host slept, shut down, or lost connectivity. Background work needs Zipper’s agent service to remain available. Model limits and required approvals can also stop progress.
For work that must continue while your laptop is off, use a host that can stay online. Verify a small background task before relying on a longer unattended run.
Report a reproducible problem
For invited builds, use the private project channel available to you. Include the exact steps, expected outcome, actual outcome, build, and operating system. Explain whether the problem occurs every time.
Read security reporting guidance