Use Superapp with local coding agents

Work on the same Mac project with Claude Code, Codex, or an agentic Xcode tool.

On Mac, a Superapp project is a normal local folder containing a native Swift and Xcode project. You can open that folder in Claude Code, Codex, Xcode, or another local coding agent and continue working with the tools you prefer.

One project, several tools

Superapp, local coding agents, and Xcode can all edit the same files. There is no separate export format to translate: point the other tool at the project folder and ask it to work directly with the Swift code. Keep only one tool actively writing at a time to avoid conflicting edits.

Product-level iteration

Superapp

Describe screens, flows, behavior, and design changes in plain language while Superapp manages the project it generated.

Direct project access

Local agents and Xcode

Inspect files, make precise code changes, run tests, debug builds, and use specialist developer tooling directly on your Mac.

Use a safe handoff

1. Save a known-good version

Confirm the app builds, then create a version-control commit or another recoverable snapshot before giving an external agent write access.

2. Open the project folder

Start Claude Code or Codex in the Superapp project folder, or open the Xcode project in an agent-enabled Xcode workflow. Do not copy only a few Swift files into a second folder.

3. Give the agent a narrow task

Name the desired result and explicitly protect signing, entitlements, bundle identity, deployment targets, and unrelated project settings unless the task requires them.

4. Review the complete diff

Check every changed file before accepting the work. Pay special attention to Xcode project configuration and files the agent did not need to touch.

5. Build and test before returning

Run the app in Xcode or Superapp, test the affected flow, and commit the working result. If Superapp was open during the edit, reopen or refresh the project before continuing.

Changes that need extra care

A coding agent can modify more than Swift source. Seemingly small configuration changes can stop signing, device builds, cloud features, or App Store submission from working.

• Signing: development team, certificates, provisioning, and automatic signing settings.
• Identity: bundle identifier, product name, targets, schemes, and build configurations.
• Entitlements: iCloud, Sign in with Apple, push notifications, HealthKit, app groups, keychain groups, and associated domains.
• Build environment: deployment target, package dependencies, build phases, compiler flags, Info.plist values, and generated project files.
• Connected services: Supabase configuration, API endpoints, secrets, RevenueCat products, and environment-specific values.

A safer agent prompt

Work only inside this existing Swift project.

Implement [describe the change] without changing the bundle identifier, signing team, entitlements, deployment target, schemes, build phases, package dependencies, or unrelated project settings.

Before editing, inspect the current structure. After editing, build the existing scheme and summarize every changed file and configuration value.

If the project stops working

1. Stop making additional changes and save the current diff for diagnosis.
2. Compare it with the last known-good commit, especially project and entitlement files.
3. Revert the external change or restore the saved version.
4. Build again before asking Superapp or another agent to continue.

When asking for help, include the build error and a list of changed files. Remove tokens, certificates, private keys, and other secrets before sharing logs or project content.