Files
agent-runtime-framework/harnesses/contexts/minimax-m3-max/v1/harness.yaml
Paul O'Reilly 7244e0ec5f fix(minimax-m3-max, fable-low-effort): H-SECRET-4 rejected MAX_THINKING_TOKENS in env
The validator pattern-matches *TOKEN* as credential-shaped and rejected
both contexts, failing every task on the new harnesses. The env var name
is fixed by Claude Code, so deliver the thinking budget via the
settings.json env map in init.sh instead (jq-merge preserves apiKeyHelper
from the minimax/oauth layer).

Claude-Session: https://claude.ai/code/session_019tJk7P8tZzJ24PvtgoGhLN
2026-09-03 00:39:59 +12:00

23 lines
913 B
YAML

kind: context
name: minimax-m3-max
version: 1
description: "Pin MiniMax M3 (1M context) at max reasoning effort — layer AFTER minimax/v1 (auth + base URL come from there)"
requires: [claude-code]
provides: []
# Model pin + effort for the MiniMax Anthropic-compatible proxy.
# - ANTHROPIC_MODEL forces every main-loop request to M3 (1M context variant)
# instead of the proxy's default Claude-name mapping.
# - The max thinking budget (M3 reasoning effort) is set by init.sh via
# settings.json — the env var name trips H-SECRET-4's credential pattern
# so it cannot live in this env: block.
# - CLAUDE_CODE_AUTO_COMPACT_WINDOW matches M3's real 1M window (the proxy's
# model metadata under-reports 200K, which triggers premature compaction).
env:
ANTHROPIC_MODEL: "MiniMax-M3[1m]"
ANTHROPIC_SMALL_FAST_MODEL: "MiniMax-M3"
CLAUDE_CODE_AUTO_COMPACT_WINDOW: "1000000"
scripts:
init: ./init.sh