This release transforms the first-run experience: taskmeld init now auto-detects a local OpenClaw installation, offers one-click install if missing, and guides users through Gateway configuration — no more manual setup. The server startup is rewritten to run foreground-first with automatic local Gateway lifecycle management.
Added
- OpenClaw local detection and management — New
src/openclaw/module:openclaw-detector.ts: Detect local OpenClaw installation, version, and config pathopenclaw-installer.ts: One-click install vianpm install -g openclaw@latestopenclaw-gateway.ts: Gateway start/stop/status management and health pollingopenclaw-types.ts: Type definitions for detection results and config schema
- Init orchestrator (
src/init/): Rewritten interactive setup flow with branching logic:- Auto-detect local OpenClaw → auto-connect if running with token
- Three paths on missing install: auto-install, remote Gateway, manual
- Optional model configuration delegation to
openclaw configure
- Non-interactive init modes:
--auto-install,--remote <url>,--skip-model-configflags for CI/CD - Server runtime client: Foreground-first server startup with startup lock, health polling, and ownership probing
- 10 new test files (~1400 lines) covering Wevra loop/executor/memory/registry/permissions, pipeline readiness, OpenClaw detector, CLI enhanced init, and LLM client stream
Changed
- Server start rewrite:
taskmeld server startnow runs in foreground; auto-starts local OpenClaw Gateway when installed locally - Init command rewrite: From simple Gateway connection prompt to full orchestration with detection, installation, and branching user choices
- UI prompts: Added
numberedSelectPrompt,maskedFieldPromptfor init flow - Localization: New translation keys for init flow (en/zh.json +61 each)
- README overhaul: Updated architecture diagram, prerequisites, install flow, quick start, directory structure, and roadmap to reflect OpenClaw management capabilities
- Version bumped to 0.2.5
Fixed
- Gateway connect errors: Retryable connection failures treated as transport errors, properly propagated up
- Init remote config: Remote Gateway URL/Token saved without requiring live connection validation
- Security: API and Vite dev server restricted to
127.0.0.1only, no longer binding to0.0.0.0 - Server process group: Cleaner daemon lifecycle management