🎯 Use case
This file lives under “utils/”, which covers cross-cutting helpers (shell, tempfiles, settings, messages, process input, …). On the API surface it exposes getHardcodedTeammateModelFallback — mainly functions, hooks, or classes. It composes internal code from model (relative imports). What the file header says: @[MODEL LAUNCH]: Update the fallback model below. When the user has never set teammateDefaultModel in /config, new teammates use Opus 4.6. Must be provider-aware so Bedrock/Vertex/Foundry customers get the correct model ID.
Generated from folder role, exports, dependency roots, and inline comments — not hand-reviewed for every path.
🧠 Inline summary
@[MODEL LAUNCH]: Update the fallback model below. When the user has never set teammateDefaultModel in /config, new teammates use Opus 4.6. Must be provider-aware so Bedrock/Vertex/Foundry customers get the correct model ID.
📤 Exports (heuristic)
getHardcodedTeammateModelFallback
🖥️ Source preview
import { CLAUDE_OPUS_4_6_CONFIG } from '../model/configs.js'
import { getAPIProvider } from '../model/providers.js'
// @[MODEL LAUNCH]: Update the fallback model below.
// When the user has never set teammateDefaultModel in /config, new teammates
// use Opus 4.6. Must be provider-aware so Bedrock/Vertex/Foundry customers get
// the correct model ID.
export function getHardcodedTeammateModelFallback(): string {
return CLAUDE_OPUS_4_6_CONFIG[getAPIProvider()]
}