What infrastructure you no longer need to build from scratch to make a Manus in 2026

This piece uses AWS AgentCore as a sample to break down the cloud infrastructure needed to build a Manus-class agent in 2026. A typical Manus task averages 50 tool calls, resting on five hard problems: isolated sandboxes, session stickiness, long-term memory, credential management, and full-chain observability. In 2024 you had to build all of this yourself—the Manus team rebuilt their agent framework four times. By 2026, AWS packaged the whole stack as AgentCore: Runtime gives each session a dedicated Firecracker microVM that runs up to 8 hours; Memory decouples user preferences from compute nodes; Identity holds API keys without writing them to disk; Browser and Code Interpreter handle risky execution in isolation. But AgentCore's microVMs idle-timeout at 15 minutes by default and get destroyed, while Manus treats sandboxes like personal cloud computers kept alive for 7–21 days—cloud vendors optimize for stateless cattle, vertical products for stateful pets. The post doesn't disclose AgentCore pricing or whether Manus actually uses AWS.

Why it matters: The piece breaks down the five infrastructure pillars behind a Manus-class agent (sandbox, session affinity, memory, credentials, observability) and uses AWS AgentCore as a reference to contrast the 2024 all-DIY vs. 2026 managed-cloud landscape. Solid engineering detail with d...