AWS shows a live preview for agent-built web apps
Its AgentCore walkthrough puts chat beside the changing website.
The AWS walkthrough lets developers inspect a website while a coding agent edits it in its AgentCore session. Vite, the development server, updates the browser as files change. A local intermediary supplies credentials for browser requests. This supports trying changes during development: the session address is temporary, and serving the finished application to users requires a separate hosting deployment.
The access guide separates configuration from execution: allowing a port does not start an application. The developer must start its server listening on 0.0.0.0 at that port. Each request requires authentication; possessing the address grants no permission. Replacement of the underlying compute can interrupt connections, and reconnecting does not guarantee preservation of memory or an unfinished response. Only safely repeatable requests should be retried: a broken connection does not prove that the server never executed the request.
File retention is another decision. AWS’s storage guide describes managed session storage, a preview capability for microVM runtimes. Its configured directory preserves files across stopping and resuming with the same session identifier. When explicitly stopping, wait for the stop operation to finish before resuming. This is not a permanent archive: data resets after fourteen days without an invocation, or when the runtime version changes.