{"title":"Amber 2.0 Beta 2 - A Complete First-Run Path","summary":"A verified installation path, a standalone CLI, and the release boundary for evaluating Amber 2.0.0-beta.2.","date":"2026-07-31","category":"Release","author":"Seth Tucker","url":"https://amberframework.org/blog/2026/07/31/amber-2-beta-2","markdown_url":"https://amberframework.org/blog/2026/07/31/amber-2-beta-2.md","json_url":"https://amberframework.org/blog/2026/07/31/amber-2-beta-2.json","image_url":"https://amberframework.org/assets/characters/amber-hero-original-studio-9664a92e5af8767af84ceab3f1c79f34.webp","content_markdown":"# Amber 2.0 Beta 2: a complete first-run path\n\nAmber `2.0.0-beta.2` is ready for evaluation together with Amber CLI `2.0.2`.\nIt supersedes beta.1 for new applications by fixing server startup with\nCrystal 1.21's default multithreaded runtime.\nThis beta is focused on one thing that has to work before broader ecosystem\nclaims mean much: a new user on a supported Mac or Linux machine can install\nthe CLI, generate an Amber V2 web app, test it, build it, and run it.\n\n## Install the new standalone CLI\n\nOn Apple Silicon macOS or x86_64 Linux with Homebrew:\n\n```bash\nbrew install amberframework/amber_cli/amber_cli\namber --version\n```\n\nThe tap and formula are named `amber_cli`; the executable remains `amber`.\nVerified direct archives and checksum files are also available from the\n[Amber CLI v2.0.2 release](https://github.com/amberframework/amber_cli/releases/tag/v2.0.2).\n\n## Create the beta web app\n\n```bash\namber new my_app --type web\ncd my_app\ncrystal spec\ncrystal build src/my_app.cr -o bin/my_app\namber watch\n```\n\nThe generated app pins Amber `2.0.0-beta.2` from the official framework\nrepository, uses ECR and typed configuration, serves its generated static\nassets, and does not pull an ORM or every database driver into a hello-world\nbuild.\n\n## What this beta guarantees\n\nThe release gate covers Apple Silicon macOS and x86_64 Linux, using Homebrew or\nthe matching release archive. On both platforms we verify the CLI executable,\ndependency installation, generated app specs, compilation, server startup, the\nhomepage, and generated CSS.\n\nThe framework beta includes its controller/router core, Schema API, jobs,\nmailer, WebSockets, adapters, testing support, and typed configuration.\n\n## What is still preview\n\nPersistence-backed model, scaffold, API-resource, and auth generators remain\npreview. Grant, Gemma, the separate Asset Pipeline, and native application\ngeneration also have independent dependency and platform work left. Their\ndocumentation is labeled preview so that useful work-in-progress material is\nnot mistaken for the supported zero-setup path.\n\nAmber V2 removes Kilt and Slang; new and generated V2 views use ECR.\n\n## Read the guides and help us test\n\nStart with the [installation guide](/docs/v2/getting-started/installation/),\nthen work through [Getting Started](/docs/v2/getting-started/) and the\n[beta support matrix](/docs/v2/beta-support/).\n\nWhen reporting a problem, include your OS and architecture, Crystal version,\nAmber CLI version, install method, exact command, and complete output. Use the\n[framework issue tracker](https://github.com/amberframework/amber/issues) for\nframework behavior, the [CLI issue tracker](https://github.com/amberframework/amber_cli/issues)\nfor generators or binaries, and the [tap issue tracker](https://github.com/amberframework/homebrew-amber_cli/issues)\nfor Homebrew installation.\n\nThis is a beta, not the finish line. But it is the first V2 release with one\ndocumented path that is meant to be followed exactly and tested end to end.\n"}