Problems / Multi-agent and harness, medium
A long-running harness depends on one model provider, which is down for 20 seconds mid-run.
Free to open. Runs in your browser, no sign-up.
Success ≥ 95% of tasks, p99 ≤ 90 s.
1 requests a second for 45 seconds: 100% task (writes).
What each component does in this design, and what calls it. The simulator mimics each one from these settings.
| Component | Its job here | Settings |
|---|---|---|
| Load balancerLoad balancer | Traffic enters here.Calls Agent API.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| Agent APIApp service | Load balancer forwards to it.Calls Agent harness.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s. | 3 replicas × 500 slots · timeout 180 s |
| Agent harnessAgent harness | Agent API calls it.Calls Model, MCP tool servers.A harness is everything around the model in an agent: context management, tools, checkpoints, retries and evaluation. | 400 slots · 6 steps |
| ModelLLM endpoint | Agent harness calls it.Latency has two parts: time to the first token, then a steady stream of tokens per second. | 300 streams |
| MCP tool serversTool / MCP server | Agent harness calls it.Tools give the model actions such as search or database queries; each call is another round trip. | 200 slots |
Try it first. Open one hint at a time if you get stuck.
Long tasks are likelier to hit an outage.
Multiply by the fan-out and the number of turns to get the real call rate on shared models and tools.
Add a fallback model.