Skip to main content
This changelog covers notable changes to the CyberOS platform that affect users and integrators. It highlights user-facing features, protocol amendments, and module status milestones. For the full line-by-line technical history, see the CHANGELOG.md in each module directory in the open-source repository.

​
Checking your installed version

Use cat .cyberos/VERSION in an installed repo to check your installed CyberOS version. The current platform release is 1.0.0 (2026-07-14).

​
Week of 2026-07-20 — Post-1.0.0 Patches

The first week after the 1.0.0 release focused on tightening install/uninstall behaviour and proving the release pipeline end-to-end. No breaking changes; safe to pick up on any 1.0.0 install via cyberos install (see Installation).

​
Fixes

  • Orphaned status hook no longer blocks commits. The leftover pre-commit hook used to fail every commit that touched VERSION, CHANGELOG.md, or docs/tasks/ if you deleted a repo’s .cyberos/ directory without running cyberos uninstall. The hook now warns twice, names both remedies, and exits cleanly. Machines with an intact install are unaffected.
  • Release pipeline verified end-to-end. The 1.0.0 release checklist ran to completion (20/20). The tag → build → publish flow, the GitHub release notes, and the docs-site status page all render from the same corpus. The changelog page is now the source of truth for shipped state.

​
Updates

  • Uninstall is now the inverse of install. cyberos uninstall removes its own MCP registrations, cleans every managed skill link across the Claude, Grok, Codex, OpenCode, and Cursor families, and byte-exactly strips the entries it added to .gitignore and the pre-commit hook. Operator files it never wrote are preserved. See Installation.
  • macOS parity for the developer test suite. The repo’s own test suite now runs on macOS (bash 3.2 + BSD userland) as well as Linux. Contributors on Apple Silicon and Intel Macs can run the full suite locally without a Linux VM. Shipped payload code is unchanged.
Run cyberos version to check for updates. If a newer payload is available, cyberos install re-vendors it in place — no separate apply step.

​
Version 1.0.0 — 2026-07-14

The first stable release of CyberOS. The 1.0.0 designation is deliberate: the 0.x line hardened the governed development machinery end to end. 1.0.0 commits to the engineering-spec@1 task contract and the 10-state task lifecycle as stable interfaces.
  • Stable contracts. engineering-spec@1 and the 10-state task lifecycle are committed stable interfaces. The /create-tasks and /ship-tasks workflows are hardened for multi-repo production use — resumable ship manifests, deterministic queue selection, gate autodetect across 9 language stacks, per-repo config, and audited backlog writes.
  • Visual deliverables. Every task renders to its own CDS-styled page. The status hub (status-hub@2) provides three lenses — board, table, and releases — regenerated from task frontmatter, this CHANGELOG, and the VERSION file on every deploy.
  • Consumer CLI finalised. Commands: install, uninstall, version, status, help. Matching Claude plugin slash commands: /install, /uninstall, /version, /status, /help.
  • Soft update-check. On any .cyberos use, CyberOS checks whether a newer version is available. If stale, it prompts you to run cyberos install to re-vendor.

​
Recent module highlights

Wave 1 — All 6 MUST tasks shipped and strict-audited.
  • SAML SSO with XML Digital Signature verification: Full XML-DSig validation for SAML assertions — strict algorithm allowlist (RSA-SHA256 + SHA-256 + exc-c14n), enveloped-signature stripping, and X.509 certificate verification. Enterprise SSO providers (Okta, Azure AD, Google Workspace) are now fully supported.
  • GeoIP travel policy: Cross-continent velocity detection and geo-velocity anomaly flagging protect all login flows. Administrators can configure per-tenant travel allowlists and suppression windows to reduce false positives for frequent travellers.
  • Admin REST API: Tenant and subject management — list tenants, list subjects, revoke/unrevoke subject access — with cursor-paginated responses and an in-memory JTI deny-list for immediate token invalidation.
Deferred to Wave 3: Redis-backed deny-list for horizontal scale and a structured revoke-reason taxonomy.
All 9 tasks in the MEMORY Wave 2026-Q3 shipped end-to-end with 110+ acceptance criteria covered.
  • put_if precondition-hash writes: New canonical operation that only commits a write if the current content hash matches a supplied precondition. Prevents lost-update races in concurrent multi-agent scenarios.
  • cyberos dream — proposal-mode consolidation: Agents propose memory consolidations; proposals are queued for human review before any write is committed. Proposals are tracked by ID and visible in cyberos history.
  • Per-store ACL: Fine-grained access control on memory subtrees. Denied accesses are emitted as audit rows.
  • Session transcript ledger: Opt-in encrypted session transcripts with full CLI management: cyberos transcript start|append|end|read|list|purge-expired.
  • cyberos history: Read-only per-path history projection with flags for limit, date range, chronological order, and JSON output. Never mutates the store.
  • Desktop app: Tauri 2 desktop application with Dashboard, Search, and Sync tabs. Sync supervisor with automatic restart on failure.
  • 100+ author/audit skill pairs indexed in the CyberOS skill library, covering all 47 active CUO personas.
  • Anthropic Agent Skills open-standard compliance. All skills conform to the SKILL.md contract format, making them compatible with Claude, Codex, Cursor, Goose, Amp, and any Agent Skills-compliant client.
  • cyberskill-vn pack shipped. Six Vietnamese-market skills in production: vietnam-mst-validate, vietnam-bank-transfer (VietQR), vietnam-vat-invoice (hóa đơn), and supporting utilities.
  • Universal-protocol skills. memory-capture@1, memory-sync@1, and synthesis-author@1 form the memory-protocol skill bundle — invocable by any persona that needs to read from or write to BRAIN.
  • Distribution roadmap: R0 (local cache) → R1 (.skill bundles) → R2 (OCI registry) → R3 (agentskills.io citizen) → R4 (own marketplace, gated on ≥50 paying tenants) → R5 (enterprise white-label).
  • 47 active personas, 221+ workflows. Full persona library with consistent naming convention. Every C-role has a dedicated workflow suite.
  • Advanced workflow supervisor. Six handler patterns for complex multi-task scenarios: linear (default), time-critical (SLA-bypass with breach audit), per-instance fan-out, multi-output per-recipient fan-out, sequential approval chaining, and persona-pair interleaved chains.
  • Single-backlog model. The improvement track was merged into the product track. One backlog, one ship-tasks flow.
  • Dream loop (propose mode). cyberos dream ships as a CUO-adjacent command. Agents propose memory consolidations; the loop defers writes until human acceptance.
  • Gate autodetect. Supports Go, JVM, .NET, PHP, Ruby, Rust, Python, TypeScript, Bun. Per-repo overrides via .cyberos/config.yaml.
  • Audited backlog writes. One write path to BACKLOG.md — all state transitions go through the backlog-state-update@2 skill, never direct file edits.
  • Slash commands: /install, /uninstall, /version, /status, /help — full parity with the CLI surface.
  • Claude Code marketplace listing. The CyberOS plugin is listed on the Claude Code marketplace. A .plugin file enables one-click install from Claude Desktop.
  • /status opens the status hub in the default browser, showing the board/table/releases view of the current task corpus.
  • Soft update-check on any .cyberos use. If a newer version is available and the user confirms, install re-vendors the payload. No separate apply path.

​
Module status

For full technical changelogs, see the CHANGELOG.md in each module directory in the open-source repository at modules/<slug>/CHANGELOG.md.