philschmid: replace built-in multi-agent features with an MCP server of the harness itself
_philschmid · x · 2026-11-18
philschmid argues agent harnesses should replace built-in multi-agent features by exposing the harness itself as an MCP server: recursively reuse the same loop/CLI to spawn new threads or search past ones, and use MCP events for subscriptions. This lets you rebuild message-board collaboration for one model and an orchestrator pattern for another — and makes iterating or upgrading far easier.
More from coding & agent
- Safer coding agents: synthetic credentials via 1Password intercepting proxy — craigbalding · 2026-11-18
- Which web search API do you actually use for agents? Exa, Tavily, Brave compared — Fluffy-Resident-8734 · 2026-11-18
- AI short film workflow revealed: Seedance 2.5, Kling 4.0, Nano Banana, Suno, Premiere — Uncanny_Harry · 2026-11-18
- Microsoft adds role-based Copilot skills as Agent 365 passes 50 million agents — shashib · 2026-11-18
- Running multiple LLM agents 24/7 on a VPS: why Telegram management falls apart — thetapereader · 2026-11-18
- Full prompt released: one-shot 15s Pixar-style 3D peacock video, covers walking, fanning and rain — CodeByPoonam · 2026-11-18