PM Gremlins
Give them a mandate. They explore the app, propose bounded epics, and test each implementation against its acceptance criteria.
- Real browser exploration
- Product ideas grounded in your app
- QA evidence and a promotion batch

OPEN SOURCE. SLIGHTLY FERAL.
Your app has a backlog. And blind spots. Give PM Gremlins a goal worth pursuing; they explore, investigate, and propose improvements. Approve the direction. Your crew codes, tests, and brings you a batch of improvements to review.
Self-hosted · Real browsers · Your final say
WHEN TO CALL IN THE GREMLINS
The onboarding you keep putting off. The feature nobody has time to explore. The permissions that need a closer look. Start with one part of your existing product that deserves more attention.
Connect your repository. A Setup Gremlin reads the code and suggests a crew with distinct responsibilities. Review their briefs, connect Linear, and test access to the app before starting patrols.
Start with one neglected area.Your PM investigates and proposes an epic: an outcome, boundaries, and a definition of success. Approve that scope once. It breaks the work into testable tickets for Coding Gremlins.
Product ideas with something behind them.Coders implement; PMs test each change. Failed checks return with feedback. Each PM collects its passing work into a promotion PR, at 10 tickets by default. You review the batch into staging.
Your runners. Your release decision.Useful before launch. More useful as the app grows. Bring a working prototype or an established product. You don’t need a big team; you need a real codebase, a direction, and time to review the results.
Try one improvement$ npm install -g
git+https://github.com/AgentBurgundy/shipgremlins.git
$
gremlins setup
Then connect your app in the private dashboard and give your first gremlin a useful job. See the next steps →
A LITTLE CHAOS.
A LOT OF SCREENSHOTS.
MEET YOUR TWO CREWS
Different jobs. Shared evidence. PM Gremlins investigate and QA. Coding Gremlins implement the milestones inside your approved epic.
Give them a mandate. They explore the app, propose bounded epics, and test each implementation against its acceptance criteria.

They pick up eligible tickets from approved epics on your runners. The controller checks and merges internal PRs into the test branch.

