Inspiration
A zombie process (<defunct>) has already exited, but its parent never collected it with wait(). Signalling the zombie does nothing; the only fix is the parent. Away from a terminal that means SSH, ps, finding the parent, deciding, and killing it. Nobody does that from a train. We wanted it to take one second, from a phone.
What it does
- An agent on each Linux server reads
/procevery 5 seconds and reports the parents that hold zombies. It only connects out; the server opens no port. - When a new parent appears, your phone gets a push notification within 30 seconds, even with the app closed.
- The battle screen shows the server, PID and command line. Hold the button for 1 second: the agent re-checks the process and sends
SIGKILLto that parent. The outcome is always shown.
Killy is a small, silent apprentice reaper. It never speaks; it only reacts (……!). Everything that needs explaining is plain system text beside it.
What Killy guarantees:
- One action only:
SIGKILL. No other signals, no shell. - The same process, or nothing: right before signalling, the agent checks through a pidfd that the process still has the PID and start time you were shown and still holds zombies. A reused PID is never killed.
- Protected processes: never PID 1, the agent itself or its ancestors.
- Only your phone: only a paired phone can see a server or kill on it. Pairing codes work once and expire in 10 minutes.
How we built it — the Frankenstein
Low-level Linux process control, a mobile game and push notifications, stitched into one app:
- Agent (Go):
/procscanning,pidfd_open/pidfd_send_signalthrough raw syscalls, so a kill can never fall back to signalling by PID. - Killy server (Go, PostgreSQL): relays between agents and phones over HTTPS and Server-Sent Events, sends pushes through Expo, and waits for each kill's result.
- App (Expo / React Native): the battle screen, notifications, QR pairing, English and Japanese.
- Infrastructure: a home Kubernetes cluster with Argo CD, reached through Cloudflare Tunnel.
How we used Kiro
- Steering (
.kiro/steering/):product.mdanddesign.mdpoint Kiro at the PRD, architecture and design docs in every session.killy-character.mdmakes the "Killy never speaks" rule apply everywhere: app copy, notifications, store text, the README and this video. - Specs (
.kiro/specs/): six specs, one per vertical slice: relay and pairing, agent process control, the mobile battle slice, notifications and settings, server management, and the demo environment. Each slice was implemented and reviewed against its spec. - Hooks (
.kiro/hooks/merge-gate.json): aPreToolUsehook that blocksgh pr mergeunless every check on the PR's head succeeded and the merge pins that head commit. The hook's logic has its own tests (tools/mergegate/).
Challenges we ran into
- PID reuse. Between "you saw PID 192" and "kill PID 192", the PID can belong to someone else. We kill only through a pidfd opened after checking the start time, and we refuse rather than fall back when pidfd is unavailable.
- Keeping streams alive through Cloudflare and the ingress: heartbeats every 20 seconds, and reconnects with backoff and jitter so a server restart does not cause a reconnect storm.
- Push delivery that neither loops nor goes silent: bounded retries, and dropping tokens that Expo reports as gone.
- A character who never speaks. Every message had to become system text beside Killy, never Killy's words.
Accomplishments that we're proud of
Killing a zombie's parent from a phone in about one second, on a real Linux machine, with a guarantee that the PID you saw is the process that dies.
What we learned
Steering and specs kept a long, multi-part build consistent: the same rules about safety, wording and character held from the Go agent down to the push notification text.
What's next for Killy
Release on the App Store and Google Play beyond testing, and a production Killy server for your own fleet.
Try it
No server needed: in the app, open Settings → Add server → Try the demo server. A shared demo machine keeps creating zombie parents. Only those can be killed, and a parent someone else kills disappears for everyone.
Built With
- argo-cd
- cloudflare-tunnel
- expo-notifications
- expo.io
- go
- kiro
- kubernetes
- postgresql
- react-native
- server-sent-events
- typescript