083c146aac
* fix: include kanbanImmersive in immersiveOverlayActive calculation When Kanban board is open, HUD elements (camera preset buttons, edit toolbar, overlays) should be suppressed. The kanbanImmersive flag was defined but not included in the immersiveOverlayActive condition, causing HUD elements to remain visible. This fix adds kanbanImmersive to the immersiveOverlayActive calculation so HUD elements are properly hidden when the Kanban board is open. Co-authored-by: Luke The Dev <iamlukethedev@users.noreply.github.com> * Fix: Hide mini status bar when Kanban immersive overlay is open Wraps the bottom-left mini status bar (showing agent stats, vibe score, and control hints) with !immersiveOverlayActive check to match the behavior of other HUD elements like camera controls and toolbar. This ensures the status bar is properly hidden when the Kanban board or any other immersive overlay is active, maintaining a clean immersive experience. Co-authored-by: Luke The Dev <iamlukethedev@users.noreply.github.com> * chore: drop unrelated package-lock line from branch Co-authored-by: Luke The Dev <iamlukethedev@users.noreply.github.com> * universal-backend-plan * backend-neutral runtime seam * package.json update * feat: add Hermes gateway adapter as alternative to OpenClaw Adds a WebSocket adapter that lets Claw3D connect to a Hermes AI agent runtime without any changes to the frontend. The adapter implements the full Claw3D gateway protocol and bridges it to the Hermes HTTP API. Changes: - server/hermes-gateway-adapter.js: WebSocket bridge implementing the Claw3D gateway protocol against the Hermes HTTP API. Supports all core methods (agents, sessions, chat streaming, cron, config, files, approvals) and multi-agent orchestration via spawn_agent/delegate_task tools. Persists conversation history to ~/.hermes/clawd3d-history.json. - scripts/clawd3d-start.sh: All-in-one startup script that launches Hermes, the adapter, and the Next.js dev server with auto port conflict resolution. Alias as `claw3d` for convenience. - src/features/office/hooks/useCronAgents.ts: Hook that polls the gateway for cron-scheduled agents and surfaces them in the 3D office. - package.json: adds `hermes-adapter` npm script - .env.example: documents Hermes config vars - docs/hermes-gateway.md: setup guide and protocol reference Usage: npm run hermes-adapter # start adapter (connect to http://localhost:8642) npm run dev # start Claw3D, point browser at localhost:3000 # or: bash scripts/clawd3d-start.sh (starts everything automatically) Both OpenClaw and Hermes are supported simultaneously — the gateway URL in NEXT_PUBLIC_GATEWAY_URL determines which backend Claw3D connects to. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat: add read_agent_context tool for cross-agent coordination Agents can now read each other's conversation history via the read_agent_context tool, enabling the orchestrator to check what a sub-agent has done before re-delegating work. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * feat: wire Hermes office UX and role-aware runtime updates * feature update - demomode & hermes adapter * fix lint blockers * lintfix #2 * fix: stabilize retro office camera preset callbacks * Initial plan * fix: stabilize retro office overview preset hooks Agent-Logs-Url: https://github.com/gsknnft/Claw3D/sessions/9cc71555-591e-44cf-aec4-25affbdcb405 Co-authored-by: gsknnft <123185582+gsknnft@users.noreply.github.com> * feat: add truthful backend selection, Hermes adapter hardening, and demo gateway mode * fix: address bugbot review and finalize backend selection * fixed - onboarding and hermes calls * office systems roadmap * feat specs in docs * specs ready * feat: continue custom runtime seam and gateway alignment * custom lane wired * feat: add custom runtime provider path and office runtime alignment * runtime fixes * fix lukes findings * fix lukes findings #2 * stable UI & connect screen page -> overlay * better baseline for connection * stable providers & ui rendering * best launch yet * nearly no gateway on reconnect * auto reconnect last state * fix: preserve selected runtime across reconnects Keep backend selection aligned with the operator's chosen runtime instead of reviving a mismatched last-known-good adapter, and keep custom runtimes prompting for reconnect when Studio cannot auto-connect them. Made-with: Cursor --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Luke The Dev <iamlukethedev@users.noreply.github.com> Co-authored-by: Elias Pfeffer <eliaspfeffer@gmail.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: iamlukethedev <lucas.guilherme@smartwayslfl.com>
139 lines
5.4 KiB
Bash
Executable File
139 lines
5.4 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# clawd3d-start — Start all Clawd3D services, auto-resolving port conflicts.
|
|
#
|
|
# Setup (once):
|
|
# echo 'alias clawd3d="/absolute/path/to/Claw3D/scripts/clawd3d-start.sh"' >> ~/.zshrc
|
|
# source ~/.zshrc
|
|
#
|
|
# Then just run: clawd3d
|
|
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" >/dev/null 2>&1 && pwd)"
|
|
CLAWD3D_DIR="$(cd -- "$SCRIPT_DIR/.." >/dev/null 2>&1 && pwd)"
|
|
LOG_DIR="/tmp/clawd3d-logs"
|
|
mkdir -p "$LOG_DIR"
|
|
|
|
GREEN='\033[0;32m'; YELLOW='\033[1;33m'; BLUE='\033[0;34m'; NC='\033[0m'
|
|
log() { echo -e "${GREEN}[clawd3d]${NC} $*"; }
|
|
warn() { echo -e "${YELLOW}[clawd3d]${NC} $*"; }
|
|
info() { echo -e "${BLUE}[clawd3d]${NC} $*"; }
|
|
|
|
# ── Helpers ───────────────────────────────────────────────────────────────────
|
|
|
|
# Returns PIDs *listening* on a port (excludes client connections), or empty.
|
|
pids_on_port() { lsof -ti:"$1" -sTCP:LISTEN 2>/dev/null || true; }
|
|
|
|
# True if the port is free.
|
|
port_free() { [ -z "$(pids_on_port "$1")" ]; }
|
|
|
|
# Find first free port >= $1.
|
|
find_free_port() {
|
|
local p=$1
|
|
while ! port_free "$p"; do p=$((p + 1)); done
|
|
echo "$p"
|
|
}
|
|
|
|
# True if every PID on $port matches the grep pattern in its command line.
|
|
port_owned_by() {
|
|
local port=$1 pattern=$2
|
|
local pids
|
|
pids=$(pids_on_port "$port")
|
|
[ -z "$pids" ] && return 1
|
|
while IFS= read -r pid; do
|
|
local cmd
|
|
cmd=$(ps -p "$pid" -o command= 2>/dev/null || true)
|
|
if ! echo "$cmd" | grep -qE "$pattern"; then
|
|
return 1
|
|
fi
|
|
done <<< "$pids"
|
|
return 0
|
|
}
|
|
|
|
# ── 1. Hermes gateway (API, default 8642) ────────────────────────────────────
|
|
HERMES_PORT=8642
|
|
if ! port_free $HERMES_PORT; then
|
|
if port_owned_by $HERMES_PORT "hermes"; then
|
|
warn "Hermes gateway already running on :$HERMES_PORT — reusing."
|
|
else
|
|
HERMES_PORT=$(find_free_port $((HERMES_PORT + 1)))
|
|
warn "Port 8642 taken by another process → using :$HERMES_PORT for Hermes."
|
|
log "Starting Hermes gateway on :$HERMES_PORT..."
|
|
nohup env API_SERVER_PORT="$HERMES_PORT" hermes gateway run \
|
|
> "$LOG_DIR/hermes-gateway.log" 2>&1 &
|
|
sleep 2
|
|
fi
|
|
else
|
|
log "Starting Hermes gateway on :$HERMES_PORT..."
|
|
nohup hermes gateway run > "$LOG_DIR/hermes-gateway.log" 2>&1 &
|
|
sleep 2
|
|
fi
|
|
HERMES_API_URL="http://localhost:$HERMES_PORT"
|
|
|
|
# ── 2. Hermes adapter (WebSocket bridge, default 18789) ──────────────────────
|
|
ADAPTER_PORT=18789
|
|
if ! port_free $ADAPTER_PORT; then
|
|
if port_owned_by $ADAPTER_PORT "node.*hermes-gateway-adapter"; then
|
|
warn "Hermes adapter already running on :$ADAPTER_PORT — reusing."
|
|
else
|
|
ADAPTER_PORT=$(find_free_port $((ADAPTER_PORT + 1)))
|
|
warn "Port 18789 taken by another process → using :$ADAPTER_PORT for adapter."
|
|
log "Starting Hermes adapter on :$ADAPTER_PORT..."
|
|
cd "$CLAWD3D_DIR"
|
|
nohup env HERMES_ADAPTER_PORT="$ADAPTER_PORT" HERMES_API_URL="$HERMES_API_URL" \
|
|
npm run hermes-adapter > "$LOG_DIR/hermes-adapter.log" 2>&1 &
|
|
sleep 1
|
|
fi
|
|
else
|
|
log "Starting Hermes adapter on :$ADAPTER_PORT..."
|
|
cd "$CLAWD3D_DIR"
|
|
nohup env HERMES_ADAPTER_PORT="$ADAPTER_PORT" HERMES_API_URL="$HERMES_API_URL" \
|
|
npm run hermes-adapter > "$LOG_DIR/hermes-adapter.log" 2>&1 &
|
|
sleep 1
|
|
fi
|
|
GATEWAY_WS_URL="ws://localhost:$ADAPTER_PORT"
|
|
|
|
# ── 3. Next.js dev server (default 3000) ─────────────────────────────────────
|
|
APP_PORT=3000
|
|
if ! port_free $APP_PORT; then
|
|
if port_owned_by $APP_PORT "node.*next|next-server|server/index\.js"; then
|
|
warn "Clawd3D dev server already running on :$APP_PORT — reusing."
|
|
else
|
|
APP_PORT=$(find_free_port $((APP_PORT + 1)))
|
|
warn "Port 3000 taken by another process → using :$APP_PORT for Clawd3D."
|
|
log "Starting Clawd3D dev server on :$APP_PORT..."
|
|
cd "$CLAWD3D_DIR"
|
|
nohup env PORT="$APP_PORT" NEXT_PUBLIC_GATEWAY_URL="$GATEWAY_WS_URL" \
|
|
npm run dev > "$LOG_DIR/clawd3d-dev.log" 2>&1 &
|
|
fi
|
|
else
|
|
log "Starting Clawd3D dev server on :$APP_PORT..."
|
|
cd "$CLAWD3D_DIR"
|
|
nohup env PORT="$APP_PORT" NEXT_PUBLIC_GATEWAY_URL="$GATEWAY_WS_URL" \
|
|
npm run dev > "$LOG_DIR/clawd3d-dev.log" 2>&1 &
|
|
fi
|
|
|
|
# ── 4. Wait until the app responds ───────────────────────────────────────────
|
|
log "Waiting for Clawd3D to be ready at :$APP_PORT..."
|
|
ready=0
|
|
for i in $(seq 1 90); do
|
|
if curl -sf "http://localhost:$APP_PORT" > /dev/null 2>&1; then
|
|
ready=1; break
|
|
fi
|
|
sleep 1
|
|
done
|
|
if [ "$ready" -eq 0 ]; then
|
|
warn "Timed out waiting for :$APP_PORT — check $LOG_DIR/clawd3d-dev.log"
|
|
fi
|
|
|
|
# ── 5. Open browser ───────────────────────────────────────────────────────────
|
|
open "http://localhost:$APP_PORT"
|
|
|
|
echo ""
|
|
log "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
|
|
log " Clawd3D → http://localhost:$APP_PORT"
|
|
info " Gateway WS → $GATEWAY_WS_URL"
|
|
info " Hermes API → $HERMES_API_URL"
|
|
info " Logs → $LOG_DIR/"
|
|
log "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
|