Give the conversation a build result
Request a native build and get its completion status and logs. Bring real compiler errors back into the conversation.
▸ Native build
BuildProject
↓
RelayOperation
↓
status + build log
MCP CHAT MODE · PRO MODEL · YOUR XCODE
Codex limit?
Bring ChatGPT Pro
to your Xcode.
Let a Pro model in Chat read your code, implement changes and verify builds in the same Xcode project. Built for feature iterations and fixes in an existing iOS or macOS app.
Make code changesCheck local buildsInspect previews
Public download not yet available · Prepare your setup
Native macOS appYour project, your permissions
A Codex limit does not exhaust Chat Pro.Its allowance is separate; you still need remaining Chat Pro usage and support for the required tools. Official usage guide
INTERACTIVE ILLUSTRATION · NOT A PRODUCT RECORDING
CHATGPT
Read the project, plan this release, make the scoped changes and verify the build.
RelayReadexample
BuildProjectexample
BuildProject scheme: "SampleApp" destination: "iPhone Simulator" Build completed · 0 errors
Build result received
CHATGPT
Render the SwiftUI preview and inspect the image you receive.
RelayReadexample
RenderPreviewexample
RenderPreview file: "ContentView.swift" operation: completed ImageContent received
Inspect the returned image
CHATGPT
Read the view, make one focused change, then build to verify.
RelayReadexample
RelayOperationexample
struct ContentView: View { var body: some View { Text("Hello, Relayard") } }
Review the change and build result
Interactive workflow illustration · not a live session
FROM YOUR PROMPT TO A REAL LOCAL RESULT
ChatGPTMCP + OAuthXcodeSwiftUI
START WITH A SCOPED TASK
What will you
move forward next?
Give Pro the goal, current progress and acceptance criteria together. These task templates organize planning, implementation and verification; outcomes depend on your project and tools.
Move a feature iteration forward
For example: favorites and filters for an existing list.
Open task template
What to review: A change summary, build result and remaining work.
TRY THIS IN CHATGPT
Add favorites and filtering to the current app list. Inspect the project and its existing list, storage and UI conventions. Scope: toggle a favorite, filter favorites, and show an empty state. Preserve navigation and data. Make a short plan, then work through the related changes. Use authorized builds, tests or previews to check results. Acceptance: favorites persist using the existing storage approach; filtering and empty states work. Confirm the binding, permissions and actual tools first. Preserve original errors; never invent a pass. Report changes, verified results and unfinished work. Do not automatically commit or publish.
Unblock a failing build
For example: a compiler error left open in Codex.
Open task template
What to review: The root cause, a focused fix and terminal build logs.
TRY THIS IN CHATGPT
Continue the build fix in this Xcode project. Latest error and attempted solutions: [fill in]. First confirm the project, scheme, tools and existing changes. Read the logs and relevant code, find the cause and make the necessary fix. Do not refactor unrelated modules or overwrite existing changes. Build again and follow it to a terminal state. Report the fix and any remaining errors. Confirm the binding, permissions and actual tools first. Preserve original errors; never invent a pass. Report changes, verified results and unfinished work. Do not automatically commit or publish.
Refine a SwiftUI screen
For example: spacing and empty states in an existing view.
Open task template
What to review: UI changes, the actual returned image and checks still needing a person.
TRY THIS IN CHATGPT
Refine the SwiftUI screen in [view / file]. Goal: [spacing, hierarchy, empty state or accessibility requirement]. Inspect the existing code and preserve business logic and design conventions. Make the scoped change, then render using an available native Preview tool. Inspect the actual returned image before assessing the visual goal. If there is only a path or no image, report visual verification as incomplete. Confirm the binding, permissions and actual tools first. Preserve original errors; never invent a pass. Report changes, verified results and unfinished work. Do not automatically commit or publish.
HOW IT WORKS
A shorter path
from prompt to project.
Keep the Xcode workflow you know. Relayard makes the connection between your AI client and your local project.
01
Choose your project
Select Xcode and a project on your Mac. Review which tools can read, edit or execute.
02
Connect your AI
Copy your stable MCP URL and authorize the connection in a supported client.
03
Work with real results
Start with a file read. Follow builds to completion and inspect the preview image that comes back.
CLOSER TO YOUR CODE
Beyond the code snippet.
Files, builds, previews and runtime context. Connected in the same development conversation.
See the actual preview
Request an available SwiftUI preview and receive its image, so the next change starts from what actually rendered.
Make focused changes
Read the source, make a scoped edit, then use a build and its returned result to check your work.
One stable connection
Keep a stable URL for your project binding. Authorize clients with OAuth, without putting credentials in the URL.
Reach available Simulator tools
Use the run and screenshot capabilities your environment exposes, after local pairing and permission review.
Tool availability depends on Xcode, native tool discovery, client support and local permissions. Simulator actions also require an active pairing. Use the capabilities your environment actually exposes.
CHECK THE EVIDENCE
A working connection
has results you can inspect.
Start with a read-only request, then authorize edits and execution. An online indicator or tool name alone does not prove a completed task.
01 / Read
Actual contents from a file in the selected project.
02 / Build
A terminal operation state and logs from that build.
03 / Preview
An image actually received and inspected, tied to the operation.
YOUR MAC. YOUR CONTROL.
The connection is remote.
The control is yours.
Choose the project, capabilities and client. Files and builds stay on your Mac; requested source, logs and images pass through the hosted relay and AI client.
Understand data flow & permissionsBound to the project you choose
Each endpoint targets a specific project, rather than following the frontmost Xcode window.
Permissions with a purpose
Review read, edit, execution and Simulator capabilities. Remote requests still pass local checks.
Pause or revoke access
Pause new work from your Mac or revoke a client grant. Completed changes are not automatically rolled back.
A GOOD PLACE TO START
A little setup. A lot closer.
01 / CONNECT
Connect ChatGPT to Xcode
From local permissions to your first read-only request.
Read guide02 / VERIFYYour first build & preview
Track the operation and inspect the actual returned image.
Read guide03 / TROUBLESHOOTGet your connection working
Check state, permissions and pairing in the right order.
Read guideGOOD QUESTIONS
Before you connect.
Can I keep developing after hitting a Codex limit?
Pro models in Chat have usage allowances separate from ChatGPT Work and Codex. Reaching a Codex limit does not by itself exhaust your Chat Pro allowance. With Chat Pro usage remaining and the required tools available, use Relayard to continue in the same Xcode project. Check the limits and reset time shown for your account.
Does one message mean one complete app release?
A well-scoped request can ask Pro to plan, implement and verify multiple changes in one workflow. A release is not a guaranteed quota unit: completion depends on project state, scope, context and available tools. There is no fixed promise of one message per release or a universal monthly message count.
Does Relayard import my Codex conversation?
No automatic conversation import is provided. Save your files, preserve a Git checkpoint, and bring a short handoff with the goal, completed work, remaining tasks and latest errors. ChatGPT then reads the current project through Relayard.
What subscriptions or costs are involved?
You need your own ChatGPT account with access to a Pro model and usage remaining. Relayard does not include or expand ChatGPT usage. Relayard pricing, trial terms and release arrangements have not been announced on this site.
What is Relayard?
Relayard is a native macOS app and hosted MCP relay that connects an authorized AI client to a selected Xcode project on your Mac. It provides project binding, OAuth access, permission controls and operation results.
Do builds run on my Mac?
Yes. Available native Xcode operations run on your Mac. Relayard connects the client to those tools; it does not replace Xcode or move your build to a cloud compiler.
Can I connect it to ChatGPT?
It is designed for clients that support remote MCP and OAuth, including eligible ChatGPT configurations. Your account or workspace must provide the required connection capability. Follow the connection guide and check the actual imported tools.
Is every Xcode or Simulator action available?
No. Availability depends on your installed Xcode, native tool discovery, the selected project, client support and local permissions. Simulator actions also require the relevant local pairing and approved capabilities.
Does my code stay entirely on my Mac?
Your project and builds stay on the Mac, but requested code excerpts, logs and images pass through the hosted relay and the AI client you authorize. This is not an offline or end-to-end encrypted workflow.
Where can I download Relayard?
The download page tracks release availability. A public signed installer or App Store listing has not been linked yet. If you already have a build, you can use the setup guides now.
Make your next conversation
about your actual project.
Check Mac app availability and get ready for your first connection.