What changed
Roder adds Fireworks AI inference and first-class Kimi Code support. Kimi Code supports subscription OAuth and Moonshot API-key fallback, while Fireworks can route to account-scoped model IDs through normal provider configuration.
Provider coverage also moved into app-server lists and smoke tests, making these providers visible to terminal and client integrations instead of hiding them as config-only options.
Why it matters
- Teams can route coding-agent turns to Fireworks account-scoped model IDs through the same provider configuration flow as the rest of Roder.
- Kimi Code users can authenticate with subscription OAuth or a Moonshot API key, giving both individual and platform setups a path into the CLI.
- App-server provider lists make the new providers visible to integrations that rely on Roder’s runtime metadata.
Setting it up
Use roder auth login kimi-code for Kimi subscription OAuth, or configure a Moonshot API key for API-key based Kimi Code usage. Fireworks follows the standard provider configuration path.