Why this matters
Intent to submit for Gemini XPRIZE.
Practical agent workflows for constrained environments, approved endpoints, and human review.
Gemini XPRIZE intent · public beta
AgentOS is a local workspace and dashboard for running agent workflows on Windows machines where users may have limited permissions. It helps connect approved model endpoints, launch local runtimes, and keep the work visible to the user.
Downloading the beta means you accept the terms. Registration is optional. Email: hello@mix-of-agents.com.
Why this matters
Practical agent workflows for constrained environments, approved endpoints, and human review.
Purpose
AgentOS gives users a local control surface for approved endpoints, visible sessions, and environment-aware automation.
Use an approved API, OAuth-backed provider, or local OpenAI-compatible endpoint. AgentOS does not bundle model access.
The beta is a folder-based workspace with launchers, scripts, and a dashboard bridge. Users can test the parts their environment allows.
The dashboard emphasizes visible status, explicit session controls, and human review rather than hidden background automation.
Example environments
Designed for places where useful work has to fit existing device permissions, network rules, and review expectations.
Requirements
Begin with browser-only review, then add endpoint access, PowerShell, Python, or local services only where allowed.
Dashboard preview
Example tiles showing how recent work could be resumed intentionally.
Python bridge role identified; dashboard preview state loaded.
PreviewAPI, OAuth, and local endpoint setup examples staged securely.
ReadyAgent role, runtime limits, and next action summarized before execution.
QueuedGeneric setup examples. No private endpoints, tokens, or keys are shown.
Example connector area for files, approved endpoints, and future integrations.
Attach or stage user-approved local files.
Keep calls routed through configured provider settings.
Lightweight notes explain what works with browser-only review, PowerShell, Python, and local endpoints.
The beta should make incomplete functionality clear instead of pretending everything is finished.
Beta terms
Please review these beta terms before downloading, testing, or sharing feedback. Additional policies or signed agreements may apply where separately posted or provided.
Status. AgentOS is beta software provided for evaluation, testing, and feedback. Some features may be incomplete, unstable, local-only, or dependent on the user's device permissions, installed tools, configured endpoints, and organizational policies.
Free beta access. The current beta is offered without charge. Free access does not create a support obligation, uptime commitment, warranty, service-level agreement, or promise that future releases will remain free or unchanged.
License to use the beta. Subject to these terms, users may download, extract, run, and evaluate the beta for personal, internal, or organizational testing. Users may not sell, repackage, misrepresent, or redistribute AgentOS as their own product without written permission or a separate license.
User content and intellectual property. Users keep their rights to their own prompts, files, data, workflows, and outputs, subject to the terms of any model provider, endpoint, or third-party service they choose to use. Mix of Agents retains rights in the AgentOS software, site, documentation, design, branding, and related materials. Feedback, bug reports, feature requests, and usage suggestions may be used to improve AgentOS without obligation to compensate the submitter.
User responsibility. Users are responsible for choosing approved endpoints, protecting credentials, following workplace or organizational rules, and reviewing outputs before using or sharing them. Do not submit secrets, protected data, regulated records, or confidential material unless you are authorized and the endpoint you choose is approved for that data.
Local files and logs. The local workspace may create configuration files, logs, memory, cached data, runtime outputs, or session artifacts inside the extracted folder. Users should inspect, retain, delete, or protect those files according to their own requirements.
Site logging and beta evidence. The public site may record beta signups, optional contact information, testing-environment notes submitted by the user, download events, timestamps, and basic request metadata. This helps measure adoption, improve packaging, and prioritize development. The beta should not require a public account merely to download.
Third-party services. AgentOS may connect to external model providers, local model servers, APIs, or other endpoints configured by the user. Those services are governed by their own terms, pricing, privacy practices, security controls, and usage limits.
No warranty. The beta is provided as-is and as-available. It may fail, produce incorrect outputs, lose local state, or behave differently across environments. Users should not rely on it for safety-critical, medical, legal, financial, emergency, or production decisions without independent review and appropriate safeguards.
Restricted environments. AgentOS is designed to degrade by layer, but it cannot bypass device policy, network policy, endpoint restrictions, script controls, or administrative rules. Users should not attempt to use the beta to evade controls.
Additional terms. A fuller EULA, privacy policy, contribution policy, or source license may apply if published separately. If there is a conflict between these short beta terms and a signed or separately published agreement, the more specific agreement controls.
Scroll inside the box to review all beta terms.
Beta updates
Share an email and any context that would help prioritize the beta. Keep sensitive details out of this form.