Event-driven autonomous agents triggered by GitHub repository activity — no polling, no scheduled timers. Built on Zo Computer.
Zo Computer is a personal AI server that runs in the cloud with full tool access — files, calendar, email, browser, GitHub, and more. It ships with an agentic workflow engine that can be triggered on a schedule (RRULE/cron) or, as this project demonstrates, purely by external events via webhooks.
Tweet: https://x.com/etok_me/status/2043233125262929941?s=46
Key routes on that space:
| Path | Purpose |
|---|---|
/api/github-webhook |
Receives GitHub webhook events and triggers the autonomous agent |
/docs |
In-space documentation for the full setup |
Repo: https://github.com/EthanThatOneKid/zo-gh
Setup (quick start, route install, secrets, ping), supported events, security,
multi-repo and org-wide scenarios, troubleshooting, and a self-contained source
appendix live in SKILL.md. Start there for anything beyond
this overview. For any Space other than the reference deployment, set
ZO_WEBHOOK_ENDPOINT to your full webhook URL before running the register
or test scripts (see SKILL.md).
zo-gh/
├── scripts/
│ ├── register-webhook.sh # Registers GitHub webhook (all events)
│ └── send-test-webhook.ts # Synthetic payloads (ping, push, …) to hit the route locally
├── webhook-agent/ # Zo Space bundle: api-github-webhook.ts → POST /api/github-webhook
├── SKILL.md # Agent skill + Appendix (verbatim sources; no clone required)
├── DISPLAY.json # Zo / registry UI metadata (icon, tags, integrations)
└── README.md # This file — short intro and links
Zo is a personal AI server that lives in the cloud. It runs your files, your automations, and your agents — with full access to your calendar, email, browser, GitHub, and more. This project is one example of hooking Zo's agentic workflow into the outside world via webhooks, enabling event-driven automation without any scheduled polling.
Want your own Zo? Use my affiliate link to get started.