DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to connect Kimi Code to Atria Dawn over Chat Completions with Atria Dawn

Add an Atria provider and model entry to Kimi Code's user config.

Authorization notice. Atria Dawn is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The api_key line holds your Atria key as a literal value in a plain config file, so restrict file permissions on that config.

Who it is forA developer who uses Kimi Code and wants Atria Dawn as an OpenAI-compatible model.

The problemKimi Code needs a provider entry with the right base URL, model name, and context setting before it will load the model.

The outcomeKimi Code lists atria/Atria-Dawn as its default model and sends requests to the Atria endpoint.

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

  1. Run kimi --version and confirm you have version 0.43.1 or later.
  2. Back up your config with cp -a ~/.kimi-code/config.toml ~/.kimi-code/config.toml.bak.
  3. Merge the README's default_model, [providers.atria], and [models."atria/Atria-Dawn"] blocks into ~/.kimi-code/config.toml, with base_url https://api.atria-asi.ai/v1.
  4. Put your atr_ key on the api_key line as a literal value.
  5. Start Kimi Code and send a short text prompt to confirm it responds. (inferred, check the README)

Prompt for your agent

Using the atria-asi/Atria-Dawn README, configure Kimi Code 0.43.1 or later to use atria/Atria-Dawn through https://api.atria-asi.ai/v1. Back up ~/.kimi-code/config.toml first, then merge the provider and model blocks. Expected output: a working text reply from Atria Dawn. Verify that default_model is set above the tables and that the context setting is present.

Caveat. The README says the api_key value is read literally, with no ${VAR} expansion and no OPENAI_API_KEY fallback.

Share: 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