GPC
Google Play Console CLI
- Developer Tools
- 2026
- Studio product


- 234Play API endpoints across four APIs
- 23K+npm downloads in the past year
- 2,900+Automated tests across the packages
- 9Offline policy scanners before upload
- 7Packages published on npm
- 19Agent skills for Claude Code
The Google Play Console, run from the terminal. GPC covers 234 publisher endpoints across four Google Play APIs from a single binary, with no Ruby, JVM or browser. A GitHub Action stops a bad build before upload, and 19 agent skills teach Claude Code to drive it.
The challenge
Shipping an Android update means working through the Play Console screen by screen: upload the build, write the notes, configure the rollout, check the crash numbers, read the reviews. Every single release. The usual automation tools cover only a slice of the Play API and pull in heavy runtimes most teams would rather not install.
What I built
A TypeScript CLI that does the Play Console's job from the terminal and from CI, checks a build against Google Play policy before upload, and ships with a GitHub Action and agent skills around it.
One CLI for the whole console
Seven TypeScript packages cover releases and staged rollouts, store listings, vitals, reviews, subscriptions, reports and Managed Google Play. Every command can print JSON and returns a documented exit code, so a pipeline can act on the result instead of parsing text.
Bun compiles the CLI into a standalone binary for macOS, Linux and Windows; it also installs from npm and Homebrew. The core packages work on their own as an SDK, and a plugin SDK lets a team add its own commands.
Rejections caught before upload
gpc preflight runs nine offline scanners against the bundle: the manifest, restricted permissions, 64-bit native libraries, listing limits, leaked keys, non-Play billing SDKs, tracking SDKs, Families policy and download size. Nothing is sent to Google, and a reason for rejection shows up on your machine instead of in review.
The rules follow Google's dates. Version 1.1 reads the Play Billing Library version from the manifest and fails a build still on version 7 or older, which Google stopped accepting after November 1, 2026.
A stable 1.0 that CI can pin
After two release candidates, 1.0 shipped in October 2026 with a written promise: commands, flags, exit codes and JSON output follow semantic versioning, so a pinned pipeline keeps working. Before it shipped, every vitals gate was checked live against a production app, through both the npm package and the binary.
gpc watch follows crash and ANR rates during a staged rollout and can halt it when a threshold is crossed, so a bad release stops spreading without someone watching the console.
Around the CLI
gpc-action publishes to Google Play from GitHub Actions and runs preflight first by default, so a bad build fails the job before upload. Teams on r0adkll/upload-google-play switch by changing one line.
gpc-skills packages 19 agent skills, from first setup to Fastlane migration and vitals monitoring, so Claude Code uses GPC the way the docs intend. The packages carry over 2,900 tests, run on every change.
Built with
- TypeScript
- Node.js
- Turborepo
- tsup
- Vitest
- Bun
- VitePress
- GitHub Actions
- Google Play API
- gpc status$ gpc statusApp: com.example.app (fetched just now)RELEASESproduction v142 completed -beta v143 inProgress 10%internal v144 draft -VITALS (last 7 days)crashes 0.80% ↓ ✓ anr 0.20% ↓ ✓slow starts 2.10% ✓ slow render 4.30% ⚠REVIEWS (last 30 days)★ 4.6 142 new 89% positive ↑ from 4.4
App health at a glance: releases, vitals, and reviews in one command - gpc preflight$ gpc preflight app-release.aabScanning app-release.aab (9 scanners)✓ Target SDK 35 (meets requirement)✓ Permissions All declared correctly✓ Exported components All flagged⚠ API keys 1 hardcoded key in BuildConfig✓ Billing SDK Play Billing v7✓ Privacy/tracking No issues✓ COPPA flags Not targeted at children✓ Download size 24.3 MB (under 200 MB)✓ Store listing Metadata complete8 passed 1 warning 0 errors
9 offline policy scanners catch rejections before Google does - gpc releases$ gpc releases upload app.aab --track beta --notes "Bug fixes"Creating edit... doneUploading app.aab... done (24.3 MB)Assigning to beta track... doneSetting release notes... doneCommitting edit... done✓ v143 uploaded to beta track$ gpc releases promote --from beta --to production --rollout 10✓ v143 promoted to production at 10% rollout
Upload, promote, and roll out from the terminal - gpc doctor$ gpc doctor✓ Node.js v20.20.0✓ GPC version v0.9.51✓ Configuration loaded from .gpcrc.json✓ Default app com.example.myapp✓ Authentication service account✓ API connectivity verifiedAll checks passed!
Validate your entire setup before shipping