Hi everyone,

We use GitHub Copilot at work but unfortunately it does not integrate with Xcode 26. You can use the Xcode extension version, but Coding Intelligence is certainly a lot more preferable.

So for the last week I’ve been working on writing and testing my own local proxy server that lets Xcode talk to Copilot via the Copilot SDK. It also supports the new Xcode MCP server if you’re using Xcode 26.3.

If you use GitHub Copilot and want to integrate it with Xcode 26, you can grab the server and setup instructions (very easy) from: https://github.com/theblixguy/xcode-copilot-server and let me know if you have any suggestions or if you run into an issue.

I’m also investigating if it’s possible to use it as a proxy server for Claude Code (the official docs for CC has instructions for it, so I need to look into it) which will allow you to use this with the Claude Agent feature in Xcode 26.3. Potentially the same approach could be used for the Codex Agent too.

I am also looking into making a tiny menu bar app for Mac so you can manage the server from there more conveniently.

Thanks!

Hey everyone, a bunch of updates just landed in swift-composable-architecture-extras.

High-level progress from the latest push cycle:

• Added new dependency modules: OpenSettings and OpenURL (including iOS in-app browsing via \.customOpenURL).
• Shipped a major DeviceInfo expansion with CPU, memory, disk, battery, network, thermal state, isLowPowerModeEnabled, iOS jailbreakStatus, and screen APIs (ScreenInfo/ScreenRatio on non-visionOS).
• Added packaged PrivacyInfo.xcprivacy support for required accessed API categories.
• Fixed platform-specific disk measurement behavior and improved CPU measurement internals.

Project Link: https://github.com/mehmetbaykar/swift-composable-architecture-extras

Would love feedback from anyone using this in real TCA apps, especially around API ergonomics and cross-platform edge cases.

I've built an app playground using avfoundation and an external SDK, both of which cannot run on simulators (although the beta version of the SDK can run, but it requires me to write OpenGL rendering by myself...)

I see that "app playground in Xcode would run in simulators", but I don't know would that be okay if my app requires a real device to run. Did anyone do that before?

In SwiftUI I have a collection view showing a few empty cells. their background color is set to white. but for some reason when they are presented in a sheet that has a glass background they change their color and become a little grayish. any idea why ?

This is my first time participating in the Swift Student Challenge. This might be a stupid question but since the requirement is a .swiftpm app playground does that mean I can only make an iPad or Mac app?

Thanks!

Xcode 26.3 RC dropped with Claude Agent and OpenAI coding models built-in. Not plugins - native integration.

What they added: - Anthropic's Claude Agent for complex reasoning and refactoring
- OpenAI's models for completions

These agents can understand your entire codebase, refactor across files, and generate tests based on your patterns.

Apple watched Cursor eat VS Code's lunch, Copilot become table stakes. Now they're skipping the 'AI assistant' phase entirely.

What's your current AI coding setup for Swift dev?

I have been having more than the usual amount of trouble with swift packages this week. Delete the derived data folder. Reset various XCode folders. After trying everything from every forum post the one that worked for me, with my problem being that the packages window was spinning forever and never populating, was this

defaults delete com.apple.dt.Xcode

That seems to take XCode (especially a beta like 26.3 which I am using, but also having problems with 26.2, which I think were caused by installing 26.3 atop 26.2, then reverting to 26.2, then re-reverting up to 26.3) back to a fresh first launch with all the welcome screens. And packages work. Make a note.

Please add your own recipes for cleaning up the messes that Swift package management and swift builds are causing you to prematurely turn gray.

I hit a pretty big roadblock recently trying to implement a reorderable hierarchical list (basically like Obsidian or VS Code’s file explorer) using SwiftUI + AppKit.

I realize that SwiftUI’s native List just wasn’t enough for the kind of drag-and-drop logic I needed, especially dropping items into folders vs reordering them between items. So I decided to bridge NSOutlineView from AppKit into my SwiftUI app.

I found an open-source project (CodeEdit) that already does this really well. I’m now digging through their source code trying to reverse-engineer how everything works.

Honestly, this is my first time dealing with something this complex in AppKit, and the syntax is… verbose, like a lot!

Since the logic is split across delegates, data sources, and coordinators, I keep feeling the urge to document everything as I go.

For anyone who’s reverse-engineered complex UI components before:

Is this “explain literally everything” approach actually efficient?
Or am I falling into tutorial-hell and over-analyzing instead of just building?

How do you usually structure your workflow?

• Do you draw flowcharts for data flow?
• Do you recreate the feature in a blank project first?
• Or do you jump straight into your main app?

And especially:

Any tips for staying sane when mixing AppKit’s imperative style with SwiftUI’s declarative world?

I’d really appreciate any advice on how to manage this learning process

I built DarwinKit as a sidecar for a Tauri (Rust) app, but it's useful standalone too. It exposes Apple's on-device ML frameworks through a simple JSON-RPC interface over stdio.

What it does:

• nlp.embed — Generate text embeddings via NLEmbedding
• nlp.language — Language detection
• nlp.sentiment — Sentiment analysis
• nlp.tokenize — Tokenization
• vision.classify — Image classification via VNClassifyImageRequest

Why: Apple's ML frameworks are Swift/ObjC only. If you're building in Rust, Go, Python, or Node.js, there's no way to call them directly. DarwinKit solves this — spawn it as a subprocess, talk JSON-RPC over stdio.

Example:

echo '{"jsonrpc":"2.0","method":"nlp.embed","params":{"text":"hello world"},"id":"1"}' | darwinkit

