← Back to OS AI HistoryHonor MagicOS

Honor MagicOS AI History

A China-source history tracing MagicOS from its platform-level AI foundation through intent-based interaction, MagicLM, YOYO Agent, cross-application execution, and a self-evolving agent OS.

4 formal versionsOfficial sources prioritized

Timeline scope: The formal sequence covers MagicOS 7 through 10. Magic UI remains predecessor context and is not included as a formal version in this history.

Evidence levels show how strongly the currently linked material supports a record. They do not rate product quality or general availability.

System lineage

MagicOS 7 is the starting point; Magic UI remains predecessor context

Honor described MagicOS 7 as a strategic move from UI to OS. This history therefore begins at MagicOS 7, keeps Magic UI as background only, and does not characterize the transition as a simple rename.

View sources1 official records

[1]HonorHonor launches MagicOS 7 in China

Part 1 · Platform foundation

MagicOS 7: platform-level AI foundation

Magic Live, MagicRing, and personalized scenario services established the starting point for the formal MagicOS sequence.

Official ReleaseEvidence · High

MagicOS 7

Platform-level AI foundation

Nov 22, 2022

MagicOS 7 established Honor's formal OS sequence around platform-level AI, personalized services, and cross-device collaboration.

New in this version

Magic Live scenario intelligence

Magic Live used context and user needs to surface personalized service suggestions in documented scenarios. [1]

MagicRing cross-device coordination

MagicRing coordinated supported devices and services around user activity as part of the platform-level intelligence layer. [1]

Starting point

This is the starting point of this formal sequence; no earlier release in this history is compared.

Release, sources & limits1 milestone · 1 source

Release path

Official ReleaseNov 22, 2022
Honor introduced MagicOS 7 in China on November 22, 2022. [1]

Sources

[1]HonorHonor launches MagicOS 7 in China

Evidence limits

MagicOS 7 is the first formal entry in this history; Magic UI is predecessor context rather than a comparison version.
The official launch describes platform positioning and examples, not independent testing across every eligible device.

Part 2 · Intent to agents

MagicOS 8–10: intent recognition to self-evolving agents

The selected China records document intent-based interaction, MagicLM, Magic Portal, YOYO Agent, cross-application execution, and an expanding agent architecture.

Official ReleaseEvidence · High

MagicOS 8

Intent-based interaction and MagicLM

Jan 10, 2024

MagicOS 8 added MagicLM and intent-based interaction so supported system services could respond to richer language, screen, and gesture context.

New in this version

MagicLM on-device model

Honor introduced a 7-billion-parameter on-device MagicLM model as part of MagicOS 8's platform-level AI architecture. [1]

Intent-based interaction

The release used intent recognition to move beyond command-style interaction toward predicting supported user needs. [1]

Multimodal Magic Portal

Magic Portal interpreted selected language, images, gestures, and gaze context to suggest or open supported services. [1]

Compared with the previous version

MagicOS 8 made MagicOS 7's platform intelligence more explicit through MagicLM, intent recognition, and multimodal service routing with Magic Portal. [2][1]

Release, sources & limits1 milestone · 2 sources

Release path

Official ReleaseJan 10, 2024
Honor introduced MagicOS 8 in China on January 10, 2024. [1]

Sources

Evidence limits

Model size and launch examples do not independently establish accuracy, latency, or availability across every MagicOS 8 device.

Official ReleaseEvidence · High

MagicOS 9

YOYO Agent and cross-app execution

Oct 23, 2024

MagicOS 9 introduced YOYO Agent and expanded supported task execution across applications, alongside a broader MagicLM family and agent ecosystem.

New in this version

YOYO Agent

Honor introduced YOYO Agent as a system assistant designed to understand requests and complete supported multi-step tasks. [1]

Cross-application execution

The release described task execution across supported applications and services rather than stopping at recommendations or app opening. [1]

MagicLM family and agent ecosystem

MagicOS 9 expanded MagicLM into a model family and introduced an agent-store direction for supported ecosystem capabilities. [1]

Compared with the previous version

MagicOS 9 extended MagicOS 8's intent recognition and service routing into YOYO Agent and supported cross-application task execution. [2][1]

Release, sources & limits1 milestone · 2 sources

Release path

Official ReleaseOct 23, 2024
Honor introduced MagicOS 9 in China on October 23, 2024. [1]

Sources

Evidence limits

Cross-application execution is limited to supported applications, services, devices, and rollout stages described by Honor.

Official ReleaseEvidence · High

MagicOS 10

Self-evolving agent OS

Oct 15, 2025

MagicOS 10 advanced Honor's agent architecture toward a self-evolving OS with YOYO perception, execution, system-level connections, and a wider agent ecosystem.

New in this version

Self-evolving agent OS

Honor positioned MagicOS 10 as a self-evolving agent operating system that could adapt supported services around user context. [1]

YOYO perception and execution

YOYO combined visual understanding with supported system actions so it could move from seeing a task context to executing documented steps. [1]

System and ecosystem agent connections

The release described system-level MCP connections and a broader set of supported ecosystem agents and services. [1]

Compared with the previous version

MagicOS 10 expanded MagicOS 9's YOYO Agent and cross-app execution into a broader self-evolving architecture with deeper system and ecosystem connections. [2][1]

Release, sources & limits1 milestone · 2 sources

Release path

Official ReleaseOct 15, 2025
Honor introduced MagicOS 10 in China on October 15, 2025. [1]

Sources

Evidence limits

Self-evolving and ecosystem-scale descriptions are vendor architecture claims, not independent proof of arbitrary task completion.
Available agents, MCP connections, and execution steps depend on supported devices, services, applications, accounts, and later updates.

Evidence limits

How to read this history

This history uses selected official Honor China pages and excludes overseas feature sets and global rollout timing.
Feature access can vary by device, system subversion, application version, account, staged rollout, and later product changes.
Honor's release descriptions are vendor claims, not independent product tests or proof that every listed capability worked identically on every supported device.