The subagent revelation & tiered routing

Hit my first major architecture roadblock with the local Telegram bot. Gave it a massive 10-source web research task. If it ran on the main thread, the bot would have been locked completely for 45 minutes, unable to answer new texts. Instead, the OpenClaw orchestration engine automatically spawned a headless 'Subagent' background process. The main bot said 'I'll get back to you', freed up the thread, and the Subagent crunched the web in the background for 42 minutes before delivering a perfect markdown report. Now looking at Tiered Routing: running a fast E2B model as the communicative router on the GPU, and delegating the heavy lifting Subagents to a 26B MoE running purely on system RAM. The iMac 2017 handles it flawlessly.