v0.2.1

Fixed

• AWS SSO login instructions. The documented aws sso login --no-browser cannot complete inside a MicroVM: a bare aws sso login resolves the default profile, and the Authorization Code flow redirects to the VM's own 127.0.0.1. The README and the in-sandbox agent guidance now use aws configure sso followed by aws sso login --profile <name> --use-device-code.

Docs only, but microvm/agents/AGENTS.md is part of the image, so the next ./scripts/deploy.sh rebuilds it.

Full changelog: v0.2.0...v0.2.1

v0.2.0

Added

• Configurable image tools. Choose coding agents and optional infrastructure CLIs in deploy.env, using a current release, a pinned version, or an explicit disable.
• Deployment previews. ./scripts/deploy.sh --dry-run creates a CloudFormation changeset without applying it.

Changed

• Budget alerts are explicit. Set BUDGET_EMAIL to create a monthly budget; leave it unset to skip one.
• No-change deploys are quieter. They skip frontend publishing, CloudFront invalidation, and MicroVM artifact uploads when their inputs are unchanged.
• Claude Code is the default agent. The generated deploy.env enables it while keeping the other agents opt-in.
• Chooser screenshot refreshed.

Fixed

• Concurrent frontend deploys. IDE asset uploads use isolated temporary files instead of sharing one path.
• Smoke-test prerequisites. Deployment detects AWS CLI installations that lack Lambda MicroVM support before applying a stack update.

v0.1.0

Added

• Per-user AWS Lambda MicroVMs. Each user gets a dedicated MicroVM, launched on demand and suspended when idle, with configurable memory and lifetime limits.
• A persistent home on Amazon S3 Files. The home is a per-user S3 Files access point mounted at /home/coder, so files, shell history, and logins survive restarts and VM recycles.
• A browser VS Code workbench. A real VS Code workbench served from CloudFront, with its file system and terminal backed by an in-VM agent over an authenticated WebSocket, and a File menu action back to the chooser.
• A browser terminal. An xterm.js terminal with a touch key bar and PWA install; clicking a file path in the output opens it in the editor.
• Four coding CLIs, preinstalled and preconfigured for unattended work: Claude Code, Codex CLI, OpenCode, and Kiro CLI. Each uses the user's own provider login; no API keys ship in the image.
• Cognito authentication. Admin-created users only, with API Gateway validating the JWT before a token-vending Lambda finds or creates the user's home, launches or resumes their MicroVM, and mints short-lived credentials.
• One-command deploy and teardown. scripts/deploy.sh bootstraps the stack, builds the IDE and MicroVM image, uploads the frontend, creates the first login, and smoke-tests a throwaway VM; scripts/teardown.sh removes everything it created.
• Runtime configuration through deploy.env: MicroVM memory, idle, suspend, and lifetime limits, NAT mode (instance or gateway), and a monthly AWS Budget whose limit, recipient, and enable/disable are configurable.
• Release-based versioning. The footer shows the running release and flags newer GitHub releases instead of treating every commit as an update.
• Break-glass tooling (tools/) to reach a running MicroVM without SSH.