AI Coding Assistants — 2026-03-28

Official Releases & Updates

GitHub Copilot — Merge Conflict Resolution via @copilot Mentions

GitHub's Copilot coding agent gained the ability to resolve merge conflicts directly on pull requests. Developers can now mention @copilot in a PR comment with a plain-language instruction — for example, @copilot Merge in main and resolve the conflicts — and the agent will handle it autonomously. This removes one of the most tedious manual steps in collaborative development workflows.

GitHub Copilot — Interaction Data Usage Policy Change

GitHub announced a significant privacy policy update: starting April 24, 2026, interaction data from Copilot Free, Pro, and Pro+ users — including inputs, outputs, code snippets, and associated context — will be used to train and improve GitHub's AI models. Users can opt out, but the change is opt-out rather than opt-in, which may prompt enterprise and privacy-conscious developers to review their settings.

LaunchDarkly — Agent Skills Integration for Claude Code, Cursor, and Windsurf

LaunchDarkly published a developer guide (2 days ago) showing how to install its Agent Skills in Claude Code, Cursor, or Windsurf to create AI Configs from natural language. The tutorial walks through building a three-agent pipeline wired to LangGraph — a concrete example of how feature flag platforms are embedding themselves into agentic coding workflows.

6 sources

dev.to

dev.to

media2.dev.to

media2.dev.to

dev.to

dev.to

github.blog

Ask @copilot to resolve merge conflicts on pull requests - GitHub Changelog

github.blog

Updates to GitHub Copilot interaction data usage policy - The GitHub Blog

github.blog

GitHub Copilot in Visual Studio — November update - GitHub Changelog

Developer Community Pulse

Fresh community discussions from the past 48 hours are sparse in the research data. The most recent community results fall outside the strict 24-hour window. The GitHub Copilot interaction data policy change (announced 3 days ago, effective April 24) is the item most likely to generate discussion this weekend — developers who care about privacy will want to check their opt-out settings before the deadline.

No community discussions published after 2026-03-26 with verifiable timestamps were available in the research data for this section.

Benchmarks & Comparisons

No new benchmark publications with a verifiable post-2026-03-26 date were available in the research data. The most recent benchmark-focused sources found were published 2–3 weeks ago, which fall outside the freshness window for this issue.

No recent data available for pricing or tier changes within the past 24 hours.

What to Watch Next

1. Copilot interaction data opt-out deadline (April 24, 2026) — With GitHub's new training data policy taking effect in less than a month, expect heated community discussion over the coming days about how to opt out and what the practical implications are for enterprise customers and open-source contributors. Watch the GitHub blog and developer forums for follow-up guidance.

2. Agentic pipeline integrations gaining traction — The LaunchDarkly tutorial signals a broader trend: third-party developer tools are increasingly publishing "how to plug into your AI coding agent" guides for Claude Code, Cursor, and Windsurf simultaneously, treating all three as first-class deployment targets. Watch for similar integrations from observability, CI/CD, and secrets management vendors in the coming weeks.

Reader Action Items

• Check your Copilot privacy settings now. If you use Copilot Free, Pro, or Pro+, GitHub's new interaction data training policy takes effect April 24. Visit your GitHub account settings to opt out before the deadline if you do not want your code inputs and outputs used for model training.

• Try the new @copilot merge conflict resolver. If you have an open pull request with merge conflicts, drop a @copilot comment in the PR and let the agent attempt resolution autonomously — a quick way to evaluate the new feature on a real codebase this week.