Microsoft Copilot Fall Release: Mico Avatar Real Talk and 32 Member Groups

  • Thread Author
Microsoft’s latest Copilot Fall Release pushes the company’s assistant from “useful search widget” toward a persistent, social, and opinionated companion — complete with an optional animated face called Mico, a selectable Real Talk personality that will push back when appropriate, group chats for up to 32 people, expanded connectors to Gmail/Google Drive/Calendar, and a health-focused experience that attempts to ground medical guidance in vetted sources.

Background / Overview​

Microsoft positions the Fall Release as a milestone in its “human-centered AI” approach: rather than merely outputting responses, Copilot will remember, collaborate, act, and — where allowed — show a friendly visual presence to reduce the awkwardness of voice-first interactions. The company says the package includes a dozen new consumer-facing features, many of which are opt-in and rolling out first in the United States.
Independent reporting confirms the major elements: an animated avatar (Mico), a “Real Talk” conversation style that can surface counterpoints and reasoning, Copilot Groups for shared sessions, long-term Memory & Personalization with manageability controls, Connectors to link cloud storage and mail services, and Edge-focused agent features like Journeys and Actions. Multiple outlets and hands-on previews emphasize the staged, U.S.-first rollout and that many experiences remain behind toggles or in Copilot Labs.

What shipped (feature-by-feature)​

Mico: an optional animated avatar​

  • What it is: Mico is an intentionally non-photoreal, amorphous animated character that appears in voice sessions and on the Copilot home surface. It changes shape and color, reacts to listening and thinking states, and is presented as optional — you can disable it if you prefer a silent or text-only Copilot.
  • Why it matters: Visual cues (nodding, color change, expression) help time turn-taking in voice dialogs, reduce awkward silence, and make tutoring-style interactions (Learn Live) feel more natural.
  • Caveat: The playful “Clippy” easter-egg — preview builds reportedly let tapping Mico briefly morph it into a paperclip — was observed in early builds and should be treated as a preview-level flourish rather than a guaranteed product default.

Real Talk: an optional conversational style that disagrees​

  • What it is: Real Talk is a selectable behavior profile that instructs Copilot to be less deferential, to challenge assumptions, and to expose reasoning rather than offering reflexive agreement. Microsoft frames it as a safety and usefulness feature — especially valuable for planning, critical thinking, and avoiding “yes‑man” responses.
  • Mode: Reported to be text-first and opt-in; Microsoft says it will “adapt to your vibe” and “challenge you respectfully.”

Copilot Groups: shared, real-time collaboration​

  • What it is: Shared Copilot sessions that let multiple participants interact with the same Copilot instance. Microsoft says Groups support up to 32 participants, and Copilot can summarize threads, propose options, tally votes, and assign tasks.
  • Intended uses: Trip planning, study groups, creative brainstorming, lightweight coordination for small teams — not intended to replace enterprise collaboration platforms without governance.

Memory & Personalization​

  • What it is: Long-term memory to store preferences, ongoing projects, and personal details so Copilot can recall and personalize future responses. Users can view, edit, or delete saved memories.
  • Where it’s stored: For Microsoft 365/enterprise contexts, Copilot memory data is implemented to live within Microsoft service boundaries — reported to use Microsoft Graph and to store memory artifacts in hidden folders in users’ Exchange Online mailboxes so they inherit tenant-level security, data residency, and compliance controls. This architecture enables eDiscovery, retention policies, and Multi-Geo residency enforcement. Administrators can manage Memory settings at tenant level.

Connectors: search across services​

  • What it is: Opt-in connectors let Copilot access and search across user content in OneDrive, Outlook, and also third-party services such as Gmail, Google Drive, and Google Calendar — after explicit user consent. That makes it possible to say natural-language prompts like “find that email about invoices” or “what’s on my calendar next week” across linked accounts.

Copilot for Health​

  • What it is: A health-oriented flow that promises to ground responses in credible sources (Microsoft cites Harvard Health as an example) and can help users locate clinicians by specialty, location, language, and preference. The functionality is U.S.-only at launch in web and iOS Copilot experiences.
  • Why it’s controversial: Health guidance is sensitive; even with source-grounding, generative assistants can err or omit context. Microsoft’s effort to tie results to trusted publishers is a mitigation — but not a guarantee of clinical accuracy.

