Release 0.5.72

[0.5.72] - 2026-05-04

Fixed

• Repair startup when a persisted OpenClaw config still selects the unavailable tools.web.search.provider=brave provider. The add-on now clears that provider before launching the gateway so OpenClaw can start; users can reinstall/enable the Brave provider later if they want web search through Brave.

Full Changelog: v0.5.71...v0.5.72

Release 0.5.71

What's Changed

• Bump OpenClaw to 2026.5.2 by @techartdev in #127

Full Changelog: v0.5.70...v0.5.71

Release 0.5.70

What's Changed

• Bump OpenClaw to 2026.4.27 by @techartdev in #124

Full Changelog: v0.5.69...v0.5.70

v0.5.69

What's Changed

• Bump OpenClaw to 2026.4.24 by @techartdev in #122

Full Changelog: v0.5.67...v0.5.69

Release 0.5.67

What's Changed

• Bump OpenClaw to 2026.4.22 by @techartdev in #121

Full Changelog: v0.5.66...v0.5.67

Release 0.5.66

What's Changed

• fix: re-render landing page with gateway token after onboard (issue #102) by @techartdev in #107
• Bump OpenClaw to 2026.4.12 by @techartdev in #116

Full Changelog: v0.5.65...v0.5.66

Release 0.5.65

What's Changed

• chore: bump OpenClaw to 2026.4.2 by @techartdev in #106

Full Changelog: v0.5.63...v0.5.65

Release 0.5.63

Changed

• Bump OpenClaw to 2026.3.13.

Full Changelog: v0.5.62...v0.5.63

Release 0.5.62

Fixed

• Gateway restart loop (issue #95): openclaw gateway run is a thin wrapper that spawns openclaw-gateway as a long-running daemon then exits. The supervisor had two bugs: (1) pgrep pattern "openclaw.*(gateway|node).*run" never matched the daemon name openclaw-gateway, so self-restarts were never detected; (2) after re-tracking a self-restarted PID, wait failed with "pid N is not a child of this shell" (exit 127) because the new daemon was spawned by the old one, not by run.sh. The supervisor loop now uses pgrep -f "openclaw-gateway" for reliable daemon detection and switches to kill -0 polling for non-child PIDs instead of wait. The loopback relay (tailnet mode) is also stopped/restarted around supervisor-initiated gateway restarts to prevent port conflicts.

Full Changelog: v0.5.60...v0.5.62

Release 0.5.60

Fixed

• Session lock cleanup ignored non-default agents: cleanup_session_locks was hardcoded to agents/main/sessions, skipping stale locks for any agent with a custom forcedAgentId. Stale locks could block the gateway from opening sessions for those agents, causing silent fallback to main. Cleanup now scans all agents/*/sessions/ directories.

Full Changelog: v0.5.59...v0.5.60