Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

Codex to the app stores

Setting up Codex for a team: shared AGENTS.md, approval and sandbox rules, secrets

One developer with Codex can rely on habits. A team cannot, because the agent does whatever the configuration on each laptop allows. A few written conventions settle this: what the agent may do without asking, what a person always reviews, and where secrets live.

Free 15-minute call with our team, or call +49 761 519 751 50 (24/7, English + German)

  • Approval guarantee – or money back within 14 days
  • No coding needed
  • One-time payment, free updates
  • 24/7 human support
  • Made in Germany since 2014 · ISO 27001

Why conventions come before speed

Codex runs commands in a sandbox and asks for approval according to the settings each person chooses. Those settings range from read-only to working without any questions. If everyone picks their own, the team has as many risk levels as members, and the most permissive one defines what can go wrong.

For an app that is live in the stores this matters twice. A merged change reaches users with the next deployment, and the project contains things an agent must never handle: signing keys, production credentials, user data.

What the shared AGENTS.md contains

Commands

How to install, test, lint and build. An agent that can verify its own work needs fewer corrections.

Store invariants

Rules every change must respect: account deletion stays reachable, the privacy page stays a real route, digital goods go through in-app purchases.

The forbidden list

Files and actions that are off limits: signing material, production environment files, migrations against the live database, pushing to the main branch.

Definition of done

Tests pass, the summary names every changed file, and anything unfinished is listed openly.

Ownership

The file changes by pull request and is reviewed like code. Personal preferences belong in each person's own configuration.

Four settings to agree on

SettingTeam defaultException
Where the agent may writeOnly inside the project folderNone
Network access during tasksOff, or limited to the package registriesNamed domains for a named task
Approval for commandsAsk before anything that installs, deletes or leaves the sandboxRead-only mode for audits
Working without questionsOnly in disposable environments such as cloud tasks or containersNever on a machine with production access

What a person always reviews

  • Login, sessions and everything that decides who a user is.
  • Data access rules: who may read or change which records.
  • Payments, in-app purchases and the webhooks behind them.
  • Account deletion, because the stores expect that it really deletes.
  • New dependencies and changes to the lockfile.
  • Pipeline configuration and build scripts.
  • Permissions and capabilities in the native project.

Rolling it out

Start with one repository. Write the shared file together in one session, with the AGENTS.md template as a base, agree on the four settings, and protect the main branch so that the platform enforces the review rule.

Our team runs hands-on workshops on exactly this, with playbooks for AGENTS.md and code review and workflows aligned with ISO 27001. To plan one for your team, book a free call.

Frequently asked questions

Does everyone have to use the same approval settings?

Agree on a minimum. Stricter is always allowed. Looser settings are only for disposable environments without production access.

May Codex push to the main branch?

No. It works on branches and opens pull requests. Branch protection makes sure a person approves each merge.

Where do personal instructions go?

Into the personal configuration of each developer. The AGENTS.md in the repository holds only what is true for the whole team and the whole project.

How do we handle freelancers and contractors?

Same file, same settings, and test credentials only. Access to store consoles and signing keys is granted separately and only when needed.

Three ways to get your app into the stores

Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.

Do it yourself

$109 per platform, one-time

The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.

See plans on the main page

Cloud Builder

$349 per license, one-time add-on

No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.

How the Cloud Builder works Try the free demo

Full Service

$698 per platform $798

Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.

Full Service details Powered by WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Talk it through with our team

Free 15-minute call: your app, your tools, your next step

Rather start right away? See plans and pricing or hand it over with Full Service.