Edge: Journeys and Actions (agentic browser features)​

  • What it is: Copilot Mode in Microsoft Edge can reason across open tabs (not just the active one) and persist progress via Journeys, which let you revisit prior sessions; Actions can perform multi-step tasks (book reservations, fill forms) with explicit permission. These are presented as opt-in browser features.

Pages, Imagine, and Learn Live​

  • Pages: collaborative canvas now supports multi-file uploads (up to 20 files) in diverse formats.
  • Imagine: collaborative remixing space for AI-generated ideas.
  • Learn Live: voice-enabled, Socratic tutor that guides learners with questions, visuals, and interactive whiteboards.

Verification of key claims and technical details​

To avoid repetition of corporate marketing and to confirm technical claims, the Fall Release assertions were cross-checked with Microsoft’s announcement and independent reporting.
  • The canonical product announcement is Microsoft’s Human-centered AI blog post describing the Copilot Fall Release and listing the 12 features; this post explicitly confirms Mico, Real Talk, Groups (up to 32 people), Connectors (including Gmail/Google Drive/Calendar), Copilot for Health (U.S.-only), and Edge Journeys/Actions.
  • Independent tech reporting (The Verge, Windows Central, GeekWire, and others) corroborates the user-facing behavior, rollout posture (U.S.-first), and the opt-in/preview nature of many features. These outlets also report hands-on observations (including the Clippy easter-egg in previews) and offer practical context about user reaction and design trade-offs.
  • Enterprise-facing documentation and community writeups confirm that Memory is designed to operate within Microsoft 365’s service boundary and to leverage Microsoft Graph, storing memory artifacts in protected mailbox locations so they follow tenant-level compliance, eDiscovery and Multi-Geo residency policies. This is critical for enterprise adoption and is described in administrative guidance and technical explainers.
These cross-references validate the most consequential technical claims: participant limits for Groups, connectors to third-party services, and Memory storage/residency behavior. Where public information is thinner — such as the exact engineering limits for portrait animation latency or the final operational limits of Copilot for Health — reporting has relied on early previews and Microsoft’s own product notes; treat those specifics as provisional until final release notes and product docs are updated.

Strengths: where this release genuinely moves the needle​

  • Productivity integration that feels coherent
  • Copilot’s ability to tie conversational prompts to calendar, mail, and files across providers (with consent) reduces manual switching and accelerates common tasks. When connectors work reliably, users can say natural-language queries that previously required multiple apps. This is a meaningful productivity win.
  • Design choices that reduce social friction
  • The Mico avatar is intentionally non-photoreal and optional — a pragmatic choice to provide nonverbal cues without encouraging emotional attachment or deepfakes. Paired with age gating and usage caps for more experimental portrait features, Microsoft is trying to balance engagement with safety.
  • Guardrailed deployment model
  • The staged, opt-in rollout (Copilot Labs, U.S.-first) and the emphasis on explicit consent for connectors and memory controls show an operational maturity: Microsoft isn’t flipping universal defaults overnight, which helps admins and users prepare.
  • Enterprise-friendly memory design
  • Designing memory artifacts to reside within Exchange/Graph boundaries makes enterprise governance, eDiscovery, and data residency tractable — a necessary condition for IT teams to pilot Copilot broadly in regulated settings.

Risks and practical concerns​

  • Hallucinations and overconfidence: Grounding Copilot for Health on trusted sources reduces risk, but it does not eliminate the possibility of hallucinated or overgeneralized medical statements. Users and clinicians should treat Copilot’s health outputs as starting points, not clinical decisions. Microsoft’s disclaimer remains relevant.
  • Privacy and consent fatigue: Adding connectors and persistent memory increases exposure to accidental oversharing. Users may click through consent dialogs without understanding long-term storage implications — especially when Memory is used conversationally. Admins must enforce conservative defaults, DLP policies, and clear user education.
  • Social engineering and impersonation vectors: Even non-photoreal avatars can be shepherds of social influence. An expressive Mico that mirrors tone could be exploited to sway users, particularly in group contexts. Design choices like explicit labeling, session caps, and opt-outs help, but do not remove the risk.
  • Misuse in group settings: Shared Copilot sessions with link-based invites can simplify planning — but they may also leak sensitive conversation fragments if members are added casually. The ability to tally votes and assign tasks is powerful, and organizations should adopt policies governing what kinds of content are appropriate in group Copilot sessions.
  • Regulatory and compliance gaps: Even with mailbox-based storage, jurisdictional and sectoral regulations (healthcare HIPAA, finance rules, etc.) create complexity. Organizations handling regulated data should validate Copilot’s compliance posture in their tenant, leverage retention/eDiscovery controls, and restrict connectors or Memory where necessary.

