integrate 1-minute follow-up watcher into ZeroClaw stack workflow
expose /realtime_1min.log on follow dashboard
update progress tasks for RTC/Zacus dual-stack readiness
Changes
tools/ai/zeroclaw_stack_up.sh: start follow server via orchestrator path and dashboard refactor for richer realtime visibility.
specs/04_tasks.md: add completed tasks for provider check, scan, and target mapping.
specs/zeroclaw_dual_hw_todo.md: add port mapping task completion and realtime/loop notes.
stack_down/watch_1min: stack lifecycle and realtime file already present in branch baseline and kept for loop coordination.
Notes
next step after merge: run dual-loop evidence checks and webhook traces for repo-hint=rtc and repo-hint=zacus.
## watcher 1min + realtime log
### Scope
- integrate 1-minute follow-up watcher into ZeroClaw stack workflow
- expose /realtime_1min.log on follow dashboard
- update progress tasks for RTC/Zacus dual-stack readiness
### Changes
- tools/ai/zeroclaw_stack_up.sh: start follow server via orchestrator path and dashboard refactor for richer realtime visibility.
- specs/04_tasks.md: add completed tasks for provider check, scan, and target mapping.
- specs/zeroclaw_dual_hw_todo.md: add port mapping task completion and realtime/loop notes.
- stack_down/watch_1min: stack lifecycle and realtime file already present in branch baseline and kept for loop coordination.
### Notes
- next step after merge: run dual-loop evidence checks and webhook traces for repo-hint=rtc and repo-hint=zacus.
chatgpt-codex-connector[bot]
(Migrated from github.com)
reviewed 2026-02-21 18:12:54 +00:00
chatgpt-codex-connector[bot]
(Migrated from github.com)
left a comment
Copy Link
Copy Source
💡 Codex Review
Here are some automated review suggestions for this pull request.
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
### 💡 Codex Review
Here are some automated review suggestions for this pull request.
**Reviewed commit:** `382b752d7c`
<details> <summary>ℹ️ About Codex in GitHub</summary>
<br/>
[Your team has set up Codex to review pull requests in this repo](http://chatgpt.com/codex/settings/general). Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
</details>
The script exits when brew is missing before it checks uname, so Linux users hit a hard failure even though the script already has a non-Darwin path (nohup ollama serve) and may already have ollama installed. This makes ollama_local_setup.sh unusable outside macOS unless Homebrew is installed unnecessarily.
Useful? React with 👍 / 👎.
**<sub><sub></sub></sub> Skip Homebrew requirement on non-macOS hosts**
The script exits when `brew` is missing before it checks `uname`, so Linux users hit a hard failure even though the script already has a non-Darwin path (`nohup ollama serve`) and may already have `ollama` installed. This makes `ollama_local_setup.sh` unusable outside macOS unless Homebrew is installed unnecessarily.
Useful? React with 👍 / 👎.
Ship orchestrator API server or disable API dashboard mode
This branch adds a dashboard that polls /api/status, /api/run, and question endpoints, but startup only serves those routes when tools/ai/zeroclaw_orchestrator_server.py exists. In this commit tree the file is not present (the new tools/ai entries do not include it), so this condition is always false and the script always falls back to python -m http.server, which returns 404 for every new orchestration control/API panel.
Useful? React with 👍 / 👎.
**<sub><sub></sub></sub> Ship orchestrator API server or disable API dashboard mode**
This branch adds a dashboard that polls `/api/status`, `/api/run`, and question endpoints, but startup only serves those routes when `tools/ai/zeroclaw_orchestrator_server.py` exists. In this commit tree the file is not present (the new `tools/ai` entries do not include it), so this condition is always false and the script always falls back to `python -m http.server`, which returns 404 for every new orchestration control/API panel.
Useful? React with 👍 / 👎.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
watcher 1min + realtime log
Scope
Changes
Notes
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:
382b752d7cℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
@@ -0,0 +52,4 @@if ! command -v brew >/dev/null 2>&1; thenecho "[fail] Homebrew is required on macOS for automated Ollama setup." >&2exit 1fiThe script exits when
brewis missing before it checksuname, so Linux users hit a hard failure even though the script already has a non-Darwin path (nohup ollama serve) and may already haveollamainstalled. This makesollama_local_setup.shunusable outside macOS unless Homebrew is installed unnecessarily.Useful? React with 👍 / 👎.
@@ -539,0 +926,4 @@display: flex;}.modal-card {width: min(760px, 100%);This branch adds a dashboard that polls
/api/status,/api/run, and question endpoints, but startup only serves those routes whentools/ai/zeroclaw_orchestrator_server.pyexists. In this commit tree the file is not present (the newtools/aientries do not include it), so this condition is always false and the script always falls back topython -m http.server, which returns 404 for every new orchestration control/API panel.Useful? React with 👍 / 👎.
Codex review (manual): PASS. Scope is script-only (tools/ai + spec docs), no firmware/runtime code changes. No secrets/absolute paths detected, checks green, merged cleanly. Side-effect: one added orchestrator server fallback improves UI/API tooling and remains optional. Safe for merge continuation.