Oleksandr Liubushyn’s Post

🚨 GitHub is training Copilot on your code starting April 24 — and most developers don't even know. This is one of those silent policy updates that flies under the radar until it's too late. Starting April 24, GitHub will use all Free, Pro, and Pro+ Copilot interaction data to train their AI models. That means your code snippets, file names, navigation patterns, comments, and documentation are all going directly into their training pipeline. The kicker? It's opt-in by default. If you don't manually go into your settings and disable it before the deadline, your coding patterns become Microsoft's training data. No notification. No confirmation prompt. Just a policy update buried in a blog post. Who is exempt? Enterprise and Business plans are safe — their contracts explicitly prohibit training on customer data. But the millions of individual developers on Free, Pro, and Pro+ plans? You're in unless you act. GitHub’s CPO, cited "meaningful improvements, including increased acceptance rates" from internal tests as justification. While that's great for the product's evolution, it means the smarter suggestions you're seeing are being built on code from developers who didn't realize they were contributing. This isn't a debate about whether AI training on code is good or bad. It's about informed consent. A 30-day window quietly posted on a blog isn't consent — it's a countdown. How to fix it right now: Go to Settings → Copilot → disable interaction data sharing. Do it today. Read the official update here: https://lnkd.in/dRTzDajg #GitHubCopilot #DeveloperTools #Privacy #SoftwareEngineering #TechNews #AIAssistedDevelopment

I noticed a few interesting AI updates this week. 😎Claude Opus 4.7 was released. I haven’t tried it yet, but the first feedback I heard was not very excited. I’m not too motivated to test it, but anyway I’ll test it before making any conclusions. 😎GPT also has a new version - 5.5 This one looks promising, so I’m going to test it over the weekend. 🥲And GitHub Copilot changed its pricing strategy for individual plans. Now it looks closer to other coding agent providers: more limits, more structure, more usage control. Not the most exciting update. But probably a very expected one. What I liked is how GitHub explained the change. They were direct about the cost of agentic workflows and premium models. https://lnkd.in/diKTAf6P And I think this is the main point here: AI tools are growing fast, but the “unlimited usage” phase is slowly disappearing. For teams and engineers, this is worth watching. Not dramatic right now. Just another sign that AI coding tools are becoming more mature, more controlled, and probably more expensive 💰💰💰 Will test more and share thoughts later. #AI #GitHubCopilot #ClaudeCode #Codex #CodingAgents #EngineeringLeadership

GitHub Copilot data usage is changing—here’s what to know before April 24 ⚠️ Using GitHub Copilot? A privacy + ToS update could affect how interaction data is used. GitHub says that starting April 24, it will begin using Copilot interaction data—inputs, outputs, code snippets, and related context—from Copilot Free, Pro, and Pro+ users to train/improve AI models, unless opting out. ✅ Not affected: Copilot Business + Copilot Enterprise. What clicking the link gets: 🔎 A clear breakdown of what changed in the Privacy Statement and Terms of Service 🧠 The specifics on AI model training and what data is included 🛡️ How GitHub describes safeguards (filters, de-identification) 🌍 Notes for EEA/UK users on “legitimate interest” as the lawful basis 🏢 What “sharing with affiliates (incl. Microsoft)” means—and how opt-out preferences travel with shared data If Copilot is part of daily workflow, this is worth reading—and discussing. https://lnkd.in/dVnmDd3S #GitHub #Copilot #Privacy #TermsOfService #AI

GitHub just changed the economics of AI-assisted development. Yesterday, GitHub announced Copilot is moving to usage-based, token-driven pricing starting June 1. For teams running agentic workflows, this isn’t a pricing tweak — it changes how AI costs compound per feature. We published a deep dive on: - Why dashboard AI metrics no longer satisfy finance or boards - How per-feature ROI and per-feature cost tracking actually works - What teams should do before June 1 to avoid surprise spend If you’re scaling Copilot or agentic workflows, this is required reading. 👉 Read the full post: https://loom.ly/GjBuThc #GitHub

GitHub just paused new sign-ups for Copilot. Not because of a bug. Not because of a breach. Because AI agents are using so much compute that they can't keep up with demand. Think about that for a second. The tools that help developers write code are now so powerful that GitHub literally had to pump the brakes. They've also removed their most powerful model (Opus) from standard plans because it costs too much to run at scale. Meanwhile Kimi just dropped an open-source model that's beating closed-source competitors on coding benchmarks. And OpenAI is about to launch GPT Image 2. The AI race isn't slowing down. It's accelerating so fast that even the biggest players can't keep their infrastructure ahead of demand. For UK businesses this means one thing: the cost of NOT adopting AI is going up every single day. The tools are getting better, the competition is getting smarter, and waiting is the most expensive option. At Altura we're helping businesses in Sheffield and across the UK build AI systems that save real time and money. Not hype, not theory. Working automations that pay for themselves. If you're still on the fence, the fence is shrinking. Drop me a message.

