TRUST · EARLY ACCESS
AGI early access: try the general intelligence first.
AGI early access is a small programme for people who want to test a general intelligence on real work before the wider release. You get the desktop application, a direct line to PC LAB and the chance to shape what comes next. Places are limited, and we say so plainly rather than inventing urgency.
WHO IT IS FOR
Who AGI early access is for
Early access is for people with a real job in front of them, not for people collecting a demo. If you run a small agency and need client sites built and checked, if you maintain servers and want logs read and fixes verified, if you research markets and need sources carried through to a report, this programme is built around that work.
It suits a person who can describe the finished result and then judge it. You do not need to write code to take part, but you do need to be willing to say when the output is wrong. The feedback is the point of the programme, and it is worth more when it is specific.
It is not a good fit for anyone looking for an anonymous trial with no contact. Early access involves a conversation with PC LAB, a real task on your own machine and a short report back on what happened.
WHAT IS INCLUDED
What early access includes
The desktop application
The current local-first build for any operating system and 11 x64, installed on your own machine with your own model provider or a local model.
A direct line to PC LAB
A named contact for questions, failures and feedback. No ticket maze, and no anonymous support queue between you and the people who build it.
Early sight of new work
New skills, MCP connections and Agent Teams improvements reach early access first, so your feedback can land before a feature is finished rather than after.
Influence on priorities
Specific, well-described problems shape the roadmap. Early access members are the people whose work exposes what a general intelligence still lacks.
HOW TO APPLY
How to apply for AGI early access
01
Describe one real job
Use the contact page and tell us what you would hand over first: the site, the server, the report, the event. Include the outcome and the systems involved, not a wish list of features.
02
Tell us about your setup
Windows version, whether you use a cloud model provider or a local model, and the accounts or access the work would need. This determines whether the job can run safely on day one.
03
We reply with fit and timing
PC LAB answers with an honest assessment: a place now, a place in the queue with an expected window, or a no if the programme is not the right route for your case.
04
Onboard, run the task, report back
Once accepted, we set up the first task together, watch the loop close and ask for a short written note on what worked, what failed and what you would do differently.
THE HONEST NOTE
What places are limited actually means
Places are limited because early access is supported by people, not by a queue that scales itself. Every participant gets attention on their own work, and taking on more than the team can support properly would turn the programme into a waiting room with a label.
So the process has three outcomes, and two of them are not acceptance. You may be offered a place now, added to a queue with an expected window, or told that the programme does not fit your case and why. An application is not a commitment for either side.
We will not invent scarcity to hurry you, and we will not promise a date we do not believe. If the timing matters, say so in the application and we will tell you honestly whether early access is the right route or whether the open release is.
FAQ
Questions, answered.
Short, direct answers. If yours is missing, the full FAQ page has more.
A small programme that puts the desktop build of Zeus AGI in the hands of people with real work to do, before the wider release. It includes a direct contact at PC LAB, early sight of new skills and Agent Teams work, and a real influence on priorities.
A any operating system PC with an x64 processor, a model provider or a local model, and one real job you are willing to hand over. You also need time to review the report and tell us clearly what worked and what did not.
Use the contact page and describe one real job plus your setup. There is no long form and no automated scoring. A person at PC LAB reads the application and replies with fit and timing, usually within two working days.
Sometimes. When places are full, applications go into a queue and we tell you your position and an expected window. If the wait is long and the timing is critical for you, we will say so rather than quietly holding the application.
We agree a first task, set up the access it needs and run it together. You get the result and the evidence, then a short written check-in: what worked, what failed, what you would change. That note is what the programme exists to collect.
Because every participant gets attention on their own work. The programme is supported by the people who build the product, and accepting more members than can be supported would make the label meaningless. Limiting places protects the quality of the feedback for everyone.
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
Bring a real job, not a wish list.
Tell PC LAB what you would hand over first and what your setup looks like. You will get an honest answer about fit and timing, and a place if there is one.