MESH-API v0.7.2 Beta - Channel Agents in the WebUI

MESH-API v0.7.2 Beta — Channel Agents in the WebUI

A feature release on top of v0.7.1 Beta. All v0.7.0/v0.7.1 functionality is unchanged.

🤖 New: Channel Agents Manager (WebUI)

The Channel Agents routing feature (assign a channel to a dedicated AI provider or extension, introduced in v0.7.0) is now fully manageable from the dashboard — no more hand-editing config.json.

• New 🤖 Agents toolbar button opens a Channel Agents manager.
• Per-channel assignment: route any channel to a specific AI provider (OpenAI, Hermes, Ollama, Claude, Gemini, Grok, OpenRouter, Groq, DeepSeek, Mistral, LM Studio, OpenAI-compatible, or Home Assistant) or to a loaded extension (e.g. OpenClaw). Optional per-channel 🔒 PIN gate.
• Applies live — assignments take effect on the very next message, no restart required. They persist to config.json (only the channel_agents block is rewritten; all other settings/secrets are preserved).
• Channel badges: channels with an assigned agent now show a badge (🤖 provider / 🧩 extension, plus 🔒 when a PIN is required) in the Channel Messages panel.
• Legacy aware: the old home_assistant_channel_index mapping is surfaced automatically so existing Home Assistant setups show up without reconfiguration.

API

• GET /api/channel_agents now also returns the available AI providers, the currently loaded extensions, and channel names (everything the editor needs).
• POST /api/channel_agents saves assignments, persists them to config.json, and applies them live.

🐳 Docker

Multi-arch images (linux/amd64 + linux/arm64) for this release will be published to Docker Hub: mrtbot/mesh-api after community testing.

---

Built and maintained by one developer with the help of AI tools. If MESH-API is useful to you, please consider a donation (links in the README) and file issues with your real-world experience. 🙏