storebound/docs/bypass.md

1.5 KiB

Bypass mode

Default off. The owner turns it on once per machine when they want their AI agent to press the owner-only buttons too, instead of stopping and asking:

storebound settings bypass on      # or answer "y" to the question in storebound init
storebound settings bypass status
storebound settings bypass off     # back to the owner pressing every final button, at once

It is stored in ~/.storebound/settings.json (this machine only), never in a project's config or repo.

What it unlocks

  • MCP: the owner_step tool appears. It runs one of: apple submit, apple resubmit, apple iap-submit, apple release, apple preorder, play release, play rollout, reviews (replies), apple testflight (testers), play products, play subscriptions, apple iap, apple subscriptions, prices (live prices). Dry run first (dry_run defaults to true), then dry_run: false runs it with --yes.
  • storebound api: owner-only operations (submit, release, delete, ...) are sent for an agent with --yes --confirm <operationId>.
  • Console plans: the agent may press buttons.final (Publish, Create app, Send for review) itself.

What stays

  • Every owner action an agent runs is appended to <project>/.storebound/owner-actions.log (time, dry or ran, exit code, the command, the last line of its output).
  • Dry runs still come first and must pass.
  • An AI client may still ask the owner for legal agreements, passwords and 2FA codes: those are its own rules, and a storebound setting cannot change them.