🚀 GitHub Limits AI Usage: Cost Reduction and Improvement in Service Quality GitHub, the leading software development platform, has announced restrictions on the use of its artificial intelligence tools, such as GitHub Copilot, with the aim of optimizing resources and enhancing the user experience. This measure responds to the exponential growth in AI demand, which has significantly increased operational costs. 🤔 Why Implement These Limits? The decision arises from the need to balance accessibility with sustainability. Intensive use of AI models generates high computing costs, and without controls, it could compromise the service stability for everyone. 🔹 Main Changes in AI Usage - Limits on daily requests for free and basic plans, avoiding abuse and prioritizing active developers. 📊 - Adjustments in token consumption for complex queries, which reduces costs by 30-50% according to internal estimates. 💰 - Improvement in response prioritization, ensuring greater accuracy and speed for premium users. ⚡ - Upgrade options for teams that require greater capacity, promoting scalable enterprise plans. 🏢 These limits not only help GitHub maintain accessible prices but also drive more efficient and ethical AI in the development ecosystem. For more information visit: https://enigmasecurity.cl #GitHub #ArtificialIntelligence #SoftwareDevelopment #Technology #Copilot #TechInnovation Connect with me on LinkedIn to discuss trends in AI and cybersecurity: https://lnkd.in/dj8wrubg 📅 Tue, 21 Apr 2026 16:45:00 +0200 🔗Subscribe to the Membership: https://lnkd.in/eh_rNRyt

Action Required: Disable GitHub Copilot's New Data Training Policy If you use GitHub Copilot, there is a critical update you need to know about. Starting April 24, 2026, GitHub will begin using your interactions, including code snippets, inputs, and outputs, to train its AI models by default for Free, Pro, and Pro+ accounts. While AI advancement is exciting, many developers and companies have strict privacy requirements regarding their proprietary logic and data flow. How to opt-out (in under 60 seconds): Go to your GitHub Settings. Click on Copilot in the left-hand sidebar. Look for the dropdown: "Allow GitHub to use my data for AI model training". Change the selection to "Disabled". Why this matters: IP Protection: Ensure your unique solutions don't inadvertently influence future model outputs. Privacy: Keep your active session context private. Consent: This is an "opt-out" system, meaning it's active unless you manually turn it off. Note: This change does not currently apply to Copilot Business or Enterprise tiers, but it’s worth a quick audit for every developer to ensure your settings align with your privacy preferences. Spread the word to your fellow devs! 💻🔒 #GitHub #GitHubCopilot #DataPrivacy #SoftwareEngineering #DeveloperTips #AI Ethics

I cancelled my GitHub Copilot subscription today. Not because it's bad. Because something better replaced it. A few weeks ago I disabled it to test other AI tools. Since then I've only turned it back on twice and immediately turned it off again. The only thing I actually missed was inline code completion. And honestly? I'm writing less and less code anyway. The tools I've picked up since are better at the work I'm actually doing now: architecture, product decisions, and prompting. Copilot was built for how I worked a year ago. The tools replacing it were built for how I work today. My OpenAI subscription is probably next. Not because ChatGPT is bad, but because other tools are catching up and pulling ahead in the areas I actually use daily. The AI tooling space is moving so fast that the best tool from six months ago might not even make your shortlist today. What tools have you swapped out recently? What replaced them? #aitools #githubcopilot #github #openai #claudecode #codex

A developer opened GitHub Copilot on Monday morning and noticed his favorite AI model was gone. Replaced by a newer version that cost 7.5 times more in credits. New sign-ups to the plan had been quietly suspended. The trigger was a blog post from GitHub announcing changes to Copilot individual plans. The premium AI models that developers had been using for months were being restricted or removed. Credits that used to last all month now ran out in days. Some said this was always inevitable. AI tools have been running at a loss since launch. One commenter calculated that a handful of heavy coding sessions could burn through more compute than the entire monthly subscription cost. Another pointed out that every major AI tool launch in the last two years has been a promotional period subsidized by investor money, not a business model. The bill was always going to arrive. That argument seemed settled until the enterprise crowd pushed back. Enterprise customers pay through different channels - consolidated billing, data protection agreements, compliance packages bundled under Azure. The individual plan was always a side show. Enterprise contracts carry the business, and those prices haven't changed. A few commenters noted that most coding tasks don't need the most expensive model anyway, and developers defaulting to the biggest model available were creating their own cost problem. Most of my day is spent finding bottlenecks in businesses and optimizing them with AI. I put together a framework for non-tech founders trying to figure out where AI would actually fit in their business - without having to follow every new release. Comment "AI Framework" or DM me and I'll send it over - please make sure I can DM you.