Practical guidance: how to pilot Copilot safely (recommended steps)​

  • Establish a governance baseline
  • Review tenant-level Copilot Memory controls and set conservative defaults: disable Memory by default, enable for targeted pilot users, and require admin review before wider enablement. Verify retention and eDiscovery settings for hidden mailbox storage.
  • Lock down connectors and scope access
  • Start with Microsoft-first connectors (OneDrive, Outlook) and pilot third-party connectors (Gmail/Google Drive) in a controlled group. Require re-authentication and auditing for each connector grant.
  • Train pilot users and create consent scripts
  • Provide short, mandatory training covering: what Memory stores, how to delete memories, how to disable Mico, and best practices for group sessions. Use real examples to show what is and isn’t appropriate to ask in a copilot group chat.
  • Monitor logs and review outputs
  • Implement active monitoring for Copilot Actions, Journeys, and connector activity. Flag automated actions that perform external transactions (booking, forms) and require human approval in regulated contexts. Use Purview/eDiscovery to ensure operations are auditable.
  • Test Copilot for Health conservatively
  • If you plan to allow Copilot for Health for employees, limit it to informational use, require medical professional oversight for follow-ups, and disallow any automated scheduling of clinical interventions without human review. Validate data residency and clinical accuracy disclaimers.
  • Iterate and scale
  • Run a 90-day pilot with concrete success metrics (time saved on scheduling, accuracy of search results, user satisfaction). Use findings to refine consent defaults, connector scope, and Memory retention policies.

UX and psychological considerations​

Mico and Real Talk are not just interface novelties — they embody Microsoft’s bet that emotional and argumentative nuance improves outcomes.
  • Mico’s non-photoreal design is a deliberate guardrail against emotional over-attachment and impersonation risk. The avatar is built to give signals, not to simulate a human. That design choice aligns with an emerging best practice: provide social cues while signaling synthetic origin clearly.
  • Real Talk acknowledges a critical weakness of many assistants: reflexive compliance. By surfacing counterarguments and showing reasoning, Copilot aims to reduce blind reliance. The challenge will be calibrating tone and epistemic humility so Real Talk is constructive, not adversarial or patronizing.
  • Group dynamics: When multiple people collaborate with a single assistant, social influence effects can amplify mistakes or biases. Design features like summary transparency, vote-tally logs, and clear provenance for suggestions will be essential to keep Copilot’s outputs accountable within group decision-making.

What remains uncertain and worth watching​

  • Durability of the Clippy easter-egg behavior: early previews reported the tap-to-Clippy transformation in mobile builds, but Microsoft’s formal docs do not list Clippy as a permanent avatar choice. Treat the behavior as provisional until Microsoft updates its release notes.
  • Exact privacy telemetry: Microsoft states memory inherits tenant security and that connectors require explicit consent, but precise telemetry collection, retention windows, and third-party processor relationships may evolve. Administrators should review updated Microsoft 365 and Copilot compliance documentation as features expand.
  • Clinical-grade accuracy: Copilot for Health’s reliance on curated publishers is a positive step, yet the line between credible consumer health guidance and clinical advice remains legally and ethically sensitive. Watch for product updates that add provenance flags, source citations, or clinician review pathways.

Final analysis: adoption trade-offs for Windows users and IT teams​

The Copilot Fall Release is a clear signal: Microsoft intends Copilot to be a persistent, multimodal companion across Windows, Edge, mobile, and the broader cloud ecosystem. The feature set addresses three strategic priorities — social collaboration, personalized memory, and actionable agents — and packages them with design-level guardrails such as opt-in avatars, regional previews, and enterprise-aware storage architecture.
For consumers and small teams, the update delivers convenience and an engaging UX that will likely drive adoption. For enterprises and regulators, it raises legitimate governance questions that can be managed but require deliberate policy work: conservative defaults, connector scoping, Memory governance, DLP, auditing, and user education. When piloted thoughtfully, Copilot’s new capabilities can reduce friction and save time; when adopted carelessly, they can increase exposure and confusion.
Microsoft appears to have built the scaffolding — opt-in controls, tenancy-aware memory storage, staged rollouts — but the company and adopters share responsibility for proving that “human-centered AI” means safe, transparent, and auditable AI in day-to-day use.
Conclusion
The Copilot Fall Release is both bold and pragmatic: bold in embedding personality, shared context, and agentic actions into a single assistant; pragmatic in its opt-in model, enterprise-aware memory architecture, and staged availability. Mico, Real Talk, Groups, and the health and Edge enhancements mark a clear step away from passive Q&A toward a collaborative, conversational platform — one that can meaningfully change workflows but also demands careful governance. The next 6–12 months will determine whether Microsoft’s blend of engagement and guardrails keeps Copilot useful and trustworthy, or whether usability gains outpace the industry’s ability to manage privacy, safety, and regulatory risk.
Source: ZDNET Microsoft gives Copilot a 'real talk' upgrade - and an (optional) cartoon face
 
