I built RouteSmith because mixed prompts are workflows, not single tasks. It routes coding-agent work across real host constraints instead of pretending every environment works the same way. TL;DR I built RouteSmith because coding agents still make users do too much manual routing. If a prompt says, "plan this feature, implement it, add tests, and write docs," that is not one task. It is a workflow. RouteSmith detects the current host, decomposes the prompt into task types, maps those tasks to capability classes, and routes them using what the host can actually support. If the host supports switching, RouteSmith can suggest concrete models. If it does not, RouteSmith falls back honestly instead of pretending switching happened.…