Set up a persistent AI agent gateway on macOS with Redis event bridge, heartbeat monitoring, and multi-session routing. Interactive Q&A to match your intent — from minimal (Redis + extension) to full (embedded daemon + Telegram + watchdog). Use when: 'set up a gateway', 'I want my agent always on', 'event bridge', 'heartbeat monitoring', 'agent notifications', or any request to make an AI agent persistent and reachable.
91
88%
Does it follow best practices?
Impact
96%
2.08xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Tier 1 Redis extension bridge setup
Extension directory path
0%
100%
ioredis version pinned
0%
100%
npm install command
100%
100%
Two separate Redis clients
100%
100%
Subscribe-only client
100%
100%
Events list key pattern
0%
100%
Notify channel pattern
0%
100%
LPUSH for event enqueue
0%
100%
PUBLISH for notification
100%
100%
Event format fields
20%
100%
Tier 2 always-on persistence and watchdog monitoring
GATEWAY_ROLE=central launch
0%
100%
HEARTBEAT.md checklist
100%
100%
Watchdog threshold 30 minutes
0%
100%
Watchdog check interval 5 minutes
0%
100%
Watchdog resets on heartbeat
50%
100%
tmux wrapping in launchd
100%
100%
launchd KeepAlive
100%
100%
Inngest serveHost docker
70%
100%
Inngest re-sync command
100%
0%
Tier 3 multi-session central/satellite routing
GATEWAY_ROLE env var
0%
100%
Central SESSION_ID is 'gateway'
0%
100%
Satellite SESSION_ID is pid-based
100%
100%
Sessions Redis set key
0%
100%
sadd on startup
100%
100%
srem on shutdown
100%
100%
Fan-out: central always targeted
0%
100%
Fan-out: origin session targeted
100%
100%
GATEWAY_ROLE=central in usage docs
0%
100%
825972c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.