In this episode Alec and Brian talk about AI, turkey, and AI turkey?

I am back to my work to precisely define how we integrate with many different APIs. With this round I am doing it for a handful of use cases meant to satisfy customer conversations around their AI integration needs. If you’ve been tuned into my newsletter than you’ll know that I am wrestling with defining these conversations in the context of a capability. Not an API capability, but just a capability that describes something we need to be capable of when it comes to our businesses. As part of this work I am aggregating many voices from stories I’ve read online, but also podcast episodes I am producing as part of this work. Across these stories I regularly hear how a capability is a wrapper for everything you need to integrate with AI—something that like AI, often seems pretty hand wavy.

Everyone I am talking with is someone willing to do the work to define the technical details of what a capability is, but I don’t think everyone is willing to do the work to define the business details of what a capability is. I don’t think this is any nefarious act—it is just that we aren’t used to prioritizing these things in engineering circles. In my experience, the engineering folks who I sit down to define all of the technical details aren’t always equipped or willing to sit down and go through the business details. The same is on the other side of things, and the business folks who I sit down to define all the business details aren’t always equipped or willing to sit down and go through all the technical details. With the folks willing and able to do work on both sides being a very rare beast.

The result is that you encounter people on both sides who are on board with the concept of a capability helping define the future of integrations as they are needed to drive our businesses, but things get pretty hand wavy about the details of what that means, and there is very little connecting of the dots across the business and engineering landscape. I’d say the technical details get the lion share of work, and the business details just being left unspecified, or not connected with the technical details—resulting in drift down the road. You often just end up with two distinct sets of specifications, that may or may not be connected, but as the road map rolls forward, this disconnect becomes greater over time, resulting in much of the friction and pain associated with legacy systems.

The concept of a capability is pretty powerful for bridging these two worlds. You can define, educate, govern, and align across what the two groups want. It also lets you set the context window for not just aligning with AI applications, but any application, as well as the human coordination, communication, and collaboration required to make this work. Capabilities exist within a domain, which has a well-defined vocabulary for tagging and organizing everything into meaningful boundaries. Capabilities have a well-defined set of services that are being used—including the business and technical details of these services. This alone, will help reduce the “everything you need to integrate with AI” to something that is manageable and communicated across the business and engineering groups, but also with the non-human interactions that are increasingly required to do business.

Starting December 1, the Electron project will enter a quiet period before picking back up at full capacity in January 2026. For full details, see the Policies section below.

Since 2020, December has been a time for project maintainers to take a breather from regular maintenance duties in order to take a break or focus on heads-down work. This break helps us rest up and come back energized for the year to come.

That said, a month-long pause like this one is only achievable when an open-source project is in a healthy state—we’d like to thank all maintainers and external contributors for all of their continued efforts to keep the project moving. ❤️

2025 in review​

As we close out the year, we’d like to highlight some of the projects we’ve accomplished. Here are some things we were proud of in 2025:

• ⚛️ Shipped 6 new major versions of Electron in tandem with every other Chromium major version.
• 🌿 Migrated Electron’s build tooling from Ninja to Chromium’s new siso build system, which adds native remote execution support.
• ✨ Revamped the releases.electronjs.org page with a fresh new design.
• ✅ Accepted four new RFCs and implemented two others into electron/electron.
• ☀️ Completed two new Google Summer of Code projects:
  • The Devtron DevTools IPC tracker Extension is now available via npm install --save-dev @electron/devtron.
  • The Save/Restore Window State API for Electron’s BaseWindow module was accepted as an RFC and is awaiting its final merge in Electron core.
• 📦 Released modernized major versions for all @electron/ npm packages as ECMAScript modules requiring at least Node 22.
• 🔒 Moved package publishing from Continuous Auth to the new token-less OIDC-based trusted publishing system in light of security incidents in the npm ecosystem.
• 🧑‍💻 Onboarded four new maintainers who help us ship great software every day and keep the project running long-term.

Thanks for a great year, and see you in 2026!

Quiet period policies​

Not much has changed from previous years, but we changed some of the wording around issue and pull request reviews to temper expectations but allow maintainers to continue to engage with the project as much as they want.

What will be the same in December​

1. Zero-day and other major security-related releases will be published as necessary. Security incidents should be reported via the escalation policy outlined in the SECURITY.md document.
2. Code of Conduct reports and moderation will continue.

What will be different in December​

1. The last stable branch releases of the year for Electron 37, 38, and 39 will occur on the week of December 1st. There will be no additional planned releases in December.
2. There will be no nightly, alpha and beta releases for the last two weeks of December.
3. Regular Working Group meetings will be paused.
4. Issue triage may be delayed.
5. Pull request reviews and merges may be delayed.

GPT 5.1 shipped on November 12, 2025, and it’s now rolling out to Copilot on Windows, including for those who use Microsoft’s AI without a paid subscription. That makes sense as GPT 5.1 is also free on ChatGPT, but Copilot gives you access to GPT 5.1’s Thinking without a subscription.

