Add AutoPilot mode + multi‑channel integrations

[WilsonHeres]

Describe the feature or problem you'd like to solve

Copilot CLI to operate semi‑autonomously (like Clawdbot/Moltbot) and be reachable via Teams/WhatsApp/Discord/etc while remaining secure and opt‑in.

Proposed solution

• Add copilot autopilot command group to install/start a background daemon and a /autopilot interactive mode

• Local IPC (localhost HTTP/WS or local socket), approval gates, tool allowlists, sandbox for non‑main sessions

• Channel connectors via MCP/plugin interface; initial adapters: Microsoft Teams, Discord, Slack, WhatsApp, Telegram, Google Chat, Signal, iMessage, etc.

  How will it benefit GitHub Copilot CLI and its users?

  • Hands‑free multi‑channel assistant while preserving explicit‑approval safety
  • Long‑running workflows and monitoring without leaving the CLI
  • Extensible integration surface for community‑built connectors

Example prompts or workflows

• "Autopilot, triage new Discord messages and open GitHub issues when bugs are reported"
• "Listen on WhatsApp for on‑call keywords, run diagnostics, and ask me before applying fixes"
• "From Slack, summarize last 24h PR activity and draft a status update"
• "From Teams, answer repo setup questions and link relevant docs"
• "From Telegram, run the release checklist and pause for approvals"

Additional context

No response

[marpisco]

Apparently this was added. I just saw copilot mode when cycling through modes just now.

[Perdolique]

Version 0.407 now has autopilot mode.

[harounhajem]

Apparently this was added. I just saw copilot mode when cycling through modes just now.

It might be a stealth release? Would like to have had some documentation regarding this

[Perdolique]

Apparently this was added. I just saw copilot mode when cycling through modes just now.

It might be a stealth release? Would like to have had some documentation regarding this

I'm not sure GitHub Copilot CLI has documentation at all. New features are added quite often, a few times a week and the best way to get in touch I've found is by reading changelogs. Changelogs are also available right in the app (/changelog command).