In production
Console Autopilots
Browser robots for the jobs store APIs leave to humans: Partner Center, App Store Connect, Play Console.
- Playwright
- Chromium
- Your own accounts
What it does
Every store console has work that its API cannot do. Console Autopilots are the browser robots that did those clicks for our catalogue: they keep a signed-in browser profile alive, follow each flow step by step, take a screenshot when something unexpected appears and report back in plain words.
- Microsoft Partner Center. Create add-ons and subscriptions with prices, answer the age-rating questionnaire, finish submissions the API leaves pending and save certification reports.
- App Store Connect. The web-only steps around pricing, availability and review information.
- Google Play Console. Release promotion between tracks and the console forms that block a launch.
- Built to survive. Session keep-alive, account-picker handling, retries with screenshots, and a queue so only one robot drives a console at a time.
What is inside
Browser agent
The Playwright runner, profile keeper and job queue.
Console flows
Flows for Partner Center, App Store Connect and Play Console.
Diagnostics
Screenshots and plain-language reports for every failed step.
Requirements
- A machine that can keep a browser running (Linux with a virtual display, or macOS).
- Python 3.10 or newer and Playwright with Chromium.
- Your own console accounts; you sign in once, by hand.
Risks
- Automating a web console may break that platform's terms of use, and flows can stop working when the site changes. Use the robots on your own accounts only, at your own risk.
- The robots never type passwords or solve captchas: you sign in yourself, and they reuse that session.
Updated: