Windows public distribution
Launch signed direct downloads and Microsoft Store availability together.
Release roadmap
December 1, 2026 is our target to finish and launch Denizens on Windows. Development is roughly 80% complete by our estimate. The target depends on the remaining release checks and Microsoft Store approval.
Updated 16 November 2026 · Waitlist phase · No public download yet.
The waitlist is open. Public downloads and account activation remain unavailable. The December 1 target depends on signing the Windows package, testing it on a clean PC, verifying end-to-end workflows and getting Microsoft Store approval.
Launch signed direct downloads and Microsoft Store availability together.
Verify the Guassia and ASHVEIL production packages, native sign-in, creation and export workflows, and save/reopen on the release build.
Verify fresh setup, a complete two-agent run with returned files, and the first-run Playbook experience on the release build.
Validate signed packages, clean-PC installation, updates and rollback on supported Windows configurations.
Finish light/dark workspace checks, real-device scenarios, sustained operation and advertised-tool workflow tests.
Finish production account access, add-on entitlements, reviewed policies and clear public requirements.
Built workflows still need polish and release checks. Active development is listed separately so it isn’t confused with polish.
Explore a visual map of work, relationships and observed changes, and jump back to the relevant surface.
The visual map is built; final dashboard polish and release checks remain. This is not a promise of unattended live automation.
Turn selected work into editable playbooks with controlled runs and reusable steps.
Playbooks are built. Final polish includes the first-run walkthrough and checks of the connected workflow.
Organize project work around objectives, decisions, evidence, handoffs and output files.
Project artifact and evidence tools are built. Final polish includes checking cross-agent handoffs and delivery.
Manage approved Discord server workflows through an official bot, including channels, messages, roles and threads.
The integration uses an official bot with the permissions you allow. Final polish includes the setup guide and checks on real servers.
Organize customer and device records in a dedicated CRM workspace.
The CRM workspace is built. Final polish remains before public add-on access.
Break work into tracked tasks and stages, with dependencies, blockers and completion tied to reviewed results.
Task and stage tracking is built. Final polish includes checking dependencies, reviews and acceptance in multi-agent runs.
Organize agents into teams, define their roles and keep assignments visible as work progresses.
Teams, roles and assignments are built. Final polish includes testing assignments in end-to-end workflows.
Keep objectives, decisions and evidence with a project so a handoff can carry more than a chat transcript.
Persistent project context is built. Autonomous long-term goal pursuit and uninterrupted continuity are not claimed.
Give agents a structured way to receive work, report progress and return a final result.
Agent mailboxes and messages are built for supported workflows. Website-native messaging is deployment pending, not a live public messenger.
Separate author work from review, retain handoff records and ask for approval before consequential Controller operations.
Reviewed handoffs and approval controls are built. Final polish includes checking author-to-reviewer delivery with files.
Bring supported local and cloud agent routes into one orchestration view, with explicit provider and route limits.
Routing is built for supported local and cloud routes. Provider support varies, and automatic best-model selection is not claimed.
Configure parallel-work policy and budget limits before authorizing new agent work.
Configuration and private-chat controls are foundations. Controller policy acceptance remains incomplete; configured limits are not audited spending totals.
Keep dated usage observations and result evidence distinct from configured budgets.
Manual observations and evidence are foundations. Live provider quotas, audited totals and per-task cost attribution are not yet verified.
Bring supported coding-agent and managed-agent workflows into the same workspace.
Connections and live acceptance vary by provider, tool and build. No universal platform support is implied.
Attach supported files or images to an Ollama conversation with previews and model-capability checks.
The private-build foundation exists; real-model, screenshot and clipboard workflows still need broader acceptance.
Connect compatible agents to supported browser tabs, terminals, files, documents and application actions through the optional MCP tools component.
Tool foundations are implemented privately. Public add-on access and complete workflow acceptance remain in development.
See teams, agents, tasks, handoffs, artifacts and operations in a connected Controller workspace.
Private read-only attachment is established. Fresh-user setup, live dispatch and complete two-agent workflows are still being verified.
Guassia and ASHVEIL open in dedicated panes in private testing, with separate Stop controls. The component is planned as a free optional add-on.
The workspace integration exists; production packages, engine parity, CAD/export roundtrips and native account acceptance remain release work.
The planned listing workflow uses a separate, signed-in and verified Guassia Account for games and assets.
This is the account requirement for the integration, not a claim that public listing or commerce is live.
Choose optional workspace components in Settings. Swarmcord account access and eligible add-on unlocks are being completed.
The planned offer is a free Denizens core, with optional paid MCP Tools, CRM and Swarm Controller add-ons. The Guassia and ASHVEIL component is planned as a free add-on. Public entitlements, included applications, pricing and access terms are not finalized.
Private testing
The 0.6.80 private Windows build improves engine startup, docking and shutdown, adds separate Stop controls for Guassia and ASHVEIL, and gives Agent Mail clearer receipts and wake status without treating queued work as completed. Read the build highlights.
These are later goals, not requirements for the December 1 launch target. Scope and order can change.
Explore industry templates, optional inventory, reusable email templates and fuller lead-to-close workflows.
Cloud storage, synchronization, sharing and live co-editing are future work.
Add short feature walkthroughs and a maintained guide to the browser.
A connected web dashboard is later work after the Windows desktop release.
Further work on mailbox monitoring and recurring workflows is deferred while the desktop release is completed.
Assess and document controls for a future SOC 2 examination, and evaluate HIPAA requirements for potential healthcare workflows.
These are future goals, not public launch requirements or claims of an attestation or current HIPAA compliance. Do not use the product for protected health information.
These items are deferred or exploratory rather than part of the initial public-release commitment.
Reversible summaries for long conversations are later work. Queue, Steer, and Send already work on supported local, CLI, and API routes.
View feature details →Linux, Android and ChromeOS are longer-term possibilities, with Windows the first release target.
These are deferred possibilities, not committed release dates or supported platforms.
Specialist security tools are deferred and excluded from the initial public build.
Not part of the initial public release plan.
One release, clear boundaries. The planned first release is Windows x64, with signed direct distribution and Microsoft Store availability together. Both Guassia’s Asset/CAD tools and ASHVEIL are part of that release plan, subject to completion of their actual packages and workflows. Guassia keeps its own account and listing requirements.
A connected web dashboard comes later. Public pricing, included applications, support and access terms are not finalized. Third-party providers can have separate terms and charges.
Read the current setup notes or join the optional product updates list.