[codex] autonomous zeroclaw stack with prometheus fallback and webhook controls #5

2026-02-21T01:19:31Z

electron-rare commented

2026-02-21 01:19:31 +00:00

(Migrated from github.com)

Summary

add local env bootstrap (~/.zeroclaw/env) loading in stack/chat/webhook scripts
implement Prometheus dual fallback in stack_up (binary -> docker -> disabled) with readiness checks
add Docker daemon auto-start attempt on macOS for docker mode
harden gateway pairing flow with token probe/refresh attempts
switch webhook sender to auto-send by default, add --dry-run, and add local budget guards
update orchestration spec with new auth/prometheus/webhook contracts

Validation

bash -n on updated scripts
shellcheck on updated scripts
smoke run:
- ZEROCLAW_PROM_MODE=auto tools/ai/zeroclaw_stack_up.sh
- curl http://127.0.0.1:3000/health
- curl http://127.0.0.1:8788/
- curl http://127.0.0.1:9090/-/ready
- tools/ai/zeroclaw_webhook_send.sh --dry-run ...
- tools/ai/zeroclaw_dual_chat.sh rtc --provider-check

Notes

Docker Desktop app was not present on this host, so Prometheus binary fallback was activated via Homebrew (prometheus 3.9.1).
~/.zeroclaw/env was created with OPENROUTER_API_KEY= placeholder and mode 600.
Gateway health reports paired:true, but local token auto-recovery can still require explicit re-pair when no active pairing code is available in logs.

## Summary - add local env bootstrap (`~/.zeroclaw/env`) loading in stack/chat/webhook scripts - implement Prometheus dual fallback in `stack_up` (`binary -> docker -> disabled`) with readiness checks - add Docker daemon auto-start attempt on macOS for docker mode - harden gateway pairing flow with token probe/refresh attempts - switch webhook sender to auto-send by default, add `--dry-run`, and add local budget guards - update orchestration spec with new auth/prometheus/webhook contracts ## Validation - `bash -n` on updated scripts - `shellcheck` on updated scripts - smoke run: - `ZEROCLAW_PROM_MODE=auto tools/ai/zeroclaw_stack_up.sh` - `curl http://127.0.0.1:3000/health` - `curl http://127.0.0.1:8788/` - `curl http://127.0.0.1:9090/-/ready` - `tools/ai/zeroclaw_webhook_send.sh --dry-run ...` - `tools/ai/zeroclaw_dual_chat.sh rtc --provider-check` ## Notes - Docker Desktop app was not present on this host, so Prometheus binary fallback was activated via Homebrew (`prometheus 3.9.1`). - `~/.zeroclaw/env` was created with `OPENROUTER_API_KEY=` placeholder and mode `600`. - Gateway health reports `paired:true`, but local token auto-recovery can still require explicit re-pair when no active pairing code is available in logs.

chatgpt-codex-connector[bot] commented

2026-02-21 01:19:36 +00:00

(Migrated from github.com)

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/settings/usage). To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your [settings](https://chatgpt.com/codex/settings/code-review).

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: electron-rare/Kill_LIFE#5