AGI FAQ: frequently asked questions across ten groups.

Zeus AGI is a general intelligence for real work, built by PC LAB (UK) and delivered as a local-first desktop application for any operating system and 11 x64. Give it a goal and it plans, acts, verifies and reports across unlimited domains, on your machine, with your tools and your accounts.

A any operating system PC with an x64 processor, and an internet connection for the tasks that need one. Install the desktop application, connect the model provider you want or a local model, then open a project folder and give it a goal. No server and no cloud workspace are required.

You state the finished result, the constraints and anything that needs approval. Zeus AGI returns a plan, executes it across the tools the job needs, checks the result against the brief and reports what changed with evidence. You can approve, redirect or stop at any point that matters.

It works across unlimited domains: websites, CMS, SEO, code and terminal, content, media, research, data, documents, automation, browser work, servers, devices, business operations, events, invention, medical and lab machines, skills and MCP, Agent Teams and your own domain. The list is examples, not a limit: new skills and MCP connections extend it on request.

Yes. Zeus AGI plans the pages, writes the copy, builds the design, prepares the assets, deploys to your hosting over SSH or through CMS, then checks the live result and reports what changed. The work happens on your accounts and under your permissions, with approvals before anything irreversible.

It works in your files and terminal: writing and editing code, running commands and tests, using Git, reading logs and verifying the result before reporting. Because the same intelligence is general, one run can also update the documentation and deploy the build. It works on real repositories, not pasted snippets.

Yes. The media studio generates and edits images and video, prepares them for the web and places them where the page needs them. A document workflow reads, writes and restructures files for real work, including spreadsheets and reports. The output is finished work saved in your files, not a folder of candidates.

By the definition this site uses, yes. AGI here means general, autonomous, real-world intelligence for digital work, tested six ways: generality, autonomy, real-world operation, self-verification, memory and orchestration. All six can be checked in the product. The claim is operational rather than rhetorical, and it does not include consciousness or human-level performance.

No, and the site does not claim it. The definition here is deliberately narrower: general, autonomous, real-world digital work with verification and memory. That is a high bar, but it is not the same as general human capability, and nothing on this page depends on matching a person at everything.

It means one intelligence handles many kinds of work instead of one narrow task, and carries context between them. A research brief can become a landing page; the page can become a deployed site; the site can become a report. Generality is what removes the hand-offs between separate products.

It does not decide legal, medical or financial questions for you, and it does not act in regulated environments without a qualified human in the loop. It cannot reach systems it has no access to, and it can be wrong. The limits page sets out the boundaries, the approval gates and the things it will not claim.

Local-first is the default: the application, your project files and your output live on your machine, and PC LAB does not host your workspace. When you use a cloud model provider, prompts pass through that provider’s service. You choose the provider, or run a local model to keep inference on your machine.

Your machine is where the work lives: files, projects, memory and output sit on your disk and the application runs there. Network calls happen when you choose a cloud model or when a task needs the internet. Local-first describes location and control, not a marketing label.

You do. Websites, code, copy, documents, images and reports produced during your work are yours, saved in your files, with no lock-in. Your code stays in your repositories and your content stays in your files. Ownership is how the product is built, not a feature of a plan.

With local models, yes: the app and your files are already local, and a local model keeps inference on device too. Cloud model calls need a connection. Tasks that touch live systems, such as deploying a site or browsing the web, need the internet by definition.

Agent Bridge is the PC LAB CMS plugin that gives Zeus AGI a direct, controlled connection to your site: magic login, site status and cache purge. It removes the manual signing in and cache clearing, so the agent can work on the site and verify the result. It is a plugin on your site, not a change to your host.

You choose. Zeus AGI works with multiple model providers and can use a local model for private work. The intelligence is in how the system plans, acts, verifies and remembers, not in a single model. Changing provider changes the engine, not the job.

Yes. Scheduled tasks and automation let Zeus AGI run recurring work without being prompted: site checks, reports, content refreshes and maintenance. Each run follows the same loop of plan, execute, verify and report, and you can review the output or step in wherever a decision is needed.

Agent Teams is orchestration. One lead intelligence splits a large goal into workstreams, assigns specialist agents, runs what can run in parallel, then reviews and merges the results into one report. It is how Zeus AGI handles work too large for a single thread, with one accountable result rather than several conflicting ones.

Use it when a job has genuinely parallel parts or needs different specialisms: a site build with copy, design and checks at once, a multi-market research report, or a maintenance sweep across several sites. For a single page or a single fix, one thread is faster and simpler.

Skills are reusable procedures the agent learns and keeps, so a solved problem becomes a repeatable capability. MCP servers connect it to external systems through a standard protocol. Together they mean a new domain is often a request away rather than a new product, which is why the capability list is examples, not a limit.

No. It means the scope is open to work that is digital or device based, and to whatever a skill or MCP connection can reach, with your permissions and the same verification loop. Physical limits, access limits and human responsibility still apply, and the limits page says so plainly.

Yes, across the work around an event or a business: planning documents, pages and registration copy, supplier research, schedules, asset production, on-the-day checklists and the post-event report. It also runs recurring operations such as site maintenance, content refreshes and reporting. The organising intelligence is the same one.

It can help with the digital and device-based work around them: setup and configuration records, documentation, data cleaning, device management over permitted access, research summaries and reports. Clinical or diagnostic decisions stay with qualified people. It supports the work around care and never replaces clinical judgement.

Use the contact page for a message that reaches the right person, or email zeus@pclab.tech directly. Tell us the job you want done and the constraints that matter, and a real person will reply with next steps. Support questions, press requests and early access applications all arrive at the same team.

This AGI FAQ covers ten groups: getting started, capabilities, AGI questions, privacy and ownership, technical setup, Agent Teams, skills and MCP, events and business areas, medical and lab machines, and working with PC LAB. It gives short answers with pointers. The limits page carries the boundaries, and the contact page takes anything unanswered.