OpenClaw React Client Update Adds Model Per Agent, CLI Tool, and Auto-Start
OpenClaw Client Update Features
The open-source OpenClaw React client has received a major update following community feedback. The project gained significant traction with over 900 clones in its first week.
New Features
- Model Per Agent: You can now assign specific models to specific agents. To configure this, click the + button, hit configure, and select the model you want for that agent.
- Auto-Updates: The client now receives updates automatically. You'll see a notification right on the dashboard when a new update is available.
- New CLI Tool: Managing the client is now easier with terminal commands. You can run
openclaw_client start | stop | restart | uninstalldirectly from your terminal. - Auto-Start: The client now runs automatically after a system reboot, eliminating the need to start it manually each time.
The update is available in the GitHub repository, which has seen significant community engagement. OpenClaw is an open-source platform for AI coding agents, and this client provides a React-based interface for interacting with the system.
📖 Read the full source: r/clawdbot
👀 See Also
Open-Source Framework Uses Claude Code CLI for Automated GitHub Repo Monitoring
A developer has open-sourced a framework that runs Claude Code CLI on a cron schedule to triage GitHub activity across multiple repositories. The tool includes state tracking, deduplication, Discord notifications, and a pre-check system that avoids API costs when nothing has changed.
Wisepanel MCP Server Enables Multi-LLM Deliberation in Claude Code and Cursor
Wisepanel released an MCP server that runs multi-agent deliberations directly from Claude Code, Cursor, or any MCP client, using a divergent context enhancement system with ChatGPT, Claude, Gemini, and Perplexity models.
Testing MiniMax M2.7 via API on Three Real ML and Coding Workflows
A developer benchmarks MiniMax M2.7 against Claude Opus 4.7 on three real tasks: refactoring a PyTorch project, drafting Obsidian notes, and more. Key findings and setup included.
Building a Sub-500ms Voice Agent: Architecture and Performance Insights
A developer built a voice agent from scratch achieving ~400ms end-to-end latency with full STT → LLM → TTS streaming. Key insights include treating voice as a turn-taking problem, using semantic end-of-turn detection, and colocating all components for minimal latency.