Skip to main content

FlightDeck Documentation & AI Prompt Catalog

A tested library of copy-paste prompts and operational patterns to command your AI coding agent (Claude Desktop, Cursor, Antigravity IDE) to manage App Store Connect directly from your editor.

Looking for raw context to feed your LLM?

We provide a token-optimized, zero-cruft Markdown file formatted specifically for AI system prompts and agent references.

Architecture Invariants & Dual-Layer Mutation Safety

Before commanding an AI agent, understand how FlightDeck ensures security, privacy, and full developer control over your App Store presence:

Local Loopback Only

FlightDeck binds strictly to local loopback (http://127.0.0.1:51122/mcp by default). No third-party proxy, relay, or cloud database sits between your Mac and Apple.

macOS Keychain Security

Private .p8 API keys reside in the secure macOS Keychain. FlightDeck signs ES256 JWTs locally with 15-minute expirations.

Apple is Authoritative

FlightDeck maintains zero shadow database. All reads query live Apple resources, and mutations target live Apple endpoints directly.

Human Approval Center

With AI Approval: ON (default), mutations create a staged change set. You inspect structured visual cards and field-level diffs in macOS before authorizing execution.

No matching prompts found

Try searching for a different keyword or resetting your category filter.

⚡ Quickstart: Connect FlightDeck to Your AI Assistant

Connect your Mac, App Store Connect, and your AI assistant in five straightforward steps. FlightDeck runs an embedded Model Context Protocol (MCP) server listening strictly on local loopback (default: http://127.0.0.1:51122/mcp) over Streamable HTTP transport.

Step 1: Install FlightDeck Desktop & Connect App Store Connect

Download FlightDeck from the Mac App Store (macOS 12.0+). In Apple’s developer portal (Users and Access → Integrations → App Store Connect API), generate an API key:

Team API Key (Recommended)

Generated under Team Keys by an Account Holder or Admin. Grants access across apps in your organization.

  • Key ID: 10-character alphanumeric identifier
  • Issuer ID: UUID shown above the table
  • Private Key: Downloaded .p8 file

Individual API Key

Generated under Individual Keys tied to your personal developer account across teams.

  • Key ID: 10-character alphanumeric identifier
  • Private Key: Downloaded .p8 file (no Issuer ID needed)
  • Note: Apple restricts Individual keys from Sales/Finance and Provisioning

In FlightDeck, click Add Account. Your credentials are saved securely into your encrypted macOS Keychain (kSecClassGenericPassword). FlightDeck never operates an intermediary cloud database; API requests travel directly between your Mac and Apple over HTTPS. See our API Keys Guide and Team vs Individual Keys Guide.

Step 2: Enable the Local MCP Server in FlightDeck

In FlightDeck Desktop, open the MCP Server settings screen and click Start Server.

Default Endpoint & Transport

FlightDeck binds to local loopback over Streamable HTTP transport:

http://127.0.0.1:51122/mcp

Important: 51122 is the shipping default port. If you configured a custom port in FlightDeck settings, always use the exact port and endpoint URL displayed in your running FlightDeck Desktop window.

In-App Setup Assistant

Click Copy Setup Prompt in the MCP Server view. This generates a tailored prompt containing your active endpoint URL, port, and security settings to paste into your AI assistant.

Step 3: Connect Your AI Coding Assistant

Configure FlightDeck in your preferred AI coding tool. Select your client below for exact configuration syntax:

Cursor

Configure in ~/.cursor/mcp.json or Cursor Settings → Features → MCP → Add New MCP Server:

{
  "mcpServers": {
    "flightdeck": {
      "url": "http://127.0.0.1:51122/mcp"
    }
  }
}

Read Full Cursor Setup Guide →

Claude Code CLI

Register directly from Terminal using explicit HTTP transport:

claude mcp add --transport http flightdeck http://127.0.0.1:51122/mcp

Add --scope user to make it available across all directories.

Read Full Claude Code Setup Guide →

Google Antigravity IDE

Add to global configuration in ~/.gemini/config/mcp_config.json (or project .gemini/config/mcp_config.json):

{
  "mcpServers": {
    "flightdeck": {
      "url": "http://127.0.0.1:51122/mcp"
    }
  }
}

Read Full Antigravity Setup Guide →

Windsurf & Roo Code

Windsurf: in ~/.codeium/windsurf/mcp_config.json using "serverUrl":

{"mcpServers": {"flightdeck": {"serverUrl": "http://127.0.0.1:51122/mcp"}}}

Roo Code: in cline_mcp_settings.json with "type": "streamable-http" (legacy SSE is rejected):

{"mcpServers": {"flightdeck": {"type": "streamable-http", "url": "http://127.0.0.1:51122/mcp"}}}

Read Full Windsurf & Roo Code Guide →

Security Warning: Bearer Token & Credential Protection

If you enable Require Password in FlightDeck’s MCP Server settings, the generated setup prompt will contain an HTTP Bearer authentication token. Treat this token as confidential:

  • Never commit configuration files with Bearer tokens to Git repositories. Use user-level configuration files rather than shared project repositories.
  • Never paste Apple .p8 private keys or authentication tokens into AI chats, shared Discord/Slack channels, or public issue trackers.
  • Never publish screenshots displaying active authentication tokens.
  • Always verify that your AI client connects strictly to local loopback (127.0.0.1) and uses the active port configured in FlightDeck Desktop.

Step 4: Verify Connection with Your First Read-Only Prompt

Open your AI assistant (Cursor Composer, Claude Code, Antigravity Chat, or Windsurf Cascade) and paste this initial smoke-test prompt:

First Smoke Test Prompt
Using FlightDeck, show me the apps available in my App Store Connect account and their bundle identifiers. Do not make any changes.
What Success Looks Like:
Your assistant discovers FlightDeck's MCP tools, executes the read-only apps_list tool, and reports a structured list of your App Store Connect apps, App IDs, and bundle identifiers without making any changes.
Troubleshooting First Connection:
  • MCP Server Unreachable (ECONNREFUSED): FlightDeck is not running or MCP Server is turned off. Open FlightDeck, navigate to MCP Server, click Start Server, and confirm your client config matches the displayed port (default 51122).
  • MCP Authentication Failed (HTTP 401 Unauthorized): Password authentication is enabled in FlightDeck Desktop. Ensure your client configuration includes the Authorization: Bearer <TOKEN> header.
  • MCP Connected but Tools Unavailable: In FlightDeck's Capability Permissions tab, ensure the relevant functional capability is set to Read or Read + Write.
  • FlightDeck Connected but Apple Authentication Failed (HTTP 401/403 from Apple): Your App Store Connect API key was revoked, expired, or entered with an incorrect Key ID or Issuer ID. Check Apple API Profiles in FlightDeck.
  • Apple Connected but Zero Apps Returned: Your Apple API key does not have permission to view specific apps, or no apps exist yet. Check user permissions in Apple's Users and Access portal.

Step 5: How Mutations Work (Human-in-the-Loop Governance)

Read queries execute immediately with zero approval needed. But what happens when an AI assistant wants to update release notes, add TestFlight testers, or submit a build?

Staged Change Sets & Visual Cards

With AI Approval: ON (default for every capability), mutating operations do NOT execute directly against Apple. Instead, FlightDeck intercepts the mutation and creates a staged proposal in the native macOS Approval Center.

Native Decision Controls

In the Approval Center, you inspect structured visual cards showing the target app, version, proposed operation, and before-and-after field diffs. You can:

  • Approve Mutation (or Approve All) to execute directly against Apple's REST API.
  • Request Changes to send feedback back to your AI assistant across MCP.
  • Reject to safely discard the proposal with zero impact on Apple.

Note: Approving a mutation authorizes FlightDeck to send it to Apple; Apple independently validates business rules and schema invariants. For details, see our Approval Center & Human Governance Guide and Execution vs Staging Rules Guide.

🚀 1. Release Management & App Store Review

Automate pre-flight submission readiness audits, version creation, build linking, prerequisite attestations, guideline verification, rejection triage, and submission to Apple App Review.

PROMPT 1.1

Pre-Flight Release Readiness Audit

Check if an upcoming release version satisfies all App Store Connect submission requirements and guideline prerequisites.

Read-Only
Agent Prompt
Run a FlightDeck pre-flight release readiness check on [AppName] for version [version]. Highlight any missing localized metadata, unattached builds, missing compliance declarations, or blocker diagnostics.
What Agent Does:
Calls apps_list to resolve bundle ID, app_store_versions_list to locate target version, and release_readiness_check / release_submission_diagnostics_get to audit version completeness against Apple requirements.
Safety & Approval:
Read-only operation. Zero risk to production state.
PROMPT 1.2

Prepare & Stage a New App Store Version

Create a new version draft in App Store Connect for an upcoming release.

Mutation — Staged
Agent Prompt
Prepare a new App Store release version [version] for [AppName] targeting [iOS/macOS]. Stage the version creation in FlightDeck so I can review it in the Approval Center.
What Agent Does:
Checks current live versions via app_store_versions_list, validates that no unreleased version is in draft, and stages app_store_version_create via flightdeck_operation_stage.
Safety & Approval:
Mutation operation (releases capability). Creates a staged change set requiring developer sign-off in FlightDeck before calling Apple.
PROMPT 1.3

Select & Attach Candidate Build to Version

Find eligible processed builds and associate the chosen build with the release version.

Mutation — Staged
Agent Prompt
Find the latest valid candidate builds for [AppName] version [version], and attach build number [buildNumber] to the [version] release draft.
What Agent Does:
Queries release_build_candidates to filter processed builds matching the version string, verifies export compliance via build_get, and stages release_build_select.
Safety & Approval:
Mutation operation (releases + builds). Staged for developer sign-off in the Approval Center.
PROMPT 1.4

Attest Release Prerequisites & Export Compliance

Clear mandatory Apple submission blockers, such as encryption declarations (ITSAppUsesNonExemptEncryption), third-party content rights, or EU trader status.

Mutation — Staged
Agent Prompt
Check all pending external release prerequisites for [AppName] version [version]. Attest standard encryption exemptions (ITSAppUsesNonExemptEncryption = NO) and confirm content rights so the build can be submitted without blockers.
What Agent Does:
Calls release_external_prerequisites_list to identify unfulfilled attestations on the release or attached build, verifies compliance criteria, and calls release_external_prerequisite_attest for each required key.
Safety & Approval:
Mutation operation (releases). Eliminates manual popup modals in the App Store Connect web interface.
PROMPT 1.5

Comprehensive App Store Review Guideline Audit

Audit metadata, binary entitlements, and privacy declarations against Apple's official App Store Review Guidelines.

Read-Only
Agent Prompt
Audit our release candidate for [AppName] against the App Store Review Guidelines. Check our App Store version metadata, privacy manifests, external prerequisites, and submission items for common rejection triggers.
What Agent Does:
Calls review_submission_items_inspect and release_external_prerequisites_list, cross-references localized strings with Guideline rules (login notes, Guideline 2.1, 5.1.1 privacy), and outputs a structured compliance report.
Safety & Approval:
Read-only analysis. Highly recommended prior to review submission.
PROMPT 1.6

Create Review Submission Draft & Submit

Assemble review items, run preflight validation, and submit the final release package to Apple App Review.

Mutation — Staged
Agent Prompt
Assemble an App Store Review submission draft for [AppName] version [version], run preflight validation, and if clean, submit it for Apple review.
What Agent Does:
Calls review_submission_create_draft, attaches version with review_submission_add_app_version, executes review_submission_preflight, and stages review_submission_submit.
Safety & Approval:
High-impact mutation (releases). Always stages the action or confirms with the developer prior to final submission.
PROMPT 1.7

App Review Rejection Triage & Remediation Plan

Analyze rejection notes from Apple App Review, map them to official guidelines, and generate an immediate fix plan.

Read-Only
Agent Prompt
Inspect the latest review submission status and reviewer rejection notes for [AppName] version [version]. Identify the exact guideline violation (e.g. 2.1 or 5.1.1), explain the cause, and outline the exact code or metadata fix required to resolve it.
What Agent Does:
Queries review_submissions_list and review_submission_items_inspect to retrieve reviewer feedback attachments, parses diagnostic failure codes, and formulates a remediation diff.
Safety & Approval:
Read-only analysis. Extracts Apple feedback attachments without altering remote status.
PROMPT 1.8

Cancel Active Review Submission

Pull back a version currently waiting for review or in review to fix critical regressions.

Mutation — Staged
Agent Prompt
Check the current review submission status of [AppName], and cancel the pending review submission for version [version].
What Agent Does:
Inspects active review submissions with review_submissions_list, extracts the submission ID, and calls review_submission_cancel.
Safety & Approval:
Mutation operation (releases). Safely retracts the build from Apple's queue.

🌐 2. Metadata, Localization & ASO

Audit release notes across global locales, translate "What's New" text, synchronize disk metadata (Fastlane/Git), optimize keyword densities, and manage global app subtitles.

PROMPT 2.1

Audit & Diff Localized Release Notes ("What's New")

Review release notes across all active languages to find missing translations or formatting discrepancies.

Read-Only
Agent Prompt
Fetch the 'What's New' release notes for [AppName] version [version] across all configured locales. Show me a table of all locales, character counts, and flag any languages missing release notes.
What Agent Does:
Queries app_store_version_localizations_list for version ID, extracts whatsNew for each locale, calculates character counts (Apple limit: 4,000 characters), and formats a comparative table.
Safety & Approval:
Read-only operation. Zero risk to production state.
PROMPT 2.2

Synchronize Localized Release Notes from Changelog

Generate or update localized "What's New" release notes across multiple languages from a Git changelog or summary draft.

Mutation — Staged
Agent Prompt
Update the 'What's New' release notes for [AppName] version [version] across [en-US, de-DE, ja, es-ES] using the following release summary: [summaryText]. Keep the tone professional, highlight key fixes, and stage the localized updates in FlightDeck.
What Agent Does:
Adapts the summary text to native phrasing for each locale, calls app_store_version_localization_update per language, and stages the batch in a FlightDeck change set with flightdeck_change_set_stage.
Safety & Approval:
Mutation operation (releases). Staged as an atomic change set in the Approval Center showing side-by-side diffs.
PROMPT 2.3

Sync Local Git / Fastlane Metadata to App Store Connect

Sync on-disk metadata files (e.g. fastlane/metadata/ or locales/*.json) with live App Store Connect records.

Mutation — Staged
Agent Prompt
Compare our local store metadata files in "[path/to/metadata]" with live App Store Connect metadata for [AppName] version [version]. Stage updates for any title, subtitle, description, or keyword changes that differ from disk.
What Agent Does:
Reads local files from disk, queries app_store_version_localizations_list and app_info_localizations_list, computes field-level diffs, and creates a staged change set via flightdeck_change_set_stage.
Safety & Approval:
Mutation operation (releases / apps). Provides an atomic reviewable batch in FlightDeck before touching Apple.
PROMPT 2.4

ASO Keyword Audit & Refresh

Inspect current keywords, subtitles, and promotional text, and stage optimized strings for better App Store discoverability.

Mutation — Staged
Agent Prompt
Inspect the current primary locale metadata (title, subtitle, keywords) for [AppName] version [version]. Propose an optimized 100-character keyword string and a high-converting 30-character subtitle, then stage the updates.
What Agent Does:
Calls app_store_version_localization_get to retrieve existing keywords, validates strict Apple constraints (max 100 chars comma-delimited, no spaces after commas), formats payload, and stages via app_store_version_localization_update.
Safety & Approval:
Mutation operation (releases). Displays before/after comparison before staging.
PROMPT 2.5

Update App Information (Name & Subtitle across Locales)

Manage global app identity attributes governed at the app info level.

Mutation — Staged
Agent Prompt
Check the App Info localizations for [AppName]. Update the subtitle for locale [locale] to "[newSubtitle]" without modifying the primary app title.
What Agent Does:
Calls app_info_localizations_list, locates the target locale record ID, and calls app_info_localization_update with the updated subtitle.
Safety & Approval:
Mutation operation (apps). Subject to Apple character constraints (max 30 characters).

🧪 3. TestFlight & Build Delivery (Build & Upload)

Direct the local compiler, upload binaries via FlightDeck, transform Git changelogs into "What to Test" notes, monitor processing pipelines, and manage beta groups.

PROMPT 3.1

Build & Upload Local Binary to App Store Connect

Direct the local compiler to archive and export the app, validate the binary against Apple requirements, and stream it to App Store Connect via FlightDeck.

Binary Upload
Agent Prompt
Build a release binary for [AppName] with version [version] and build number [buildNumber]: 1. Run the local build command to produce the distribution artifact (.ipa for iOS or .pkg/.zip for macOS). 2. Run build_upload_preview on the generated artifact to verify bundle ID, CFBundleShortVersionString, and CFBundleVersion against Apple App ID [appId]. 3. If clean, execute build_upload_start to upload the binary to App Store Connect. 4. Monitor build_upload_status until upload completion.
What Agent Does:
Executes compiler (xcodebuild, flutter build ipa, or fastlane gym), validates binary with build_upload_preview, initiates upload with build_upload_start, and tracks progress via build_upload_status.
Safety & Approval:
High-impact mutation (uploads). Staged for developer approval if uploads capability has AI Approval enabled.
PROMPT 3.2

Git Changelog → TestFlight "What to Test" Notes

Extract recent Git commits since the last release tag and publish them as TestFlight beta notes.

Mutation — Staged
Agent Prompt
Inspect recent Git commits since the previous release tag for [AppName]. Generate concise, tester-friendly "What to Test" bullet points and attach them to the latest build in the "[BetaGroupName]" TestFlight group.
What Agent Does:
Executes git log [last_tag]..HEAD --oneline locally, synthesizes tester notes, queries beta_groups_list and builds_list, and invokes build_add_to_beta_group.
Safety & Approval:
Mutation operation (testflight). Triggers distribution notifications to beta testers.
PROMPT 3.3

Inspect Recent Build Ingestion & Processing Status

Monitor newly uploaded .ipa or .pkg binaries as Apple processes them.

Read-Only
Agent Prompt
List the 5 most recent builds for [AppName]. Show their build numbers, processing status, expiration dates, and whether export compliance is required or missing.
What Agent Does:
Calls builds_list sorted by upload date, extracts processingState (PROCESSING, VALID, FAILED), and calls build_beta_details_get to check encryption/export compliance.
Safety & Approval:
Read-only operation. Zero risk to production state.
PROMPT 3.4

Add Build to Internal / External Beta Groups

Promote a processed build into a TestFlight beta group for immediate testing.

Mutation — Staged
Agent Prompt
Find the latest valid build for [AppName] and add it to the "[BetaGroupName]" TestFlight group. Include the following What to Test notes: "[testNotes]".
What Agent Does:
Calls beta_groups_list to resolve group ID, queries builds_list for the newest VALID build, and calls build_add_to_beta_group.
Safety & Approval:
Mutation operation (testflight). Triggers distribution notifications to testers upon execution.
PROMPT 3.5

Create a Dedicated TestFlight Beta Group

Set up a targeted feedback group for specific QA testers or beta cohorts.

Mutation — Staged
Agent Prompt
Create a new TestFlight external beta group named "[GroupName]" for [AppName] with public link recruitment [enabled/disabled].
What Agent Does:
Calls beta_group_create with the specified app ID, group name, and public link recruitment configuration parameters.
Safety & Approval:
Mutation operation (testflight). Staged for review in FlightDeck.
PROMPT 3.6

Retract Build from TestFlight Distribution

Stop beta testing for a build containing a critical issue or regression.

Mutation — Staged
Agent Prompt
Remove build [buildNumber] of [AppName] from the "[BetaGroupName]" beta group immediately to prevent further tester downloads.
What Agent Does:
Identifies relationship between build and beta group, and executes build_remove_from_beta_group.
Safety & Approval:
Mutation operation (testflight). Halts distribution for the specified group immediately.

🖼️ 4. Storefront Screenshots & Creative Assets

Audit current screenshot coverage across display targets, stage batch uploads from local directories, and bridge simulator automation directly into App Store Connect.

PROMPT 4.1

Audit Storefront Screenshot Sets

Inspect current screenshots across all display types and locales to detect missing device sizes.

Read-Only
Agent Prompt
Inspect all App Store screenshot sets for [AppName] version [version] in [locale]. List which display types have screenshots uploaded, image counts per display type, and flag any missing required device sizes.
What Agent Does:
Calls app_screenshots_list for the version localization, maps screenshots to Apple display targets (APP_IPHONE_67, APP_IPAD_PRO_3GEN_129, APP_DESKTOP), and flags missing requirements.
Safety & Approval:
Read-only operation. Zero risk to production state.
PROMPT 4.2

Generate & Execute Screenshot Upload Plan

Stage a batch upload of local screenshot image files to App Store Connect.

Mutation — Staged
Agent Prompt
Plan and stage a screenshot upload for [AppName] version [version] for locale [locale]. Use the PNG images located in local directory "[localDirectoryPath]" for display type [displayType].
What Agent Does:
Validates image dimensions against Apple specs, creates upload plan with app_screenshot_upload_plan, streams bytes to Apple's presigned S3 storage, and commits via app_screenshot_upload_execute.
Safety & Approval:
Asset mutation operation (media). Progress and reservations are staged in FlightDeck.
PROMPT 4.3

Automated Simulator Screenshot Pipeline to Storefront Upload

Bridge local simulator screenshot automation (Fastlane Snapshot, Maestro, or custom scripts) directly into App Store Connect.

Mutation — Staged
Agent Prompt
Scan our generated simulator screenshots in "[./screenshots/en-US]". Sort the images by target display size (iPhone 6.7", iPhone 6.5", iPad Pro 12.9"), generate an upload plan for [AppName] version [version] in en-US, and stage the upload.
What Agent Does:
Inspects local image headers to categorize dimensions, maps each file to its corresponding Apple display type enum, calls app_screenshot_upload_plan, and stages the upload workflow.
Safety & Approval:
Asset mutation (media). Batch operations are staged and visible in the Approval Center before assets transfer.

💳 5. Pricing, Availability & Monetization

Schedule tier changes, verify international country storefront availability, and upload required App Review proof screenshots for in-app subscriptions.

PROMPT 5.1

Inspect & Update App Price Schedule

Query the active price tier and schedule a future price change.

Mutation — Staged
Agent Prompt
Show the current pricing schedule for [AppName]. Then stage a price schedule update to change the base price tier to [tier/price] starting on [startDate].
What Agent Does:
Queries app_price_schedule_get to retrieve existing tier intervals, formats the price schedule payload, and calls app_price_schedule_set.
Safety & Approval:
High-impact commercial mutation (monetization). Staged for explicit developer sign-off in Approval Center.
PROMPT 5.2

Audit Regional Store Territory Availability

Inspect which international App Store storefronts the app is distributed in.

Read-Only
Agent Prompt
Check the territory availability for [AppName]. List all enabled country storefronts and check if [CountryCode] is currently enabled for distribution.
What Agent Does:
Calls app_availability_get, cross-references Apple territory ISO codes, and summarizes regional availability.
Safety & Approval:
Read-only query (monetization / apps). Zero risk to production state.
PROMPT 5.3

Manage Subscription & IAP Review Screenshots

Upload required review proof screenshots for auto-renewable subscriptions before submitting to Apple.

Mutation — Staged
Agent Prompt
Check if our subscription group "[GroupName]" has a review screenshot attached. If missing, stage an upload of the paywall screenshot from "[localImagePath]".
What Agent Does:
Calls subscription_review_screenshot_get / iap_review_screenshot_get, checks aspect ratio, and stages upload via monetization_review_screenshot_upload.
Safety & Approval:
Mutation operation (monetization). Required by Apple Guideline 2.1 before subscriptions can be approved.

🛡️ 6. Safe Staging, Change Sets & Approvals

Inspect pending change sets staged by your agent, discard draft proposals safely, or trigger sequential execution after human review in FlightDeck.

Approval Center Controls & Request Changes Workflow:

By default, FlightDeck enforces AI Approval: ON for all mutation capabilities. When an agent proposes a write action (such as modifying localized metadata, updating pricing, or submitting a version), FlightDeck stages the request as an immutable Change Set with a cryptographic SHA-256 fingerprint. Staged changes cannot be edited in place.

If a staged proposal requires adjustments, click Request Changes in FlightDeck and provide your guidance. FlightDeck returns this feedback directly to the AI agent across MCP. The agent can then interpret your instructions and submit a revised change set for review.

PROMPT 6.1

Inspect Staged Operations in Approval Center

Review everything an AI agent has staged before committing any changes to Apple.

Governance Query
Agent Prompt
Show me all staged operations currently pending in FlightDeck. List the operation types, targeted resources, and payload summaries.
What Agent Does:
Calls flightdeck_change_set_status or flightdeck_operation_stage_status to inspect pending mutations in the local FIFO approval queue.
Safety & Approval:
Read-only governance inspection. Audits the local queue without calling Apple.
PROMPT 6.2

Cancel or Clear Staged Operations

Discard unintended changes proposed by an agent before they touch App Store Connect.

Local Safety
Agent Prompt
Cancel all staged operations in FlightDeck and clear the pending approval queue.
What Agent Does:
Invokes flightdeck_change_set_cancel or flightdeck_operation_stage_cancel to discard unexecuted local drafts.
Safety & Approval:
Local safety operation. Discards unexecuted drafts without affecting Apple remote state.
PROMPT 6.3

Execute Staged Change Set

Execute a verified batch of operations after human review in FlightDeck.

Execution
Agent Prompt
Execute the currently staged change set in FlightDeck. Report the execution status and Apple API response for each operation.
What Agent Does:
Calls flightdeck_change_set_execute or flightdeck_operation_execute_staged, executing verified operations sequentially and returning full transaction logs.
Safety & Approval:
Mutation execution (releases, apps, media). Only executes if developer has granted necessary write permissions.

⚡ 7. The "One-Shot Ship" (Autonomous Release Pipeline)

The complete, hands-off release workflow from compiler export to App Store Review submission, safely staged for one-click human approval.

PROMPT 7.1

Full End-to-End Autonomous Release Pipeline

Orchestrates compilation, binary upload, version creation, changelog sync, build linking, export compliance, readiness checks, and review submission in a single prompt.

Multi-Step Staged
Agent Prompt
We are ready to release version [version] (build [buildNumber]) for [AppName]: 1. Build and export the signed release binary. 2. Upload the binary to App Store Connect via FlightDeck and verify receipt. 3. Create the [version] release draft and sync localized 'What's New' from our Git changelog. 4. Once the build finishes processing, select it as the release candidate and attest standard export compliance. 5. Run the pre-flight readiness audit and assemble the review submission draft. 6. Stage the final package in FlightDeck so I can click Approve.
What Agent Does:
Executes compiler → calls build_upload_preview → build_upload_start → monitors build_upload_status → prepares version with app_store_version_create → syncs app_store_version_localization_update → attaches build with release_build_select → attests compliance with release_external_prerequisite_attest → verifies readiness with release_readiness_check and review_submission_preflight → creates review package draft via review_submission_create_draft.
Safety & Approval:
The ultimate safety demonstration. Even across a complex 6-step pipeline, all mutations are staged in FlightDeck's native macOS Approval Center, allowing the developer to review the entire batch before a single byte commits to Apple.

💡 Quick Tips for Prompting AI Agents with FlightDeck

Follow these three foundational best practices when writing prompts for Claude, Cursor, or Antigravity IDE.

1

Be Specific About Identifiers

When managing multiple apps or versions, include the exact App Name, Bundle ID, or Apple App ID (e.g. id: "6470000000") in your prompt so the agent immediately picks the correct resource.

2

Combine Read Before Write

Ask the agent to inspect the current state first (e.g., "Check our existing German release notes, and then update them..."). This ensures accurate diffs and prevents unintentional overwrites.

3

Leverage the Approval Center

You never have to trust an AI agent blind. Keep AI Approval: ON in FlightDeck, let your agent stage multi-locale changes, and inspect the structured visual cards and diffs in the native macOS Approval Center before authorizing execution.

⚙️ Setup Reference & Operating Policies

Looking to connect an AI client or configure your App Store Connect credentials? See our complete Quickstart & Agent MCP Setup Guide at the top of this documentation page.

Usage & Rate Limits: FlightDeck imposes zero request caps, metering fees, or operational quotas. App Store Connect API interactions are governed solely by Apple’s standard API rate limits and the subscription or token costs of your AI provider.