Skip to content
Back to search

play-console-cli

Fast CLI for Google Play Console, for developers optimized for your agentic development flows

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/tamtom/play-console-cli with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/tamtom/play-console-cli'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/tamtom--play-console-cli/badge.svg)](/listings/tamtom--play-console-cli)

HTML

<a href="/listings/tamtom--play-console-cli"><img src="/api/listings/tamtom--play-console-cli/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

Install

# Homebrew (recommended)
brew tap tamtom/tap
brew install tamtom/tap/gplay

# Standalone binary — macOS/Linux
curl -fsSL https://raw.githubusercontent.com/tamtom/play-console-cli/main/install.sh | bash

# Standalone binary — Windows (PowerShell)
irm https://raw.githubusercontent.com/tamtom/play-console-cli/main/install.ps1 | iex

**Update:** `gplay update` verifies the release SHA-256 checksum before replacing a standalone binary. Homebrew and Go installations receive the appropriate update command. Successful interactive commands suggest newer stable releases on stderr, using a 24-hour cache; a failed check waits one hour before the next try. Help, version, completion, CI, piped commands, and development builds (`git describe` versions) skip automatic checks. Set `GPLAY_NO_UPDATE` to `1`, `true`, or `yes` to disable suggestions or run `gplay update --check` explicitly. Source builds require Go 1.27.1 or newer.

After your first successful metadata push, edit commit, or release with `gh` installed, gplay prints an optional star suggestion to stderr. It never waits for input or stars automatically: agents must ask you first. Set `GPLAY_NO_STAR_PROMPT=1` to suppress the suggestion. See [configuration](docs/configuration.md).

Authentication

`gplay` authenticates to Google Play with a **service account**.

One-command setup (recommended)

gplay setup --auto

That's it. This will: - Install `gcloud` if needed (via Homebrew on macOS, or curl on Linux) - Log you into Google Cloud - Create a service account and download credentials - Open Play Console for the one manual step (granting access) - Configure everything automatically

Pass `--project <id>` if `gcloud` has no default project, `--dry-run` to preview the commands, or `--no-browser` for CI/agent runs. Then verify with `gplay auth doctor`.

Already have a service account key?

gplay auth login --service-account /path/to/service-account.json

Manual setup

<details> <summary>Set up the service account by hand (full control)</summary>

