Authorization notice. Atria Dawn is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA team or researcher that needs to host Atria Dawn in its own environment instead of calling the hosted API.
The problemHosted access may not fit data handling or cost needs, so the model has to run locally on a supported inference framework.
The outcomeAn inference server runs Atria Dawn locally and accepts requests.
What you need first
- An Atria API key created in the Atria console (shown only once)
- Codex CLI 0.154.0 or later for the Codex setup
- Claude Code with access to ~/claude_dir/settings.json for the hook setup
- Kimi Code 0.43.1 or later for the Kimi setup
- SGLang v0.5.13.post1+ or vLLM v0.23.0+ for local deployment
Steps
- Choose SGLang at v0.5.13.post1 or later, or vLLM at v0.23.0 or later.
- Open the SGLang cookbook link for GLM-5.2 or the vLLM recipes link for zai-org/GLM-5.2 from the README.
- Install the chosen framework at the minimum version and follow its GLM-5.2 guide to load the model. (inferred, check the README)
- Check the Download table: Atria Dawn Preview and Preview FP8 are on Hugging Face and ModelScope, while the full release says Coming soon.
Prompt for your agent
Using the atria-asi/Atria-Dawn README, set up a local inference server for Atria Dawn with SGLang v0.5.13.post1 or later, or vLLM v0.23.0 or later, following the linked guide. Choose a model from the download table that is currently available. Expected output: a running local server that answers one test request. Verify the framework version before loading the model.
Caveat. The README gives no hardware requirements, and the full Atria Dawn and FP8 releases are listed as Coming soon, so only the Preview models can be downloaded now.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page