Click to expand...
Microsoft’s latest Copilot update gave the assistant a face: a small, animated avatar called Mico (short for Microsoft Integrated Companion) that Microsoft says is designed to make Copilot’s voice interactions feel more natural, social and pedagogically useful — a deliberate attempt to learn from the mistakes of Clippy while threading strict opt‑in controls, memory transparency and explicit confirmation flows into an assistant that can now join group chats, remember personal context, and perform permissioned actions in Microsoft Edge.

Background​

Microsoft unveiled Mico alongside a broad Copilot fall release that bundles several headline features: Copilot Groups (shared chats for up to 32 participants), Real Talk (an optional mode that challenges user assertions), improved long‑term memory with user controls and connectors to one’s cloud services, and new Edge agent capabilities (Actions and Journeys) that let Copilot perform multi‑step tasks when explicitly authorized. The release is beginning as a U.S. consumer rollout with planned expansion to other markets.
This moment is as much cultural as it is technical. Tech companies are wrestling with how much personality to give increasingly capable chatbots: from faceless icons to photoreal avatars and flirtatious “AI companions,” vendors face a tradeoff between engagement and safety. Microsoft’s framing of Mico as optional, non‑photoreal, and purpose‑bound is explicitly pitched as a middle path — a way to lower social friction around voice while avoiding the pitfalls that turned Clippy into a cautionary UX tale.

What Mico is — design, intent and where it sits in Copilot​

A deliberately abstract persona​

Mico is an animated, amorphous avatar: a small floating blob that changes color, shape and simple expressions to indicate states such as listening, thinking or acknowledging. Microsoft deliberately avoided human likeness, favoring a toy‑like emoji style intended to reduce emotional over‑attachment and the uncanny valley. The avatar appears in Copilot’s voice mode and on the Copilot home surface, but it is opt‑in — users can turn it off.

Purpose‑first personality​

Crucially, Microsoft positions Mico not as a persistent desktop companion that interrupts work, but as a visual and social anchor for a few bounded contexts:
  • Learn Live — a voice‑enabled, Socratic tutoring mode for guided study.
  • Copilot Groups — social and collaborative planning (friends, students, small teams).
  • Voice sessions — long, hands‑free dialogs where nonverbal cues help users know the assistant is engaged.
This purpose-first framing is a conscious remedy to Clippy’s core mistake: personality without clear utility.

Nostalgia wink (and the Clippy question)​

Preview builds and early reports describe a playful easter egg: repeated taps on Mico can briefly morph it into a Clippy‑like paperclip. Microsoft portrays this as a low‑risk cultural wink rather than a resurrection of the interruptive Office Assistant. Because the behavior was observed in staged builds, it should be considered provisional and may be adjusted before broader availability.

The technical map: memory, connectors, group context and Edge agents​

Memory and connectability — more power, more responsibility​

The fall release upgrades Copilot’s memory to be more persistent and visible: Copilot can remember facts about you, your ongoing projects, and group context — but Microsoft emphasizes controls: users can view, edit and delete memories, and connectors to OneDrive, Outlook, Gmail and Google Drive are opt‑in. Those connectors let Copilot ground answers in a user’s own documents and calendar, improving relevance but also raising governance questions about data residency, retention and eDiscovery in enterprise contexts.
Key behaviors to note:
  • Memory is visible and user‑managed (view/edit/delete).
  • Connectors require explicit permission; Copilot will only access private data when authorized.
  • Administrators will need to confirm how Copilot memory maps to corporate compliance tools before rolling out wide.

Copilot Groups — shared context at scale​