**Step 1: Create a Google Cloud Project** 1. Go to [Google Cloud Console](https://console.cloud.google.com) 2. Create a new project or select an existing one 3. Note your project ID

**Step 2: Enable the API** 1. Go to **APIs & Services > Library** 2. Search for "Google Play Android Developer API" 3. Click **Enable**

**Step 3: Create a Service Account** 1. Go to **IAM & Admin > Service Accounts** 2. Click **Create Service Account** 3. Give it a name (e.g., "gplay-cli") 4. Click **Create and Continue**, then **Done** 5. Click on the created service account 6. Go to **Keys > Add Key > Create new key > JSON** 7. Save the downloaded JSON file securely

**Step 4: Grant Access in Play Console** 1. Go to [Google Play Console](https://play.google.com/console) 2. Go to **Users and permissions > Invite new users** 3. Enter the service account email (from the JSON file, looks like `name@project.iam.gserviceaccount.com`) 4. Set permissions (Admin or specific app access) 5. Click **Invite user**

**Step 5: Login with gplay**

gplay auth login --service-account /path/to/service-account.json

# Verify it works
gplay auth doctor

</details>

Profiles for multiple accounts and troubleshooting: **[docs/authentication.md](docs/authentication.md)**

Once authenticated, you're ready to go:

# Ship a release in one command
gplay release --package com.example.app --track production --bundle app.aab --rollout 0.1

# Create a subscription with base plans and offers
gplay subscriptions create --package com.example.app --json @subscription.json

# Everything outputs minified JSON — built for agents and pipes
gplay reviews list --package com.example.app | jq '.reviews[0]'

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 209 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # gplay — Google Play Console CLI for AI Agents
  2. <p align="center">
  3. <img src="https://img.shields.io/badge/Go-1.27.3+-00ADD8?style=for-the-badge&logo=go" alt="Go Version">
  4. <img src="https://img.shields.io/badge/License-MIT-yellow?style=for-the-badge" alt="License">
  5. <img src="https://img.shields.io/badge/Homebrew-compatible-blue?style=for-the-badge" alt="Homebrew">
  6. </p>
  7. **gplay** is a fast, single-binary CLI for **Google Play Console**, built for **AI coding agents** — Claude Code, Codex, Cursor, Gemini CLI — and for humans who script. Release Android apps, create **subscriptions, in-app products, and one-time purchases**, verify purchases server-side, and monitor crashes and reviews through documented Google APIs.
  8. It replaces Play Console clicking for many day-to-day workflows. Most deployment tools only handle standard AAB uploads — gplay supports **250+ commands across 9 official Google APIs**: Android Publisher, Play Developer Reporting, Checks, both Play Games admin APIs, Managed Google Play, Play Integrity, Android Developer ID Status, and Cloud Storage for reports. Initial public-app setup, first upload, ordinary Google-managed Play App Signing enrollment, and legal declarations still require a manual Play Console handoff. Enterprise self-hosted Cloud KMS signing is supported through its separate official API. Gplay does not use private Console endpoints or authenticated browser automation.
  9. ## Table of Contents
  10. - [Quick Start](#quick-start)
  11. - [Install](#install)
  12. - [Authentication](#authentication)
  13. - [Highlights](#highlights)
  14. - [Use it with your AI agent](#use-it-with-your-ai-agent)
  15. - [How gplay compares](#how-gplay-compares)
  16. - [Documentation](#documentation)
  17. - [Contributing](#contributing)
  18. - [License](#license)
  19. ## Quick Start
  20. ### Install
  21. ```bash
  22. # Homebrew (recommended)
  23. brew tap tamtom/tap
  24. brew install tamtom/tap/gplay
  25. # Standalone binary — macOS/Linux
  26. curl -fsSL https://raw.githubusercontent.com/tamtom/play-console-cli/main/install.sh | bash
  27. # Standalone binary — Windows (PowerShell)
  28. irm https://raw.githubusercontent.com/tamtom/play-console-cli/main/install.ps1 | iex
  29. ```
  30. **Update:** `gplay update` verifies the release SHA-256 checksum before replacing a standalone binary. Homebrew and Go installations receive the appropriate update command. Successful interactive commands suggest newer stable releases on stderr, using a 24-hour cache; a failed check waits one hour before the next try. Help, version, completion, CI, piped commands, and development builds (`git describe` versions) skip automatic checks. Set `GPLAY_NO_UPDATE` to `1`, `true`, or `yes` to disable suggestions or run `gplay update --check` explicitly. Source builds require Go 1.27.3 or newer.
  31. After your first successful metadata push, edit commit, or release with `gh` installed, gplay
  32. prints an optional star suggestion to stderr. It never waits for input or
  33. stars automatically: agents must ask you first. Set `GPLAY_NO_STAR_PROMPT=1`
  34. to suppress the suggestion. See [configuration](docs/configuration.md).
  35. ### Authentication
  36. `gplay` authenticates to Google Play with a **service account**.
  37. #### One-command setup (recommended)
  38. ```bash
  39. gplay setup --auto
  40. ```
  41. That's it. This will:
  42. - Install `gcloud` if needed (via Homebrew on macOS, or curl on Linux)
  43. - Log you into Google Cloud
  44. - Create a service account and download credentials
  45. - Open Play Console for the one manual step (granting access)
  46. - Configure everything automatically
  47. Pass `--project <id>` if `gcloud` has no default project, `--dry-run` to preview the commands, or `--no-browser` for CI/agent runs. Then verify with `gplay auth doctor`.
  48. Already have a service account key?
  49. ```bash
  50. gplay auth login --service-account /path/to/service-account.json
  51. ```
  52. #### Manual setup
  53. <details>
  54. <summary>Set up the service account by hand (full control)</summary>
  55. **Step 1: Create a Google Cloud Project**
  56. 1. Go to [Google Cloud Console](https://console.cloud.google.com)
  57. 2. Create a new project or select an existing one
  58. 3. Note your project ID
  59. **Step 2: Enable the API**
  60. 1. Go to **APIs & Services > Library**
  61. 2. Search for "Google Play Android Developer API"
  62. 3. Click **Enable**
  63. **Step 3: Create a Service Account**
  64. 1. Go to **IAM & Admin > Service Accounts**
  65. 2. Click **Create Service Account**
  66. 3. Give it a name (e.g., "gplay-cli")
  67. 4. Click **Create and Continue**, then **Done**
  68. 5. Click on the created service account
  69. 6. Go to **Keys > Add Key > Create new key > JSON**
  70. 7. Save the downloaded JSON file securely
  71. **Step 4: Grant Access in Play Console**
  72. 1. Go to [Google Play Console](https://play.google.com/console)
  73. 2. Go to **Users and permissions > Invite new users**
  74. 3. Enter the service account email (from the JSON file, looks like `name@project.iam.gserviceaccount.com`)
  75. 4. Set permissions (Admin or specific app access)
  76. 5. Click **Invite user**
  77. **Step 5: Login with gplay**
  78. ```bash
  79. gplay auth login --service-account /path/to/service-account.json
  80. # Verify it works
  81. gplay auth doctor
  82. ```
  83. </details>
  84. Profiles for multiple accounts and troubleshooting: **[docs/authentication.md](docs/authentication.md)**
  85. Once authenticated, you're ready to go:
  86. ```bash
  87. # Ship a release in one command
  88. gplay release --package com.example.app --track production --bundle app.aab --rollout 0.1
  89. # Create a subscription with base plans and offers
  90. gplay subscriptions create --package com.example.app --json @subscription.json
  91. # Everything outputs minified JSON — built for agents and pipes
  92. gplay reviews list --package com.example.app | jq '.reviews[0]'
  93. ```
  94. ## Highlights
  95. - **Current official API coverage** — the reviewed manifest tracks 218 methods across eight Play-specific discovery APIs, plus the two Cloud Storage methods needed for reports. All 145 current Android Publisher methods have a CLI path; specialized third-party-store and enterprise-KMS commands are explicitly scope-gated.
  96. - **Explicit safety boundary** — `gplay capabilities` distinguishes official, manual, and unsupported workflows; `gplay bootstrap plan` prepares initial app setup without logging in, contacting Google, or changing an account.
  97. - **Agent-native discovery** — `gplay search` ranks commands, examples, flags, and canonical intents locally; `gplay schema` embeds all 218 reviewed endpoints and 568 official request/response definitions with no credentials or network access.
  98. - **Resilient one-shot workflows** — workflow steps support opt-in bounded retries and per-attempt timeouts, persist structured attempt diagnostics, fingerprint definitions, and refuse ambiguous or changed-definition resumes.
  99. - **Local weekly/daily insights** — compare installs, uninstalls, crashes, ANRs, and store-listing conversion from official Google Play CSV exports; UTF-8/UTF-16 are supported and missing metrics remain explicitly unavailable.
  100. - **Managed Google Play** — publish private (custom) apps to specific organizations with `gplay custom-apps create`, straight from the terminal.
  101. - **Complete releases & rollouts** — upload, track assignment, staged rollout with pause/resume/percentage control, promote between tracks, release notes from git history.
  102. - **Store listings, screenshots & localization** — manage listing text, images, and metadata across every locale; sync with a local directory or Fastlane.
  103. - **Full monetization stack** — subscriptions, base plans, promotional offers, in-app products, one-time purchases, regional price conversion. Pairs with [RevenueCat](docs/monetization.md#using-gplay-with-revenuecat): create products in Play with `gplay`, import them into RevenueCat.
  104. - **Purchase verification** — verify tokens, acknowledge purchases, refund orders, decode RTDN webhooks.
  105. - **Offline preflight** — `gplay preflight --file app.aab` fully decodes `AndroidManifest.xml` (binary AXML for APKs, aapt2 protobuf for App Bundles) and runs nine scanners with no API calls and no credentials: manifest flags, restricted permissions, 64-bit and **16 KB page alignment**, listing text and real screenshot dimensions, secrets, billing, privacy SDKs, target API floor, and size. Catches the rejections *before* you upload.
  106. - **App health** — crash clusters, ANRs, performance vitals, review replies, financial & statistics reports.
  107. - **Integrity and verification** — decode Android/PC Play Integrity tokens, safely gate Device Recall writes, and check Android Developer ID package/certificate registration.
  108. - **AI-agent native** — minified JSON output, explicit flags, `--help` everywhere, `--dry-run` for every write, no interactive prompts, [Agent Skills](docs/ai-agents.md) included.
  109. - **Lightweight, zero runtime to install** — a single compiled Go binary with instant startup. No Node.js, no Python, no JVM, no Gradle project required.
  110. ## Use it with your AI agent
  111. Every command is discoverable via `--help`, outputs token-efficient JSON, and never blocks on a prompt — so agents can drive the whole Play workflow. Install the ready-made skills:
  112. ```bash
  113. # Inspect the immutable, checksum-verified install plan (no network or writes)
  114. gplay install-skills --preview
  115. # Install the reviewed skill pack without npm/npx or executing repository code
  116. gplay install-skills
  117. ```
  118. The installer pins one reviewed Git commit and verifies every skill tree before an atomic install. Existing skills are never replaced unless `--force` is explicit.
  119. Then ask your agent things like *"release this AAB to internal"*, *"create monthly + yearly subscriptions with a 7-day trial and convert prices for all regions"*, or *"summarize this week's crash clusters"*. Full guide: **[docs/ai-agents.md](docs/ai-agents.md)**
  120. ## How gplay compares
  121. Versus [Fastlane `supply`](https://docs.fastlane.tools/actions/supply/) and [gradle-play-publisher](https://github.com/Triple-T/gradle-play-publisher) (all three cover AAB/APK upload, tracks, rollouts, and listings equivalently):
  122. | Capability | gplay | Fastlane supply | gradle-play-publisher |
  123. |---|---|---|---|
  124. | Subscriptions, base plans, offers, one-time purchases | ✅ Full | ❌ | ⚠️ Basic (no base plans/offers) |
  125. | Purchase verification, orders, refunds | ✅ | ❌ | ❌ |
  126. | Vitals: crashes, ANRs, performance | ✅ | ❌ | ❌ |
  127. | Reviews: read + reply | ✅ | ❌ | ❌ |
  128. | Financial & statistics reports | ✅ | ❌ | ❌ |
  129. | Users & permission grants | ✅ | ❌ | ❌ |
  130. | Offline preflight (manifest decode, 16 KB alignment, secrets) | ✅ 9 scanners | ❌ | ❌ |
  131. | Managed Google Play (private/custom apps) | ✅ | ❌ | ❌ |
  132. | Google Checks compliance gate | ✅ | ❌ | ❌ |
  133. | AI-agent-friendly output | ✅ JSON default | ❌ Human logs | ❌ Gradle logs |
  134. | Runtime | Single Go binary | Ruby + gems | JVM + Gradle project |
  135. ## Documentation
  136. | Guide | What's inside |
  137. |-------|---------------|
  138. | **[Command reference (GPLAY.md)](GPLAY.md)** | Every command and flag, auto-generated |
  139. | [Authentication](docs/authentication.md) | Service account setup, profiles, `auth doctor` |
  140. | [Releasing](docs/releasing.md) | Releases, rollouts, listings, testers, pre-submission checks, Fastlane interop |
  141. | [Monetization](docs/monetization.md) | Subscriptions, IAP, one-time purchases, pricing, purchase verification, RevenueCat |
  142. | [Monitoring & operations](docs/monitoring.md) | Vitals, reviews, reports, users, notifications, diagnostics |
  143. | [AI agents](docs/ai-agents.md) | Agent setup, skills, example prompts |
  144. | [Configuration](docs/configuration.md) | Config file, env vars, output formats, shell completion |
  145. | [CI/CD](docs/ci-cd.md) | GitHub Actions, GitLab CI, release gates |
  146. | [Policy-safe automation](docs/policy-safe-automation.md) | Official API boundary and manual Play Console handoffs |
  147. | [Official API audit](docs/research/google-play-go-api-audit-2026-08-23.md) | Versions, method inventory, gaps, and testing boundary |
  148. | [Contributing](CONTRIBUTING.md) | Development setup, testing, PR guidelines |
  149. ## Contributing
  150. Contributions welcome — see [CONTRIBUTING.md](CONTRIBUTING.md). Quick local check: `make dev` (format + lint + test + build).
  151. ## License
  152. MIT — see [LICENSE](LICENSE).
  153. ---
  154. <p align="center">
  155. Built with Go and <a href="https://github.com/peterbourgon/ff">ffcli</a>
  156. </p>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.