One backend, a mobile app and a web app
Solo buildersIndie hacker shipping an iOS app and a web app on one API
We changed the /orders endpoint for the new web dashboard on a Tuesday. The web agent was happy. The iOS app, two versions behind for a third of users, started crashing on the old response shape, and we only found out from App Store reviews.
How do I stop my AI agent from breaking my iOS app when it changes an API endpoint?
Set up ArcRoom with arcroom init in the monorepo, once for each agent you use, then record the rule: arcroom decide "API changes are additive only" --why "mobile users lag versions". Add a rule on the apps/mobile folder saying it still calls /v1. Recall puts the decision and the rule in front of any prompt that touches the API.
Also asked as: An API change for my web app crashed older versions of my iOS app. How do I prevent that? · How do I make an AI agent keep my API backward compatible? · Can an AI agent know which endpoints my mobile app still uses?
Run arcroom init in the monorepo once for each agent we use.
- Code map
- Decision
- Recall
Decision (Oct 3): API changes are additive only.
Step by step
- Run arcroom init in the monorepo once for each agent we use.
- A rule on apps/mobile says it still calls /v1.
- Record the rule once: arcroom decide "API changes are additive only" --why "mobile users lag versions".
- Recall puts the rule and the mobile note in front of any prompt that touches the API.
What the agent sees
Decision (Oct 3): API changes are additive only.
Why: about 30% of iOS users are two versions behind.
Code map: apps/mobile · calls /v1/orders, expects an arrayCompared with today's tools
CLAUDE.md per app folder
Write the additive-only rule into a CLAUDE.md in each app and keep the two files in sync by hand.
- Setup
- 30 min
- Ongoing
- update both files when a rule changes, ~5 min
ArcRoom
Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.
- Setup
- 2 min (npx arcroom init)
- Ongoing
- None
The static file states the rule but can't say which endpoint changed this week, and Cursor or Codex read their own files instead.
Where it stops
Recall picks what fits the prompt. A prompt that never mentions the API may not get the rule.
Try it in your project
Works with the agents your team already uses, and any agent over MCP or the HTTP API.