Microsoft told me that GPT 5.1 is being rolled out on Copilot gradually, and it won’t show up right away. You don’t have to log out, create a new account or update the Copilot app on Windows or anywhere else to see the new GPT 5.1. It’s a server-side rollout, and I’m only seeing it in the Copilot app.

I’m also subscribed to Microsoft 365, but I don’t think that helps with the access, as it only increases a couple of limits.

GPT 5.1 is the default “smart” mode in Copilot, but if you switch to Think Deeper, Copilot will use GPT 5.1 in ‘Thinking mode.’ Now, this is only available on ChatGPT if you pay at least $20 for the subscription. That’s something you’d get for free with Copilot, but we really don’t know if it’s always GPT 5.1 Thinking and if it is, what is the juice (thinking) level?

Copilot on Windows now has Labs, but some features are still missing

Windows 11’s Copilot is actually one of the rare native apps. It’s using WinUI 3 for most of the interface, including the conversation, compose box, etc. But you’d still find WebView2 being for “Pages.” Microsoft is still unable to bring all features to Copilot on Windows 11, but we’ve reasons to believe that this could change in the future.

Microsoft is testing Copilot Labs for the Windows desktop app, and one of the early features is ‘Vision.’ Eventually, Microsoft plans to bring Copilot 3D or audio expressions as a native feature to Copilot. Right now, these shortcuts redirect to microsoft.copilot.com in your default browser.

“Copilot Labs is now accessible directly from the Windows desktop app! Vision is already available in-app, and for experiments that require a browser—like 3D, Audio Expressions and Portraits—you’ll be smoothly redirected to their respective sites,” Microsoft officials confirmed.

The next lab feature in Copilot could be ‘Actions.’ With Copilot Actions in Copilot for Windows, you can allow Copilot to act on files stored in one of the local drives.

Microsoft says it’s using the ‘Agent Workspace‘ feature, which allows AI agents like Copilot to access personal files or folders locally stored on the PC. The Agent Workspace is a bit similar to Windows Sandbox, as it creates a special environment for agents, like Copilot Actions.

The post Microsoft begins rolling out GPT 5.1 to Copilot on Windows 11 along with new “Labs” feature appeared first on Windows Latest

Will Apple turn to Intel for production of its M-series chips in 2027? That’s what supply chain analyst Ming-Chi Kuo predicted on X Friday. Citing his latest industry surveys, Kuo says that Intel’s chances of becoming Apple’s latest “advanced-node supplier… has improved significantly” in recent weeks.

Any deal with Intel would be significant considering the chipmaker famously missed out on supplying its own processors for the original iPhone. Apple now has a deal with Taiwan-based TSMC to supply silicon chips for its iPhone, iPad and Mac products.

Kuo says that Apple has a non-disclosure agreement with Intel to acquire the company’s 18AP PDK 0.9.1GA chips. At this point, the company is waiting on Intel to deliver the PDK 1.0/1.1 kit, which is supposed to arrive in the first quarter of 2026. If everything stays on track, Intel could start shipping Apple’s lowest-end M-series processor, built on the 18AP advanced node, sometime in the second or third quarter of 2027, Kuo says. But that timing still depends on how smoothly things go once Apple actually gets the PDK 1.0/1.1 kit.

Kuo theorizes that a deal with Intel could help Apple demonstrate to the Trump administration that its committed to “buying American” by rerouting its supply chain to include more US-based companies. For Intel, a deal could signal that the company’s worst days are passed. “Looking ahead, the 14A node and beyond could capture more orders from Apple and other tier-one customers, turning Intel’s long-term outlook more positive,” Kuo writes.

Could Apple strike a deal with Intel? And what would happen if it decided to use the chipmaker’s 18AP processors for its entry-level M-series?

Our old friend Lars Wikman returns to the show to discuss Linux distro hopping, Elixir, Nerves, embedded systems, home automation with Home Assistant, karate, and more.

Join the discussion

Changelog++ members save 8 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

• Tiger Data – Postgres for Developers, devices, and agents The data platform trusted by hundreds of thousands from IoT to Web3 to AI and more.
• Augment Code – Developer AI that uses deep understanding of your large codebase and how you build software to deliver personalized code suggestions and insights. Augment provides relevant, contextualized code right in your IDE or Slack. It transforms scattered knowledge into code or answers, eliminating time spent searching docs or interrupting teammates.
• Depot – 10x faster builds? Yes please. Build faster. Waste less time. Accelerate Docker image builds, and GitHub Actions workflows. Easily integrate with your existing CI provider and dev workflows to save hours of build time.
• Framer – Design and publish in one place. Get started free at framer.com/design, code CHANGELOG for a free month of Pro.

Featuring:

• Lars Wikman – Website, GitHub, X
• Jerod Santo – GitHub, LinkedIn, Mastodon, X
• Adam Stacoviak – Website, GitHub, LinkedIn, Mastodon, X

Show Notes:

• Nerves project
• ZimaBoard
• Home Assistant
• n8n
• Beam Radio

Something missing or broken? PRs welcome!