Edit your existing app.
Copy less. Verify more.

For an existing iOS or macOS project, Relayard lets a compatible ChatGPT model read authorized source and make scoped changes.You still define the task, review permissions and inspect results, without repeatedly pasting each file into the conversation.

Who is it for, and what does it solve?

Independent developers and small teams maintaining an app and changing related files, such as adding filtering and an empty state to a list. The goal is less code copying and manual error transcription while retaining your architecture, business logic and review process.

What do you need?

• A Mac, full Xcode, a working Relayard build and a project that opens.
• A client and model supporting remote MCP, OAuth and the required tools.
• Locally approved reading, editing and build capabilities, plus available model usage.
• Saved editor changes, a Git checkpoint and no other agent writing simultaneously.

How does one change work?

1. Read the state: confirm the binding, relevant source and existing changes so work in progress is preserved.
2. Set scope: define features, excluded modules and acceptance criteria. Break complex work into reviewable stages.
3. Implement: follow project conventions and use only the tools currently available and authorized.
4. Review the diff: inspect files, behavior and unintended deletions locally. A tool result does not replace code review.
5. Verify results: get a terminal build state and logs, plus actual images for visual work. List unfinished items.

A task brief to adapt

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.

How do you recover from a failure?

Preserve the current diff, build error and operation ID. After a disconnection, query the existing operation before dispatching the same write again. Pause new dispatch when you need to limit further work.

To undo changes, separate this task's changes from pre-existing work, then review and restore only the selected changes locally. Pausing or revoking access does not roll back source. Do not reset the whole project or overwrite unsaved work.

When is this a poor fit?

For a short isolated snippet, a normal ChatGPT conversation may be simpler. This workflow does not fit environments without Mac / Xcode, accounts without tool access, projects that must keep all requested content offline, or tasks whose required permissions cannot be granted.

How do you start?

Run the setup self-check. If you have the app, verify a read-only request before enabling edits and execution. Check the availability page for the current release and installation requirements.

Documentation updated: 2026-10-08