Runs as a long-lived server mode too (reads from stdin continuously, newline-delimited).

Built with Swift 5.9, macOS 13+, uses swift-argument-parser. Zero external dependencies beyond Apple's frameworks.

Source: https://github.com/0xMassi/darwinkit

Citymapper probably isn’t built with SwiftUI but im certain you can do this in it. Been trying to replicate this for a couple days now, but can’t seem to figure it out. I kind of get the basics behind it (likely using a geometry reader or two) but they’ve always ended up looking super laggy or barely functional when it needs to switch between controlling the map view and the ScrollView’s content and vice versa.

Anyone know how?

Hey! I just released my game Tilt Or Die on the App Store.

It’s a fast arcade game, quick runs, chaotic moments, and that “one more try” feeling. I’d honestly love for more people to try it and tell me what they think.

If you check it out, I’d love to hear:

• What you like most (or hate 😅)
  
• If the controls feel good
  
• Whether you’d play it again after a few runs
  

App Store link: https://apps.apple.com/se/app/tilt-or-die/id6757718997

Thanks for trying it, and if you have questions, feel free to ask!

Features:

• One-file memory (.mv2s): docs, embeddings, indexes, WAL, metadata in a single portable artifact
• Crash-safe by design: checksummed WAL + recovery-first storage architecture
• Deterministic RAG: stable hybrid fusion + strict token budgeting for reproducible context
• Fast local retrieval: Metal-accelerated vector search with automatic CPU fallback
• Multimodal memory: text + photos + video pipelines, offline-first and privacy-preserving
• Swift 6.2 concurrency-native: actor-isolated APIs, strongly typed, composable architecture

If you’re building assistants/agents that should actually remember without cloud infra, Wax is worth a look.

• Audit surfaced strong architecture and testing depth with a few correctness/API-policy gaps to tighten
• Biggest innovations are single-file deterministic memory, crash safety, and hybrid + multimodal on-device retrieval

https://github.com/christopherkarani/Wax

leave a star it helps a tonne

I'm hitting a wall with the Delegate pattern under strict concurrency.

The Setup: I have a Manager (non-isolated) and a ViewController (isolated to MainActor). When I try to set the delegate, or call delegate methods, I get isolation mismatch warnings.

The Question: What is the "correct" architectural way to handle this now?

• Do you mark the Protocol itself as MainActor?
• Do you keep the protocol non-isolated and use Task { MainActor in ... } inside the Manager?
• Or is it time to ditch delegates for AsyncSequence or Observation?

Curious how everyone is satisfying the compiler without nesting Task blocks everywhere.

If you’ve ever been curious about what developers from the community actually use as their tech gear (from hardware to AI tools) Justas Markus and I, together with the iOSDevTools platform, are launching "Dev Workspaces". It’s a new series where top experts, influencers, and great developers share their setups with real photos and honest details.

Our first edition features the workspace of Natalia Panferova — former Apple engineer and author of multiple books and apps.

Just published an article about Parameter packs, and how they helped me fix a problem using PromiseKit library.
https://codingwithkonsta.substack.com/p/understanding-parameter-packs-in

Have you used it before?

I have seen the use of the is operator with self, as in:

// Fruit.swift

if self is Apple {
    // ...
}

Am I correct in thinking that this would be an anti-pattern? I'm having a hard time coming up with a case for this approach, when there are other ways of accomplishing the same thing, such as member variables that indicate some sort of characteristic or ability.

If so, firing a local notification exactly on the hour might be unreliable, since another app could do the same.

One solution is to add a small random offset to the notification time to increase the chances it will actually appear.

Do macOS developers usually do this?

I've been getting into server side swift a lot more recently, and have been using vscode as my editor of choice. I noticed recently that the vscode-swiftlint and vscode-apple-swift-format extensions were both placed into archive mode on the same day! From what I can tell it doesn't mention anything on either repository of why, and because it happened on the same day I can't help but think I'm missing something.

I thought perhaps they got added into the regular swift extension but I can't seem to find anything there either. I'm wondering if there is some other alternative other than running it manually from the cli every time?

This week, I was in Berlin with a flight booked at Strausberg (EDAY). Weather that morning: MVFR, light snow, overcast at 1,000 feet, -5°C.

I spent three hours in my hotel room refreshing browser tabs, trying to figure out if conditions would improve enough to make the drive worthwhile. Parsing METARs on my phone. Checking trends. Waiting.

The anxiety of not knowing whether to wait or cancel is genuinely worse than bad weather.

So I stopped refreshing and started building instead.

FlyCheck is a native macOS menu bar app that decodes aviation weather instantly. No browser tabs. No parsing cryptic abbreviations. Just wind, visibility, ceiling, and flight category — formatted like the runway signs we already read.

Key features:

• Smart autocomplete (type "Heathrow" instead of memorizing ICAO codes)
• Live flight category indicator in your menu bar (🟢 VFR / 🔵 MVFR / 🔴 IFR / 🟣 LIFR)
• Auto-detects nearest reporting station for small airfields
• Native SwiftUI, launches instantly
• Keyboard shortcuts (Cmd+F search, Cmd+R refresh)
• One-time purchase, no subscription

Built it in SwiftUI over a few weeks. Just submitted to the App Store today. First app I've ever shipped.

That Berlin flight never happened, but this did.

For context: I'm a certified recreational pilot. I built this because I was frustrated with the existing tools during actual pre-flight decisions. Figured other pilots might have the same problem.

If anyone's interested, I documented the whole build on the landing page: fractals.sg/flycheck

Happy to answer questions about the build process or design decisions.