A public agent greets site visitors over IRC while a private one handles email and scheduling, capped at $2 a day.
A public agent greets site visitors over IRC while a private one handles email and scheduling, capped at $2 a day.
George Larson ran nullclaw, a small Zig agent, on a cheap VPS. It joined his own IRC server, which visitors reached through a web client. It answered questions using preloaded context and cloned public GitHub repos to check claims. For scheduling and contact requests it called a private agent, ironclaw, over the A2A protocol through Tailscale. Ironclaw held the email and calendar access. He wrote the A2A client tool himself.
It worked for visitors, with Haiku handling chat and Sonnet handling repo reading. The agent was imperfect, and the whole system was decommissioned after running from March to June 2026.
The agent was the easy part. The hardening, DNS, TLS and Cloudflare setup took longer, and the handoff needs strict limits on what the public agent can pass on.
Set up two agents on my small VPS: a public one that greets visitors to [my website or chat channel] and answers basic questions about [me or my project], and a private one that reads my [email account] and helps with scheduling on [calendar]. Cap total spending at [$2] a day and stop when both are running and you've shown me the config and cost limits. Pause and show me any email or calendar invite before sending it.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
Copilot and Claude review each PR for bugs, missing tests and risky changes before a human looks, so reviewers can focus on design.