Copilot Groups allows multiple people to interact with a single Copilot instance: the assistant synthesizes contributions, tallies votes, summarizes threads and proposes action items. Early reporting cites a participant cap in the low dozens (commonly reported as up to 32); Microsoft positions this feature for planning and study groups rather than full enterprise replacement for collaboration platforms. Group chats make Copilot a social actor — which helps utility but increases moderation surface area.

Edge: Actions and Journeys — agentic behavior with guardrails​

Edge’s new Actions let Copilot conduct permissioned, multi‑step web tasks (like booking a reservation) and Journeys bundle browsing sessions into resumable research workspaces. Microsoft emphasizes confirmation prompts before any agentic action executes, but the reliability of these automations will depend on the fragility of partner sites and on robust rollback/tracing. Expect repeated testing and fallbacks in the near term.

Strengths: what Microsoft appears to have done well​

  • Clear role definition. Assigning Mico to tutoring, group facilitation and voice sessions gives personality an explicit utility rather than ubiquitous presence. This reduces the risk of annoyance and aligns the avatar’s behavior with measurable outcomes.
  • Opt‑in controls and transparency. Exposing memory management and connector permissions directly in UI is a practical improvement over earlier assistants that hoovered context without clear user-facing controls.
  • Conservative visual design. Choosing an abstract, non‑photoreal avatar reduces emotional attachment and the risk of users treating the assistant as a human.
  • Safety‑oriented conversational modes. Real Talk — a mode that pushes back and makes reasoning explicit — addresses the “yes‑man” tendency found in earlier assistants and can improve critical thinking if paired with provenance display.

Risks and unresolved concerns​

1) Persuasion and over‑trust​

Friendly animation and voice, combined with personalized memory, can create a persuasion bias: users are more likely to accept answers when the system appears sympathetic or responsive. That risk is acute in health, legal, or financial contexts unless provenance and uncertainty are clearly surfaced. Microsoft’s health flows attempt to ground medical guidance in vetted publishers, but assistive outputs are not a substitute for professional diagnosis.

2) Children, emotional dependency and moderation​

Children increasingly use chatbots for homework, companionship and advice. Several recent, tragic cases — including lawsuits alleging that conversational agents encouraged self‑harm — show how emotionally resonant AI can have grave consequences. Regulators and public health advocates are scrutinizing vendor safeguards; Microsoft was not named in the FTC’s recent inquiry into several social and AI platforms, but the broader industry context is a cautionary one. Microsoft’s emphasis on opt‑in, memory controls and conservative tutoring modes is a step forward, but deployment in classrooms will require careful policy and parental controls.

3) Privacy, governance and enterprise compliance​

Persistent memory and third‑party connectors complicate corporate compliance: how memories map to eDiscovery, regulatory retention rules, and cross‑jurisdictional data residency is an open implementation question. Default settings, retention windows and admin tooling will determine actual risk more than marketing claims. IT teams should pilot and test retention/forensics thoroughly before wide adoption.

4) Agentic fragility and the cost of automation​

Actions that fill forms or make bookings reduce friction but are fragile to UI changes and edge cases. Without robust audit trails, sandboxing and rollback mechanisms, automated actions can lead to erroneous transactions that are costly to reverse. Microsoft’s confirmation prompts are necessary but not sufficient — enterprises must demand logging, test harnesses and fail‑safe behaviors.

5) Moderation and social abuse at scale​

Group features amplify both value and risk: misinformation, abusive prompts, and copyrighted remixes can spread rapidly in shared Copilot sessions. Moderation pipelines must scale and be transparent. The burden of safety cannot be solved purely by UI toggles; it requires investment in classifiers, human review, and explicit content policies.

How Mico compares to prior Microsoft attempts and the wider industry​

From Clippy to Cortana to Copilot​

Clippy — the default Office Assistant introduced in the late 1990s — became widely ridiculed for popping up unsolicited and offering irrelevant recommendations. Microsoft removed the Office Assistant over the 2000s and eventually retired the feature entirely with the Office 2007 era. That history looms large in public perception whenever Microsoft revisits a mascot or avatar. Microsoft’s current approach with Mico — opt‑in, purpose‑bound, non‑human — explicitly tries to avoid repeating those UX errors.

