TRUST · SUPPORT
Support for Zeus AGI: three fast routes to help.
Support for Zeus AGI starts with the fastest route: the FAQ settles most questions without a ticket. When it does not, email and the contact form reach a person who can investigate. This page explains how support works, what to include and what to do when something has genuinely failed.
HOW SUPPORT WORKS
How Zeus AGI support works
Support here is small, direct and technical. There is no tiered queue and no script. Messages go to the people who build and run the product, which is why a clear reproduction step is worth more than a long description of frustration.
The route depends on the question. A behaviour question belongs in the FAQ, which covers setup, capabilities, privacy, Agent Teams and the honest limits. A failure belongs in support, where we can look at logs and the sequence that led to it. A commercial or partnership question belongs in contact, where it reaches the right person on the first attempt.
We aim to reply within two working days, Monday to Friday, UK time. Complex investigations take longer, and when they do we tell you the expected date rather than leaving the thread silent. We would rather give you one accurate answer than three quick ones that turn out to be wrong.
THREE ROUTES
Three support routes and when to use them
The FAQ first
Most questions about setup, model choice, approvals, ownership and limits are already answered there, in short quotable answers.
Email for a record
Write to zeus@pclab.tech when you want the conversation in writing with attachments: logs, screenshots, a failing script.
Contact for context
The contact form is best when the help you need starts with a decision: which setup, which workflow, whether this fits.
WHAT TO SEND
The diagnostics checklist to include with a support request
01
The outcome you asked for
Give the goal as you typed it, plus the constraints and approvals attached to it. The instruction text is often enough to reveal whether this is a product issue or a misunderstanding.
02
The steps that led there
List what you did in order: which tool, which file, which site, which model provider. If the failure repeats, we care about the smallest sequence that reproduces it.
03
The exact message
Paste the error text rather than describing it. A stack trace, a log line or the report the agent returned is more useful than ‘it failed’, because it names the layer that broke.
04
Your environment
Windows version, x64 or not, the current release of the app, which model provider you were using and whether a local model was in play. This narrows the cause faster than any other detail.
05
What you already tried
Retries, restarts, a different provider, a fresh project folder. This avoids us suggesting steps you have already done, and it tells us whether the problem survives a clean start.
HONEST LIMITS
What support cannot do for you
Support cannot see your machine unless you choose to send the evidence. The product is local-first by design, so we cannot reach into your files, your accounts or your hosting. Anything we diagnose, we diagnose from what you send us, which is why the checklist above exists.
Support cannot recover data that was deleted without a backup, and cannot make a third-party model provider or hosting provider behave. What we can do is confirm whether the fault sits in Zeus AGI or outside it, and give you the precise evidence to take to the other provider if it is theirs.
Support also cannot make a regulated or unsafe request acceptable. If a task needs a qualified human decision, the answer will say so. That is not a limitation of the support desk; it is the same boundary described on the limits page.
OUTSIDE THE PRODUCT
When the fault is not in Zeus AGI
Some failures arrive from outside the product: a model provider has an outage, a hosting provider changes a permission, a plugin update breaks a site, a network drops mid-run. In those cases the run report matters most. It shows which call failed and what the system did next, which is the difference between an outage you can wait out and a fault you can fix.
When the fault is external, we will say so plainly and give you the evidence to take to that provider. What we will not do is pretend the failure was your mistake, or leave a thread open while a third party takes a week to answer.
FAQ
Questions, answered.
Short, direct answers. If yours is missing, the full FAQ page has more.
Read the FAQ entry for the area first, then check the report the agent returned. Reports name what was verified and what failed, which often shows whether the fault is in the task, the access or the model. If it is still unclear, send the support request with evidence.
Send the smallest sequence you can find, the exact error text, your environment and what you had already tried. Note whether it happens with a local model and whether it survives a fresh project folder. A partial but precise reproduction is still useful.
No, not by default and not silently. Zeus AGI runs on your machine and PC LAB does not host your workspace. If a problem genuinely needs deeper evidence, we ask you to collect or send it, and you decide what leaves your machine.
Support is staffed Monday to Friday, UK time, and we aim to reply within two working days. Messages arriving at the weekend are read on the next working day. Investigations that need more time get a holding note with an expected date.
Open the run report first. It records the plan, what ran, what was verified and where it stopped, which is usually enough to see whether access, a provider call or the task itself failed. If the report is unclear, send it with the support request.
The FAQ covers ten groups of questions in short answers, and the limits page sets out the boundaries in full. Between them they answer most of what reaches the support desk, especially on setup, model choice, ownership and approvals.
BEYOND THIS
This is one example. The next domain is a request away.
Zeus AGI acquires the skills it needs and connects MCP servers, so the scope is not a fixed feature list. If the work is digital or device based, it is in scope.
RELATED
Send the evidence, not just the symptom.
A goal, a sequence and an error message get a real answer faster than any amount of description. Support reads every message and replies with the next step.