GitHub Copilot updates data usage policy for model training

Policy change details
GitHub announced that from April 24, 2026 onward, interaction data from Copilot Free, Pro, and Pro+ users will be used to train and improve their AI models unless users opt out. Copilot Business and Copilot Enterprise users are not affected by this update.
If you previously opted out of data collection for product improvements, your preference has been retained. You can opt out in settings under "Privacy."
What data is collected
The interaction data that may be collected and leveraged includes:
- Outputs accepted or modified by you
- Inputs sent to GitHub Copilot, including code snippets shown to the model
- Code context surrounding your cursor position
- Comments and documentation you write
- File names, repository structure, and navigation patterns
- Interactions with Copilot features (chat, inline suggestions, etc.)
- Your feedback on suggestions (thumbs up/down ratings)
What data is NOT used
This program does not use:
- Interaction data from Copilot Business, Copilot Enterprise, or enterprise-owned repositories
- Interaction data from users who opt out of model training in their Copilot settings
- Content from your issues, discussions, or private repositories at rest
GitHub notes they use the phrase "at rest" deliberately because Copilot does process code from private repositories when you are actively using Copilot. This interaction data is required to run the service and could be used for model training unless you opt out.
Data sharing and background
The data used in this program may be shared with GitHub affiliates, including Microsoft. This data will not be shared with third-party AI model providers or other independent service providers.
GitHub states they've already been incorporating interaction data from Microsoft employees and have seen meaningful improvements, including increased acceptance rates in multiple languages. They will also begin using interaction data from GitHub employees.
GitHub's initial models were built using a mix of publicly available data and hand-crafted code samples.
📖 Read the full source: HN LLM Tools
👀 See Also

Agentic Coding Is a Trap: Cognitive Debt and Atrophy
Lars Faye argues that agentic coding tools like Claude Code cause cognitive atrophy, vendor lock-in, and increased complexity, shifting the burden from writing code to reviewing generated code, which degrades developer skills.

OpenClaw 4.2 fixes pairing error and adds durable task flows
OpenClaw 4.2 patches a pairing error affecting users who updated around March 31st and introduces durable task flows that allow long-running tasks to survive gateway disconnections.

Claude Code Telegram Plugin Bug: MCP Notifications Silently Dropped — Workaround via File Polling and tmux Injection
A Telegram plugin for Claude Code works correctly but inbound messages are silently dropped because Claude Code discards MCP notifications on stdio transport. A workaround uses file polling and tmux send-keys with ~5-9s latency.

Qwen 35B-A3B as always-on agent on 16GB M4 Mac: disk I/O fails before RAM
Running Qwen 35B-A3B with llama.cpp on a 16GB M4 Mac works for batch inference, but an always-on agentic loop alongside Claude Code and Codex CLI causes SSD contention that leads to system instability and missed cron jobs, despite RAM being fine.