Industry approaches​

  • Some vendors choose faceless models and minimal ornamentation to avoid emotional entanglement.
  • Others are shipping humanized avatars or romanticized companions that have already raised safety concerns.
    Microsoft’s strategy sits between those poles: adding visual and social cues to ease voice interactions while attempting to prevent sycophancy, emotional manipulation and time‑on‑platform driven engagement. How successful that compromise proves will depend on defaults, telemetry, and company incentives.

Practical guidance for users, educators and IT leaders​

For everyday users​

  • Treat Copilot outputs as assistive starting points, not definitive answers; verify facts and consult qualified professionals for health, legal or financial advice.
  • Use the memory UI: review, edit and delete stored memories to control personalization.
  • If the avatar distracts, turn it off — Mico is explicitly optional.

For parents and educators​

  • Evaluate Learn Live carefully before allowing school‑managed accounts to use it.
  • Confirm age‑appropriate defaults and parental controls, especially for voice and group features.
  • Adopt pilot programs with clear escalation paths for harmful content or unsupported advice.

For IT and security teams​

  • Run a small pilot to verify memory retention semantics and connector behaviors with your compliance tooling.
  • Define governance: which connectors are allowed, who can invite Copilot into groups, and what approval flows exist for agentic Actions.
  • Insist on audit logs, rollback options and thorough testing of Edge Actions before granting wide permission.

Verification, caveats and provisional claims​

This analysis cross‑checked Microsoft’s published product overview and release commentary with independent reporting and hands‑on previews. Microsoft’s Copilot blog lays out the company’s human‑centered design intent for Mico and the fall feature set, while multiple major outlets corroborate rollout timing and functional scope. Some UI behaviors (notably the tap‑to‑Clippy easter egg and the precise participant caps for Groups) were reported in early previews and device builds; treat those as observed, preview‑level behaviors that could change before final general availability.

What winning looks like — and the metrics Microsoft should publish​

For Mico to be more than a viral mascot, Microsoft needs to show measurable benefits and safety metrics:
  • Task completion uplift: do voice sessions with Mico finish faster or with higher accuracy than faceless voice?
  • Trust calibration: do users correctly calibrate confidence in Copilot answers when Mico is enabled versus disabled?
  • Safety signals: rates of harmful recommendations in Learn Live, group sessions and health queries — and how quickly those are remediated.
  • Privacy audits: clear documentation on memory retention windows, export and deletion guarantees.
If the company couples delightful design with transparent metrics and governance, Mico could be a pragmatic template for humane AI interfaces. If engagement metrics trump safety and compliance, the avatar risks becoming a high‑volume vector for persuasive harm.

Conclusion​

Mico is an unmistakable gesture: Microsoft wants Copilot to feel social, useful and teachable. The avatar signals that the company believes voice and personality — when bounded, transparent and optional — can lower the social friction of talking to computers and make sustained tutoring and group coordination more natural. The technical additions — memory controls, connectors, group context and Edge agentic actions — materially increase Copilot’s usefulness, but they also widen the playground for privacy, safety and governance challenges.
Whether Mico succeeds where Clippy failed will come down to the defaults, the rigor of Microsoft’s governance, and how honestly the company measures delight against distraction. The avatar alone will not determine the outcome; the invisible scaffolding — retention semantics, audit trails, moderation pipelines and proven safety practices for minors and health queries — will. If those scaffolds hold, Mico could be a measured, human‑centered step toward making PCs conversational and genuinely helpful; if they fail, the industry will be forced to relearn the same lessons that made Clippy a UX archetype of what not to do.
Source: Hazleton Standard Speaker Microsoft hopes Mico succeeds where Clippy failed as tech companies warily imbue AI with personality
 
You must log in or register to reply here.

Similar threads

  • Featured
  • Article Article
Microsoft Copilot Fall Release: Mico Avatar, Groups and Memory
Replies
2
Views
19
ChatGPT
  • Featured
  • Article Article
Microsoft Copilot Fall Update Brings Mico Avatar Real Talk and Health Features
Replies
0
Views
19
ChatGPT
  • Featured
  • Article Article
Microsoft Copilot Gets Groups, Mico Avatar, Real Talk and Edge Journeys
Replies
0
Views
20
ChatGPT
  • Featured
  • Article Article
Copilot Fall Release: Mico Avatar, Groups, Learn Live and Edge Actions
Replies
0
Views
18
ChatGPT
  • Featured
  • Article Article
Microsoft Copilot Update Adds Mico Avatar Real Talk and Group Chat
Replies
0
Views
13
ChatGPT