One agent, forty customer containers, tools that run over there

Your SaaS runs one agent daemon. Forty customers each have a container with their code. You don't want forty agents, forty sessions, forty model contexts. You want one agent whose hands reach into whichever container the request is about.

A tool call carries X-Hoody-Container. With it, read_file, bash, and list_dir execute on that customer's machine, and the result comes back to the one session. The agent never copies the customer's repo to itself. It reads it where it lives, runs tests where they live, and moves on to the next container with the next header.

The routing is a header on a tool call, not a fleet of agents. One brain, forty pairs of hands, and the hands are the only thing that moves.

Multi-tenant isn't forty agents. It's one agent with a container header.