GitHub Copilot Moves Into Xcode, and the Walled Garden Opens a Little More

Have you ever picked a tool just because it was the one allowed in the room? If you build apps for Apple devices, you know that feeling. Xcode is where iPhone and Mac apps get made, and for a long time the AI help inside it came only from the names Apple invited in. This week, the guest list got a lot more interesting. The news, in one paragraph On November 3, Apple released the first beta of Xcode 27.3, and the next day GitHub announced that Copilot now works directly inside Xcode's built-in coding assistant. It is a public preview, real and usable but still early, and it needs the Xcode 27.3 beta on a Mac running macOS Tahoe 26.6 or later. You turn it on under Xcode, then Settings, then Intelligence, and GitHub says every Copilot plan is supported. A quick history of the guest list This did not happen overnight. When Apple first added AI to Xcode in version 26, ChatGPT was the invited guest, and Claude joined soon after. Version 26.3 made them more powerful, letting them act as coding agents across a whole project. Then Xcode 27 added Google Gemini to the mix, with a redesigned assistant and multi-turn conversations. Copilot is the latest name on that list, and it is a telling one. Copilot is the assistant most developers met first, back when AI coding help mostly lived in VS Code. Now it sits inside Apple's own editor, next to the tools Apple built itself. Why this one is different Here is the thing. Copilot already worked with Xcode before, through a separate extension that GitHub maintained. That extension still exists, and GitHub says it is not going away. So what actually changed? Think of it like the difference between a food truck parked outside your office and a kitchen inside the building. The extension was the food truck: useful, but always a separate thing to set up and maintain. The built-in assistant is the kitchen. Copilot now lives where the work already happens, in the same panel where you chat with the other assistants, with no extra install. Photo by Clément Hélardot on Unsplash That matters because the editor is the desk where a developer already sits. An assistant that lives at your desk gets used for the small questions, the quick "what does this error mean" moments, not just the big tasks. And Copilot is not stopping at Xcode. On November 3, the same day the Xcode beta landed, GitHub also made Copilot a selectable agent in JetBrains Air. The pattern is clear: the assistants are going to where the developers already are, instead of asking developers to come to them. The part worth staying skeptical about A public preview inside a beta is not a finished product. GitHub has not published a feature-by-feature comparison with the older extension, and Apple's release note is a single line that says nothing about inline completion or whether Copilot acts as a chat provider or an agent. So nobody can honestly tell you yet whether the built-in version does everything the extension does. The beta also includes Swift 6.4, and the stable Xcode 27.3 is expected in December, according to 9to5Mac, so the details could still shift before most developers see it. That is normal for a preview. Try it on a side project first, before you rearrange your whole workflow around it, and see whether it answers in a way that fits how you work. So what does it mean? A few years ago, the question was whether AI belonged in the editor at all. Now every major assistant is lining up to live inside it. It is no longer which assistant you can use. It is which one you actually want sitting at your desk. That is a better question, and a harder one. The tools are no longer the bottleneck. Your judgment about when to ask, when to check the answer, and when to just write the code yourself, that is the skill now. So here is my question for you: if every assistant moved into your editor tomorrow, which one would you keep, and why? Cover photo by Christopher Gower on Unsplash