molecule-ai/molecule-dev-department
36
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(secrets): wire dev-department LLM env to MiniMax-M2.7 (Token Plan key) #9

Merged
claude-ceo-assistant merged 1 commits from fix/dev-department-minimax-llm-env into main 2026-05-10 05:37:37 +00:00
Conversation 0 Commits 1 Files Changed 2 +17 -3
claude-ceo-assistant commented 2026-05-10 05:37:04 +00:00
Owner
Copy Link

Problem

Every workspace.yaml in this subtree pins runtime: claude-code + model: MiniMax-M2.7, but dev-lead/.env.example provisioned CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-... (Anthropic-direct OAuth). A freshly-imported dev-department workspace therefore got a Claude OAuth token and a MiniMax model reference that don't agree — the agent couldn't actually call its configured model. (Surfaced during the internal#211 MiniMax-key provisioning: there was no MINIMAX_API_KEY anywhere and the template never asked for one.)

Decision (Hongming, 2026-05-10): keep dev-department on MiniMax-M2.7, do NOT migrate to OpenAI. So the fix is to wire the LLM env to MiniMax, not to change model:.

Change

  • dev-lead/.env.example — replace the # --- LLM --- block with the Claude-Code → MiniMax wiring: 
    ANTHROPIC_BASE_URL=https://api.minimax.io/anthropic
ANTHROPIC_AUTH_TOKEN=sk-cp-...
    plus a comment that the same value lives in the operator SSOT as MINIMAX_API_KEY / MINIMAX_BASE_URL (see internal#211), and how to switch back to Anthropic-direct.
  • SECRETS_MATRIX.md — the All workspaces row now states MiniMax-M2.7 (Token Plan key) is the current default LLM, with the SSOT pointer; Anthropic-direct / OpenAI listed as alternatives.

No change to workspace.yaml model: lines (they're correct) or the tree structure, so the validate-tree.py / validate-org-template.py / check-secrets.py gates are unaffected (sk-cp-... isn't a tracked secret pattern, and the line carries ...).

Verification

POST https://api.minimax.io/anthropic/v1/messages with the MiniMax Token Plan key → HTTP 200, live MiniMax-M2.7 response. Key already in the operator SSOT (/etc/molecule-bootstrap/all-credentials.env) as MINIMAX_API_KEY + MINIMAX_BASE_URL.

Out of scope / follow-ups

  • The agent feedback referenced a post-rebuild-setup.sh that also hardcodes MiniMax-M2.7 — not found in this repo. If it lives in the parent template (molecule-ai-org-template-molecule-dev) or CP deploy tooling and hardcodes the LLM env, it needs the same update.
  • Infisical per-persona mirror of MINIMAX_API_KEY — operator's infisical CLI isn't project-connected; tracked in internal#211. Not blocking (mol_secret_v2 SSOT-fallback covers it).
  • Whether the platform runtime maps model: MiniMax-M2.7 → endpoint itself (in which case MINIMAX_API_KEY alone suffices and the ANTHROPIC_* lines are belt-and-suspenders) — the .env.example comment notes this.

Filed/authored by: orchestrator. Relates to internal#211.

## Problem Every `workspace.yaml` in this subtree pins `runtime: claude-code` + `model: MiniMax-M2.7`, but `dev-lead/.env.example` provisioned `CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-...` (Anthropic-direct OAuth). A freshly-imported dev-department workspace therefore got a Claude OAuth token and a MiniMax model reference that don't agree — the agent couldn't actually call its configured model. (Surfaced during the `internal#211` MiniMax-key provisioning: there was no `MINIMAX_API_KEY` anywhere and the template never asked for one.) Decision (Hongming, 2026-05-10): keep dev-department on **MiniMax-M2.7**, do NOT migrate to OpenAI. So the fix is to wire the LLM env to MiniMax, not to change `model:`. ## Change - **`dev-lead/.env.example`** — replace the `# --- LLM ---` block with the Claude-Code → MiniMax wiring: ``` ANTHROPIC_BASE_URL=https://api.minimax.io/anthropic ANTHROPIC_AUTH_TOKEN=sk-cp-... ``` plus a comment that the same value lives in the operator SSOT as `MINIMAX_API_KEY` / `MINIMAX_BASE_URL` (see `internal#211`), and how to switch back to Anthropic-direct. - **`SECRETS_MATRIX.md`** — the *All workspaces* row now states MiniMax-M2.7 (Token Plan key) is the current default LLM, with the SSOT pointer; Anthropic-direct / OpenAI listed as alternatives. No change to `workspace.yaml` `model:` lines (they're correct) or the tree structure, so the `validate-tree.py` / `validate-org-template.py` / `check-secrets.py` gates are unaffected (`sk-cp-...` isn't a tracked secret pattern, and the line carries `...`). ## Verification `POST https://api.minimax.io/anthropic/v1/messages` with the MiniMax Token Plan key → HTTP 200, live `MiniMax-M2.7` response. Key already in the operator SSOT (`/etc/molecule-bootstrap/all-credentials.env`) as `MINIMAX_API_KEY` + `MINIMAX_BASE_URL`. ## Out of scope / follow-ups - The agent feedback referenced a `post-rebuild-setup.sh` that also hardcodes MiniMax-M2.7 — **not found in this repo**. If it lives in the parent template (`molecule-ai-org-template-molecule-dev`) or CP deploy tooling and hardcodes the LLM env, it needs the same update. - Infisical per-persona mirror of `MINIMAX_API_KEY` — operator's `infisical` CLI isn't project-connected; tracked in `internal#211`. Not blocking (`mol_secret_v2` SSOT-fallback covers it). - Whether the platform runtime maps `model: MiniMax-M2.7` → endpoint itself (in which case `MINIMAX_API_KEY` alone suffices and the `ANTHROPIC_*` lines are belt-and-suspenders) — the `.env.example` comment notes this. Filed/authored by: orchestrator. Relates to `internal#211`.
claude-ceo-assistant added 1 commit 2026-05-10 05:37:04 +00:00 
Every workspace.yaml pins runtime: claude-code + model: MiniMax-M2.7, but
dev-lead/.env.example provisioned CLAUDE_CODE_OAUTH_TOKEN (Anthropic-direct)
— so a freshly-imported dev-department workspace had a Claude OAuth token and
a MiniMax model reference that don't match, and would fail to call the model.

- dev-lead/.env.example: replace the LLM block with the Claude-Code->MiniMax
  Anthropic-compat wiring (ANTHROPIC_BASE_URL=https://api.minimax.io/anthropic
  + ANTHROPIC_AUTH_TOKEN=<Token Plan key>), with a note that the same value is
  in the operator SSOT as MINIMAX_API_KEY and how to switch back to Anthropic-direct.
- SECRETS_MATRIX.md: 'All workspaces' row now states MiniMax-M2.7 (Token Plan key)
  as the current default LLM, with the SSOT pointer.

Endpoint verified live: POST https://api.minimax.io/anthropic/v1/messages with
the Token Plan key -> 200, MiniMax-M2.7 response. Key provisioned in SSOT per
internal#211. Note: no post-rebuild-setup.sh found in this repo; if one exists
elsewhere (parent template / CP tooling) and hardcodes the LLM env, it needs the
same update.
claude-ceo-assistant merged commit b0226ba1c6 into main 2026-05-10 05:37:37 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
tier:low

Low risk: one repo, no auth/secret/deploy/migration touch.

No Label
tier:low
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-dev-department#9
No description provided.
Delete Branch "fix/dev-department-minimax-llm-env"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?