UPDATES · NEWS
Zeus AGI news: build updates and release notes.
Zeus AGI news is where PC LAB publishes what changed and why: release notes, build updates, product decisions, engineering notes and the occasional explainer. There is no publishing calendar kept for its own sake. Pieces appear when there is something real to report, and this hub is where they collect.
WHAT LANDS HERE
What Zeus AGI news covers
The hub carries the record of a product being built in the open: what shipped in a release, what broke and was fixed, what changed in how the agent plans or verifies, and why a decision was made. Release notes are the spine of it, because a product that verifies its own work should be able to describe what changed.
It also carries the work around the product: Agent Teams improvements, new skills and MCP connections, and the longer explainers that answer questions a release note cannot. When something on the site changes materially, such as a revised definition or a new page explaining a limit, the change is noted here rather than slipped in silently.
THE SECTIONS
The kinds of update you will find
Release notes
What changed in a build, what it fixes and what to check after updating. Written for people who run the product, not for changelog tourists.
Engineering notes
How a hard part works: the planning loop, verification, memory, orchestration. The reasoning, not just the announcement.
Product decisions
Why a boundary exists, why a capability is described a certain way, why a feature was declined. The honest version, including the trade-offs.
AGI explainers
Short pieces on the definition, the six tests and the difference between a general intelligence and a narrow model.
Company updates
PC LAB announcements that affect users: platform requirements, availability, early access openings and changes to how support works.
HOW TO FOLLOW
How to follow Zeus AGI news without the noise
01
Start with release notes
If you use the product, the release notes are the only section that needs regular attention. They tell you what to test after an update and what changed in behaviour.
02
Read an explainer only when you need it
The longer pieces are written to be found by question, not consumed as a stream. When a release note raises a why, follow the link rather than reading everything.
03
Ask for the update you want
If a change matters to your work and has not been explained, ask through the contact page. Questions from real use are the best guide to what deserves a written note.
EDITORIAL STANDARD
What this news hub will not do
It will not invent milestones to fill a calendar, publish client stories without approval, or dress a routine change as a breakthrough. It will not quote performance figures that cannot be reproduced, and it will not turn a known limitation into an exciting roadmap item. A short note that gives the real reason is worth more than a long announcement that gives none, and the page is judged on that standard rather than on how often it publishes.
When a piece here is wrong, it is corrected on the page with a note rather than deleted. A record that quietly loses its mistakes is not a record, and the same standard the product applies to evidence applies to the writing about it.
FAQ
Questions, answered.
Short, direct answers. If yours is missing, the full FAQ page has more.
It is the record of what changes in the product and why: release notes, engineering notes, product decisions and explainers. It exists so that people who run Zeus AGI can see what moved in a build, what to check afterwards and where the reasoning came from.
When there is something real to report. There is no fixed cadence and no quota, because a schedule that must be met produces announcements rather than information. Release notes appear with releases, and explainers appear when a question keeps returning.
Yes. If a part of the product is unclear, or a release changed something you rely on and the note did not explain it, send the question through the contact page. Repeated questions are the strongest signal that a written piece is worth publishing.
Yes, and they are the most useful part for anyone using the product. Each note covers what changed in the build, what it fixes, and what to check after updating. Read those first; the longer pieces can wait until a question sends you to them.
On the tutorials hub rather than here. News records what changed; tutorials explain how to do something with it. If you are looking for a walkthrough of a first task or of Agent Teams, the tutorials page is the right starting point.
On the page, with a note. A correction is visible rather than silent, and the original claim is not quietly removed. The same evidence standard the product applies to its own work applies to the writing about the product.
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.
Follow the build, not the hype.
Release notes and engineering notes are written for people who use the product. Start with the capabilities hub to see what the build is for.