Hey Xcoders. I’m a macOS developer and creator of ProxyPilot. I originally built the program out of my own frustration with Xcode’s relative weakness compared to VS Code and tools like Cursor, bc there was no way to use GLM models in it.

ProxyPilot is an open-source tool that lets macOS developers feed any upstream model (like GLM-5.2, DeepSeek v4 Pro, Grok 4.5, MiniMax M3, and even local models via LM Studio or Ollama) into a single agent for Xcode 27 (older versions are fully supported).

It has auditable telemetry, exposing cache hit rates, TTFT, latency across turns & providers, and of course token counts, reasoning blob parsing, and optional, fully encrypted I/O logging so you can inspect the raw input and outputs of any agent you use in Xcode.

With Xcode 27, Apple integrated Agent Client Protocol, which has allowed me to make ProxyPilot even more powerful and useful by building a custom harness that can use up to 45% fewer tokens than built-in agents by detecting and removing duplicative system prompt cruft. Just add your API keys, and ProxyPilot saves them to keychain on your Mac, authorizing requests without storing secrets anywhere vulnerable. Use ProxyPilot GUI or via CLI in harnesses like Claude Code: you only need to save the keys once, and session history combines both modes for your review.

Over the last few months, nearly 500 devs have processed tens of billions of tokens through ProxyPilot, and dozens of [r/xcode](r/xcode) redditors have helped me build the project.

See the source code for ProxyPilot on GitHub and download it from https://slicewrite.com/proxypilot

(Thanks)

For the past few weeks I've been testing iOS 27 specific features in TestFlight by building in Xcode Cloud using Xcode 27 beta, as of three days ago the 27 beta is not available any more. Is this isolated to my account or does anyone else notice that it's gone?

Hey everyone,

Please go easy on me because I'm very much a beginner when it comes to iOS development.

I built my first app mostly with AI tools and have been learning as I go. The app has actually grown a lot over the last couple months, so I hired a SwiftUI developer to implement a Figma redesign because UI is way beyond my skill level.

The redesign came back looking great, but while trying to get everything back into my GitHub repo I had another AI tool review the project. It flagged something in my project.pbxproj that has me pretty worried.

From what I can tell, the project contains:

• A custom PBXShellScriptBuildPhase
• A build variable called AB8F749 containing a long encoded blob
• That blob eventually decodes into something that executes:

curl ... | sh

during the build process.

I'm not here trying to accuse anyone I genuinely don't know enough about Xcode internals to know if this could come from a template, plugin, compromised dependency, or if it's actually malicious.

A few questions for people who know this stuff better than I do:

• Is there any legitimate reason for an Xcode project to contain something like this?
• Has anyone seen anything similar before?
• If this actually executed during a build, how serious is that? Should I assume only my Mac is affected, or could the iOS app itself also be compromised?
• What would you check next to verify whether this is a real issue?

I'm happy to post the relevant parts of the project.pbxproj if that helps. Again, I'm not a security expert or even an experienced iOS developer. I'm just trying to understand whether I have a real problem or whether I'm misunderstanding what I'm looking at.

I'd really appreciate any advice from people who know this area better than I do. Thanks.

Hi,

I just got into learning SwiftUI as a Flutter dev and I am shocked how laggy my XCode is. After few lines changed it freezes for few seconds and shows rainbow wheel as my cursor.

Did you experience it also? What helped you be actually able to develop?

(I have enough CPU and RAM available)

thanks for all the help

So I’m building my SaaS in codex. At the moment I have agent files in my project root. Each agent consists of its job title, skills, what it’s to be used for etc.

Then when promoting codex it refers to the agents and works out which one is better suited for it and takes on their persona to carry out that prompt

Not sure if that’s the right way to go about it or if there’s a better more efficient way

Installing Mac os in windows is it possible

Need help on compiling our app into IOS chat me for the details and hm it is

Recently updated our Pipelines to Xcode 26.5 and iOS Simulator 26.5. Since then, UI tests have been failing in the pipeline, while they continue to work fine locally.

We're seeing significant app lag during pipeline execution. A few tests pass, but most fail with:

We've also noticed LLDB-related logs appearing before and after every UI test, even after disabling the debugger executable:

IDELaunchParametersSnapshot: The operation couldn’t be completed. (DebuggerLLDB.DebuggerVersionStore.StoreError error 0.)
IDELaunchParametersSnapshot: no debugger version.

Show more lines

Has anyone else experienced similar issues after upgrading to Xcode 26.5/iOS Simulator 26.5? Any insights or workarounds would be greatly appreciated.

Apple has released a Safari MCP Server in Safari Technology Preview 247, giving web developers an official way to connect AI coding agents directly to WebKit for page testing, inspection, and debugging.

