deemwar
Working capabilities you can run, pulled from real production problems in WhatsApp / Telegram automation, browser automation, and the workflow plumbing that connects real systems to each other. Each one leads with the job it does for you, ships as self-contained code you run locally in a sitting, and drops into your own stack. Free, MIT. Engineering-first — no slideware.
A session-based channel (WhatsApp Web, a paired device, an OAuth API) can go dark while the process stays up: /health checks liveness, not whether the session can still deliver. Runnable — node check.js --demo reproduces the false green in ten lines, or point it at your own health endpoint. No network by default, zero deps.
Drop one wrapper around your LLM client and get a hard cap that actually holds when workers run concurrently, a per-agent spend breakdown (who burned the most, in dollars), and an early pause when a loop goes runaway. Runnable — node report.js prints the spend report. No network, zero deps.
A GitHub Actions run that fails at startup, in 0 seconds, with zero jobs run, on every single push — GitHub's own message blames the workflow file, but this exact shape is usually exhausted Actions billing. Runnable — node check.js owner/repo tells the two apart. No network beyond the `gh` CLI, zero deps.
A budget cap that passes every test can let a first-seen customer through completely unmetered — HTTP 200, no error, cap configured the whole time. The cause is that null means both "no cap" and "cap didn't reach me", and nothing at the decision point can tell them apart. Runnable — node check.js --demo reproduces it in nine lines, or point it at your own gateway. Zero deps.
More examples land here as we hit the problems worth writing up. Each is judged on one thing: does the code run and hold up.
We build and run the automation these examples come from — WhatsApp and Telegram integrations, browser automation, and the workflow plumbing that connects real systems to each other — as fixed-scope engagements. Mail us what you're building or what broke; you'll get an engineer's answer, not a deck.