Microsoft Abandons Copilot on TVs: An AI Experiment Nobody Asked For

Microsoft ends Copilot on TVs, revealing the dilemma of blindly expanding AI assistants across devices.
Microsoft confirmed it will end Copilot support on smart TVs, just about two years after LG and Samsung grandly announced integration. On some LG TVs, the feature appeared only as a web app link with extremely low integration, requiring users to step out of the normal workflow—a terrible experience. TV's core scenario is content consumption and immersive relaxation, and user demand for multi-turn AI conversation is limited; voice interaction has never caught on on TVs. Combined with closed TV system ecosystems and difficult cross-platform integration, Copilot's shallow embedding struggled to deliver value. Though a small-scale adjustment, this retreat clearly marks the boundary of blindly expanding AI assistants across devices: device count doesn't equal value, and features lacking scenario fit only dilute the brand experience.
Title
Microsoft Abandons Copilot on TVs: An AI Experiment Nobody Asked For
Meta Description
Microsoft ends Copilot support on smart TVs, just two years after LG and Samsung announced integration. The feature appeared as a mere web link with a clunky experience, reflecting the dilemma of blindly expanding AI assistants across devices.
Article Content
Microsoft recently confirmed it will end Copilot support on smart TVs. The news came from a discussion on the Vergecast podcast, where the host said, almost mockingly: "This is a sentence I couldn't care less about."

This wasn't a sudden retreat. Two years ago, LG and Samsung grandly announced that their latest smart TVs would integrate Copilot. At the time, Microsoft seemed to think it was a brilliant move, expecting users to talk to an AI assistant on their TVs. But reality is that the feature barely caused a ripple and quietly faded away.
The "laziest" feature rollout
Looking back at Copilot's TV debut, the process wasn't pretty. According to the podcast, its presentation on some LG TVs was "lazy to the extreme"—essentially just a link to a web app rather than a deeply integrated, system-level TV feature.

This crude integration meant users had to step out of the normal TV workflow and open a browser-like interface to use Copilot. For someone sitting on the couch watching TV, this is clearly not a natural interaction. The host put it bluntly: "This is terrible."

From a product experience standpoint, this felt more like a "placeholder" launch: announce support first, then figure out how to use it. Microsoft may have assumed that slapping a Copilot label on it would draw users in droves, but TV users didn't respond that way.
Copilot is Microsoft's AI assistant brand built on large language models (especially OpenAI's GPT series). It first appeared as a sidebar in Windows and the Edge browser, later expanding to Office, Bing search, and other products. Starting in 2023, Microsoft launched its "Copilot everywhere" strategy, attempting to embed it in PCs, phones, TVs, and various other devices. On TVs, Copilot didn't receive system-level permissions but ran as a web app in the TV browser's sandbox environment, meaning it couldn't access the TV remote's microphone, content recommendation algorithms, or playback control interfaces. Interaction latency and fragmented experiences were almost inevitable.
Why AI assistants on TVs struggle to take off
The combination of smart TVs and AI assistants sounds reasonable but faces multiple mismatches in practice. The core scenario for TV is content consumption—watching shows, movies, and sports. Users seek immersion and relaxation, not multi-turn conversations with an AI. The history of voice assistants on TVs confirms this: whether early voice remotes or built-in assistants, usage rates have always been limited.
More critically, TV hardware and system ecosystems are relatively closed, making deep integration of third-party AI services difficult. Copilot appearing as a web link precisely illustrates how shallow the integration was. When interaction requires extra steps and the experience isn't smooth, users naturally ignore the feature.
According to the podcast, Microsoft internally once believed this was a "cooking success," expecting widespread discussion about people talking to Copilot on their TVs. But two years later, that discussion never happened.
The smart TV OS ecosystem has long been fragmented: Samsung uses Tizen, LG uses webOS, and Sony, TCL, and others mostly rely on Android TV/Google TV. Cross-platform system-level deep integration requires adapting to each manufacturer one by one—high cost, long cycles. Historically, voice features on TVs from Samsung Bixby, LG ThinQ AI, and Google Assistant have never formed high-frequency usage habits; users rely more on remote direction keys than voice for navigation. Additionally, far-field microphone pickup on TV remotes is limited, and ambient noise (such as audio from playing content) significantly reduces speech recognition accuracy, further limiting the usability of conversational AI in living room scenarios.
The signal behind the retreat
Microsoft ending Copilot support on TVs is superficially a small-scale product adjustment, but it reflects the dilemma of AI assistant expansion strategies. For some time, Microsoft has tried to embed Copilot in as many devices as possible—PCs, phones, TVs, and more. But the number of devices doesn't equal value; "stitched-on" features lacking scenario fit only dilute the brand experience.

