Stop HTTP Registry Server
SkillCloud & infraStop the background HTTP registry server started by /start-http-registry — TaskStop / KillShell by the recorded task ID, plus a /proc cmdline-scan fallback for minimal-tool sandboxes with no ps/lsof/pkill/fuser. Referenced by every warp deploy/update skill that starts the registry.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Stop HTTP Registry Server skill
What this skill tells your AI
The instructions your AI receives, as published by hyperlane-xyz/hyperlane-monorepo in .claude/skills/stop-http-registry/SKILL.md and read by ahel’s review.
Stop the background HTTP registry started via /start-http-registry. Always stop it at the end of the skill — even on failure paths — so no background process is left running.
-
Primary:
TaskStop(orKillShell) with the task/shell ID recorded when the registry was started. -
Fallback (minimal-tool sandboxes): if
TaskStopdoesn't clean up the underlying process andps/lsof/pkill/fuseraren't available, scan/procfor the registry's cmdline and kill it:# Find PIDs matching the registry process — exclude the scanning shell itself SELF_PID=$$ for pid in $(ls /proc | grep -E '^[0-9]+$'); do [ "$pid" = "$SELF_PID" ] && continue if grep -aql 'http-registry-server\|start:http-registry' /proc/$pid/cmdline 2>/dev/null; then echo "killing http-registry pid=$pid" kill "$pid" 2>/dev/null || true fi doneAlways run the fallback after
TaskStopregardless — it is idempotent if the process is already gone.
Consumers
/warp-deploy-init-route, /warp-deploy-update-owners, /warp-update, /warp-update-extend, /warp-update-resolve-artifacts — every skill that starts the HTTP registry.
Signals
- GitHub stars
- 75
- Forks
- 601
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
stop-http-registry- Source
- github.com/hyperlane-xyz/hyperlane-monorepo