Skip to content

Conversation

@sd0xdev
Copy link

@sd0xdev sd0xdev commented Jan 30, 2026

Closes #51.

Background

OpenClaw/OpenClawd defines MINIMAX_API_KEY as the API key environment variable for the MiniMax provider.

When running this worker with a containerized gateway, that env var needs to be forwarded into the container process environment so OpenClaw can resolve it (e.g. when models.providers.minimax.apiKey references ${MINIMAX_API_KEY}).

What changed

  • Add optional MINIMAX_API_KEY to the worker env bindings (MoltbotEnv).
  • Forward MINIMAX_API_KEY into the container/gateway process env (via buildEnvVars).
  • Add unit test coverage for env forwarding.
  • Document the new secret in README and .dev.vars.example.

Benefits

  • Allows users to configure the MiniMax provider without baking the API key into config files.
  • Backwards compatible: no behavior change when MINIMAX_API_KEY is unset.

- Add MINIMAX_API_KEY to worker env bindings
- Forward MINIMAX_API_KEY into the container process env
- Document MINIMAX_API_KEY and add unit test coverage
- Do not overwrite config.agents.defaults.model.primary on restart if already set
- Document optional MiniMax provider setup (MINIMAX_API_KEY + models.providers.minimax)
Follow codex review: if model.primary is unset or not allowlisted for the currently configured provider catalog, reset to a safe default. Also avoid leaving stale primary values when falling back to default catalog.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Please support MINIMAX_API_KEY

1 participant