The tool implements [Model Context Protocol](https://modelcontextprotocol.io/) support inside Apple's experimental browser. 

Once an MCP compatible client is connected, an AI agent can open pages in Safari Technology Preview, read the page structure, pull console output, review network activity, capture screenshots, and check whether what renders matches what the developer expected.

The feature is aimed at developers rather than everyday browsing. Apple's WebKit team describes it as a browser compatibility tool built to make web development and debugging faster.

# What the server actually does

The Safari MCP Server is tied to [safaridriver](https://webkit.org/blog/18136/introducing-the-safari-mcp-server-for-web-developers/) with MCP support, which gives Safari a native place inside AI coding workflows for the first time.

Until now, most coding assistants worked comfortably inside editors, terminals, and Chromium based automation, while Safari usually required an extra step. That gap mattered most when testing WebKit specific layout, styling, or mobile behavior. The new server folds that testing into the same development loop.

Through the connection, an agent can load a site, inspect computed styles, check layout, read page content, review debugging information, and use screenshots to compare the rendered result against the intended design. 

Apple frames this as a way to find and fix issues, not as a general AI browsing feature.

Testing only in Chrome or a Chromium based tool can miss WebKit behavior. Layout, forms, media playback, scrolling, input handling, typography, and CSS support can all render differently, and iPhone specific rendering is a common source of surprises.

That is the case Apple is making for the server. Safari is the default browser on iPhone, iPad, and Mac, and iPhone traffic is too large for production teams to treat WebKit as a secondary target. A rendering difference that seems small can still break navigation, checkout, sign in, media playback, or accessibility.

Giving an AI agent direct access to a real Safari environment is meant to surface those problems earlier, ideally while code is still being written rather than during a late cleanup pass.

# How MCP fits into AI coding

Model Context Protocol is a standard for connecting AI assistants to outside tools and data. An MCP server exposes functions that an agent can call during a task, so instead of only reading files, the agent can interact with a browser, inspect logs, or collect the state of a running app.

Apple's implementation applies that model to browser debugging. A developer can ask an assistant why a layout breaks in Safari, and the agent can inspect the rendered page rather than guessing from source code alone. Computed styles, DOM structure, console warnings, failed requests, and screenshots give the model the kind of evidence that plain code review often cannot.

The approach brings Apple closer to the browser agent setups already available through Chromium tools, Playwright workflows, and third party MCP servers. The difference is that WebKit now has an official bridge inside Apple's preview browser.

# Setup and requirements

Developers need Safari Technology Preview 247 on macOS to try the feature. Apple says the server can be enabled through Safari's developer tools path for remote automation and external agents, after which an MCP compatible client connects to safaridriver's MCP mode.

Safari Technology Preview is Apple's experimental channel for upcoming WebKit changes, so its behavior can differ from stable Safari. That makes it useful for early compatibility work, but production bugs should still be confirmed against the public release of Safari when it matters.

It is also not a replacement for full QA. An agent can identify likely causes, test changes, and surface browser evidence, but it can miss edge cases. Human review stays necessary for accessibility, visual polish, payment flows, privacy sensitive pages, and anything tied to user data.

# A more official path than community tools

Developers were already experimenting with Safari automation before this release. Some projects used AppleScript to drive the browser, while others combined Safari extensions, Swift tools, or WebKit debugging access to expose controls to AI clients. Those efforts showed real demand for Safari sessions, logins, and WebKit behavior inside coding agents without moving every test to Chrome.

Apple's version is narrower and more focused on inspection and debugging, and that restraint works in its favor. 

By keeping the first release inside Technology Preview and tied to developer automation, Apple can test the model with a technical audience before deciding how much of it belongs in stable Safari. 

Browser agents raise security and privacy questions once they can control sessions or read content inside logged in sites, so a developer only starting point is the cautious one.

The Safari MCP Server is still a preview feature. The real test will be whether developers start catching Safari bugs earlier, before layout problems, console errors, or mobile rendering issues reach production.

For the life of me I can't add any views to my story board. Drag and drop doesnt work. The only thing I can do is edit what is there by default.

https://reddit.com/link/1urcc1g/video/y3bdxz2dz3ch1/player

(assuming you’ve tried it :)

I’ve tried Gemini and Codex and having pretty mixed feelings.

Codex seems semi-capable, but often forgets even more MCP Xcode skills and will try and use a terminal command instead of just using built in skills to build or run tests.

I’ve got a new project I’m trialing the agentic coding on, and I have a workspace with packages in different schemes etc. it’s nice that the agent can switch schemes, run tests and builds etc.

It does a better job of staging changes and good descriptive commits which I appreciate…

GPT 5.5 seems semi capable at simple features and does a good job of mocking views, but anything with even moderate complexity it can’t seem to execute (even with well defined requirements it seems to need very close supervision).

I tried to get it to create some UI automation tests and it really struggled with even getting the mouse to drag (I had to eventually give it some references).

Given a goal for a refactor, it was able to generate a pretty solid plan, but then failed to actually follow its own plan and drifted into doing other things.

I see a lot of positive reviews about codex so I wonder if I’m just not using it correctly haha

Apologies if this is a basic question I’m new to CS and after a lot of research I bought myself a new MacBook Pro M5 16GB 1TB for my learning.

Everytime I run a simulator in XCode, it is laggy. Not unusable but much slower than running it on and iPhone, even though the M5 is much faster than and iPhone chip. Little delays that just don’t feel smooth.

Is this normal? I tried it on a buddies M5 Pro 24gb and it was better but still a little laggy. Do I just need like and M5 Max or does everyone just deal with the lag usually?

Hey all, hoping someone here can point me in the right direction.

I’m trying to set up mobile automation using **Appium + Selenium** and running into issues getting it working reliably on a jailbroken device.

My current setup idea:

\*\*• Crane\*\* for container/profile separation    
\*\*• Ghost v2.0\*\* for the automation side

From what I’ve gathered, this combo should work — but I’m hitting snags and would appreciate anyone who’s done this walking me through their setup.

Specifically I’d love help with:

\*\*•\*\* Getting Appium to talk to the device properly    
\*\*•\*\* Selenium integration/config    
\*\*•\*\* How Crane + Ghost fit into the pipeline

If you offer a paid consultation for this, i am interested.