Launch either crew from your dashboard. Follow visible tool calls, progress, checks, and screenshots in Activity.
01 / THE PM MANDATES
One PM owns one area. Give each a mandate, a schedule, and boundaries. Let curiosity do the rest.
“Should that user really be able to do that?”
“What are they trying to do next?”
“It works. But does it make sense?”
Your mandate. Your codebase. Give each PM an outcome, run discovery, and let it build a feature map and ranked ideas for what comes next. Shared project decisions keep the crew working toward the same goal. Meet the PM workspace →
02 / SHOW YOUR WORK
Every useful finding needs a reproduction. Every verified fix needs evidence. Follow the trail from a browser observation to a production merge.
Illustrative workflow. No live agents are running on this page.
Reproduce with two isolated test accounts. Record the request and the actual browser state.
Review the epic’s scope and evidence in your project inbox. Your PM turns the approved direction into testable tickets.
The PM checks the deployed revision and acceptance criteria. Passing work joins its batch; a failure returns to coding with evidence.
03 / GUARDRAILS INCLUDED
Your crew can be relentless without having the keys to everything.
Control the epic’s scope, test environment, and amount of work in flight.
Bounded retries and a dedicated recovery lane keep ordinary work paused while a broken integration is repaired.
Require current deployment evidence before a promotion opens. Stale checks and a confident comment don't count.
A CHANNEL FOR THE CHAOS
Bring PM findings and Coding Gremlin updates into Slack. Pick a workspace and channel from your dashboard, then keep up with the work where your team already talks.
Set up SlackOne channel for both crews. Human approval and production decisions stay with you.
Sample messages show the intended handoff. This page is not connected to a live Slack workspace.
04 / BRING YOUR STACK
Keep your code, tickets, and infrastructure.
Give your PMs the
evidence behind the screen, too.
THEY'RE SMALL. THEIR STANDARDS AREN'T.
Bring the app you care about. Pick the flow that needs attention. Approve a useful direction. Review the batch when it is ready.
Adopt your first gremlin# Bring the crew home
npm install -g
git+https://github.com/AgentBurgundy/shipgremlins.git
# Open your private setup dashboard
gremlins setup
# On your server or homelab · port 4311
gremlins setup --lan --port 4311Early alpha, built in the open. Bring Node.js, Git, Docker, and your provider credentials. Workers run on your machine; you approve the work and control production merges.
A FEW FAIR QUESTIONS
When you already have an app and more improvements than you have time to investigate and implement. Start with one outcome: a clearer first-run experience, a missing workflow, or better account isolation. The crew investigates and implements approved work; you set direction and review the result. Choose your starting point →
There is an experimental idea-to-app path. It creates a private-by-default repository, proposes a small crew, and lets you review a foundation coding assignment. Expect to iterate on the result: a scaffold is not proof of a polished, integrated product. Improving an existing app is the main workflow. Read the experimental guide →
No. A real codebase and a clear goal are enough to start repository discovery. Browser investigations need a runnable app in an isolated test environment; a local prototype can use supported Docker setup. Add Linear when you’re ready for proposals and approved coding work. Start with one assignment →
Yes. Delete projects and PMs from the dashboard, with a clear preview and a local recovery copy. Restore them from Settings with automation paused. Your repositories, Linear tickets, and past runs stay intact. Removal and recovery →
PM Gremlins investigate a mandate, propose epics, and QA implementations. Coding Gremlins implement eligible tickets within an approved epic. Internal PRs go through automatic checks and integration; each PM batches its verified tickets into a promotion PR. You approve epics and review batches into staging. Existing projects keep their configured delivery policy.
No. Add your GitHub or GitLab repository and let the Setup Gremlin recommend a test home. Use an existing staging environment or a disposable Docker app with optional PostgreSQL and Redis. Review any proposed setup files as a draft PR or MR, then test access in a real browser. Libraries and CLIs can stay in repository-only mode. See project onboarding →
Connect a workspace and channel in your self-hosted dashboard. When one-click installation is available, Add to Slack guides you through it. An advanced incoming-webhook option is also supported. Slack carries updates; it does not approve epics or merge releases.
No. Save a Linear connection and select it for your app; the PM prepares missing team, project, and label mappings when it needs them. Existing mappings stay in place. Inspection, adoption, and the first read-only Discovery need no Linear mapping. New PMs start paused. If workspace permissions or limits block setup, your PM stays saved for retry.
New managed projects ask you to approve a bounded epic and review each PM’s promotion batch, at 10 verified tickets by default. The crew implements and tests the child tickets; the controller checks and merges internal PRs into pm-staging. Failed QA returns with feedback and bounded retries. Existing projects keep their selected approval policy. Follow the delivery loop →
It opens the protected preview. Private app features still need a dedicated test account. Setup can suggest the password login controls from source, then checks the actual login with your saved credentials. You can choose public pages only, with private journeys clearly left untested. Set up app access →
No. Agents work on approved scope in a test environment. Promotion has verification gates, and the owner retains staging and production merge decisions. Reconciliation marks work Done only after production inclusion is proven.
Yes. Run gremlins setup --lan --port 4311 on your
server, then open the private session link from a browser on your
trusted network. Create local Docker workers in the dashboard.
Connections and configuration live on that server; jobs receive
the credentials they need. No fork, automation
repository, or GitHub Actions/GitLab CI runner registration is needed.
Yes. Enroll a remote Docker worker from the dashboard, choose its projects, and run the one-time connection command on that machine. Workers connect outbound and use expiring job leases. A cloud VM, Linux server, or Mac/Windows Docker Desktop host can provide capacity. Native iOS jobs and automatic cloud provisioning are still planned.
The current workers use Claude Code. Additional runtimes are planned. You control the credentials and model configuration in your own environment.
The browser can explore many kinds of apps, but reliable testing needs configured accounts, isolated data, and acceptance criteria. GitHub and GitLab source repositories are supported. Use Vercel, Railway, Cloud Run, or a reachable preview URL for browser work. Provider connectors discover existing deployments; they do not deploy or provision your app.
Yes. The fixture CLI generates CSVs from JSON and reproducible PNG test images, ready to upload through Playwright MCP. Semantic AI image generation and automatic test-data cleanup are on the roadmap.