I set a $5 a month spending limit on GitHub Actions. My AI agents hit it.
I raised it to $10. I think they are hitting that one too.
The sane fix was a bigger CI budget. I built a Mac app with one big deploy button per project instead.
TL;DR: Ploink is a free, open source Mac app. Press F5 in any app, hold a project's button, and your own deploy command runs on your own machine. Coding agents can ask to press it through MCP, and you choose per project whether they wait for you.
How side projects got me a CI bill
I run about 15 side projects. Most of them are built with AI agents.
It started on Vercel. I was on the $20 plan and paying another $10 to $20 in overages, recently even more. Not all of that came from deployments, but I wanted the bill down.
So I moved deploys to GitHub Actions. Each push triggered a run on a self-hosted runner on my home lab server. The runner built the app and uploaded it to Vercel or Cloudflare, wherever that app was hosted.
The cost moved with me. Then I hit the limit in GitHub Actions minutes as well, so they are charging me every month.
How, with a self-hosted runner? The runner did the heavy builds. The small jobs still ran on GitHub's machines:
- typechecks and other quick checks
- a job that decides where a push deploys, Vercel or my machine. I have a switch for that.
- an IndexNow ping for some sites, so search engines hear about new pages
GitHub rounds every job up to a full minute. AI agents build a lot and push a lot of code. Tiny jobs, times every push, times 15 projects.
Deploying by hand cost nothing, and I lost track
Next I deployed by hand from my own machine. The bill went away.
So did my memory of what was deployed, and how.
Some projects the agent deployed on its own. For others it stopped and asked me to run the command, which I put down to the agents' security settings.
I wanted an app I could summon with one key and click to deploy a project.
So I built it for myself.
What Ploink does
Every project on your Mac gets one big button.
- Hold it for 0.65 seconds. An LED ring charges, then your own deploy command runs in your login shell, the same as in your terminal.
- Press F5 in any app. A launch bar slides in with every project's button on it.
- Drop a project folder on the window. Ploink reads
package.json, Wrangler, Fly, Vercel, Netlify and Makefile setups to find the deploy command. - Open the flight log. It lists who started each deploy, what shipped and what failed.
- Confetti fires only when a deploy ships. Remember this one. It comes back.
CI minutes used: 0.
Let your agent ask to deploy
Ploink runs an MCP server on 127.0.0.1:47321 while the app is open. Setup takes three steps.
- In Ploink, open Settings > Agents (MCP) > Create token. Each agent gets its own token.
- Add Ploink to your agent with one of the configs below.
- Decide who fires the deploy. Turn on "Ask me before agents deploy this" for a project and its button glows amber until you hold it or click Deny. Leave it off and the agent's request runs at once.
Claude Code:
claude mcp add --transport http --scope user ploink http://127.0.0.1:47321/mcp --header "Authorization: Bearer plk_…" Cursor, Windsurf and other clients that take JSON config:
{ "mcpServers": { "ploink": { "url": "http://127.0.0.1:47321/mcp", "headers": { "Authorization": "Bearer plk_…" } } } } Agents can only press buttons you set up. There is no tool that runs an arbitrary command. A request you ignore expires after 10 minutes.
I run every project in manual mode, and the reason is the button. It really makes me happy when I have to deploy something and press that button.
Where the time went
Getting the UI feel just right took most of the build time. I mean the press, the animation and the small interactions on each deploy.
Second place goes to a Mac apps subreddit that kept rejecting my post. AutoModerator removed the first version for missing four required labels.
Then my deploy button lied to me
One of my projects, Automateo, has two commands on its button, "deploy" and "dry run".
Ploink remembers which command you picked for each project. Mine was still on "dry run".
I held the button. It ran wrangler deploy --dry-run, which printed this and exited with code 0:
--dry-run: exiting now. Ploink saw exit code 0 and showed SHIPPED. With confetti.
Nothing was deployed, and I had no idea.
Exit code 0 means the command did not fail. It does not mean anything shipped. My deploy tool treated those as the same thing.
Ploink 0.3.2 fixes it.
- It spots a dry run by its label, by flags like
--dry-run, and by output like Wrangler's line above. - A passing dry run shows DRY RUN OK in amber, says nothing was deployed, and gets no confetti.
- It names the real deploy command, so you know what to switch to.
- It skips the site check that runs after a deploy.
- The F5 launch bar now shows which command each button will run.
Who this is not for
This is anti-cloud lol.
I see the appeal of pushing code and having the app deploy itself. But I don't want to be paying $20 to $30 a month for that. For small micro-SaaS side projects, a cloud pipeline is overkill.
The downside is that it won't really fit the workflow of people who run agents in the cloud. But for me, at this point in my life, this is perfect.
Three more catches.
- Mac only, Apple Silicon only, macOS 12 or newer.
- It is an Electron app. The download is 122 MB.
- The beta is not signed or notarized. I have not bought the $99 a year Apple developer account yet.
Try it
- Download
Ploink.dmgfrom GitHub Releases and drag Ploink to Applications. - Open it. macOS blocks unsigned apps on the first launch. On macOS 15 or later, double-click the app, click Done, then click Open Anyway in System Settings > Privacy & Security. On macOS 14 or earlier, right-click the app and choose Open. You do this once.
- Drop a project folder on the window.
- Hold the button for 0.65 seconds.
- Press F5 in any app for the launch bar. On most Mac keyboards that is fn + F5.
Not comfortable opening an unsigned app? Build it from source. The setup guide has both routes.
The free part and the $19 part
The core is free and MIT licensed, with unlimited projects. Everything in this post is in it.
Ploink Pro is a founding pre-order. $19 once, $29 after launch, no subscription.
- The goal is 50 founders by 19 December 2026. If fewer sign up, everyone gets an automatic refund and the core stays free.
- If no signed build ships by 31 January 2027, everyone gets an automatic refund.
- Founders get the unsigned beta now, Pro for all of 1.x, and a vote on which Pro features ship first.
So far Pro is extra button packs that change how the buttons look and sound. Bigger features like agent guardrails are not built yet. That is what the refund terms are for.
Start with the free core at github.com/petarjs/ploink. If you end up holding that button every day, the pre-order is at ploink.dev.
Parts of this story first ran as an interview on Automateo. Yes, the same Automateo from the dry run bug. It is one of my 15.

