AgentCore runtime adds build hooks, and AWS lays out four patterns for fast session starts: about 2 seconds for a new session, about 200 ms for a running one
A follow-up to the 11-13 item on the new runtime becoming the default: what initialization belongs before the snapshot, how the new build hooks work, and how chat and voice experiences get under a second.
// Key points
- V2 starts the container once per create or update, waits for the first healthy ping within 120 seconds, then freezes the microVM and stores its memory and disk as a snapshot that each new session restores. The cost is a few extra minutes on every create or update while the snapshot is built.
- Memory comes back whole, but the file cache is cleared before the freeze and image files are fetched on first read, so imports and client creation belong in init, and toolchains that run as separate processes, such as tsc, can be copied to /dev/shm during init.
- Build hooks: the runtime sends two POST requests to an HTTP endpoint in the container during the build, with a header marking memory and then disk, sharing 120 seconds; anything other than a 2xx fails the create or update, with no retry.
- To get under a second, start the session in the background when the user opens the app or chat window; the idle timeout defaults to 15 minutes (60 seconds to 8 hours) and a session lives at most 8 hours.
Builder's takeIn AI Interview, the two seconds of silence before the first reply hurt the experience, and pre-warming the session when the candidate opens the interview page is the cheapest fix; the cost is a session for everyone who opens it and never starts, so keep the idle timeout short. Whether or not you use AgentCore, moving work into init and keeping the first request lean applies to any service with cold starts.
// Background · from #AI agents
Full timeline →- Nov 16 Anthropic breaks down the architecture of always-on agents into five primitives: event inbox, timers, memory, permissions and outbox
- Nov 15 Gemini connects to Google Wallet: US users can let Gemini read their spending for finance insights, but it cannot move money
- Nov 15 Bedrock AgentCore Identity supports OAuth 2.0 authorization server discovery URLs, so servers without OpenID Connect can now plug in