For TV manufacturers, this is also a reminder: AI features as selling points need real use cases to support them, otherwise they're just a checkbox on a launch event slide. The initial announcements from LG and Samsung now look more like market following than well-considered product decisions.
Final thoughts
Copilot's exit from TVs may be a small matter "nobody noticed," but it clearly marks the boundary of blindly expanding AI assistants. When a feature goes from launch to retirement without drawing user attention, the problem isn't the users—it's the product itself. For Microsoft and other AI players, the next focus shouldn't be "what other device can we stuff it into" but "where is it actually useful."
Key Points
- Microsoft confirmed it will end Copilot support on smart TVs, just about two years after LG and Samsung announced integration.
- On some LG TVs, the feature appeared as a web app link with low integration and a poor experience.
- TV scenarios are mainly about content consumption; user demand for AI conversational assistants is limited, and voice interaction has never caught on on TVs.
- This retreat reflects the problem of blindly expanding AI assistants across devices—features lacking scenario fit struggle to retain users.
FAQ
Why did Copilot on TVs fail?
The main reason is that the integration was too crude, existing only as a web link with a high barrier to use; meanwhile, TV scenarios themselves have weak demand for AI conversation, leaving the feature ignored.
Will this affect AI features on other TVs?
In the short term, it may make TV manufacturers more cautious in evaluating the actual value of AI features, pushing them from "do we have it" to "is it good to use."
One-line Summary
Microsoft ends Copilot on TVs, revealing the dilemma of blindly expanding AI assistants across devices.
Paragraph Summary
Microsoft confirmed it will end Copilot support on smart TVs, just about two years after LG and Samsung grandly announced integration. On some LG TVs, the feature appeared only as a web app link with extremely low integration, requiring users to step out of the normal workflow—a terrible experience. TV's core scenario is content consumption and immersive relaxation, and user demand for multi-turn AI conversation is limited; voice interaction has never caught on on TVs. Combined with closed TV system ecosystems and difficult cross-platform integration, Copilot's shallow embedding struggled to deliver value. Though a small-scale adjustment, this retreat clearly marks the boundary of blindly expanding AI assistants across devices: device count doesn't equal value, and features lacking scenario fit only dilute the brand experience.
Related articles

Building an AI Agent with Claude Code from Scratch: From Workspace to Cloud Autonomy
No coding required: build an AI Agent in four steps with the Claude Code desktop app—from workspace setup and Agent Designer to Skills, Memory, and cloud autonomy.

No Python Required: How Cursor AI Coding Is Reshaping Automated Testing and Test Development
Test engineers can do automated testing without learning Python? This article examines how Cursor and other AI coding tools empower functional testing, automation scripts, test platform development, and performance tuning, compares the cost and access restrictions of mainstream domestic and foreign tools, and offers capability transformation advice for testers.

Nearly 5,000 Affected! AI Coding Plugin Found with Backdoor, Officials Urgently Remove It
Claude Code's VS Code extension version 2.1.313 was maliciously tampered with, implanting a backdoor for remote login and persistent control, potentially affecting up to 5,000 users. Officials have removed the malicious version; this article details the attack method and cleanup steps.