migrateOpusToOpus1m.ts
migrations/migrateOpusToOpus1m.ts
No strong subsystem tag
44
Lines
1347
Bytes
1
Exports
3
Imports
10
Keywords
What this is
This page documents one file from the repository and includes its full source so you can read it without leaving the docs site.
Beginner explanation
This file is one piece of the larger system. Its name, directory, imports, and exports show where it fits. Start by reading the exports and related files first.
How it is used
Start from the exports list and related files. Those are the easiest clues for where this file fits into the system.
Expert explanation
Architecturally, this file intersects with general runtime concerns. It contains 44 lines, 3 detected imports, and 1 detected exports.
Important relationships
- migrations/migrateAutoUpdatesToSettings.ts
- migrations/migrateBypassPermissionsAcceptedToSettings.ts
- migrations/migrateEnableAllProjectMcpServersToSettings.ts
- migrations/migrateFennecToOpus.ts
- migrations/migrateLegacyOpusToCurrent.ts
- migrations/migrateReplBridgeEnabledToRemoteControlAtStartup.ts
- migrations/migrateSonnet1mToSonnet45.ts
- migrations/migrateSonnet45ToSonnet46.ts
Detected exports
migrateOpusToOpus1m
Keywords
modelopususersettingsparseuserspecifiedmodelsettingsmigratedlogeventgetdefaultmainloopmodelsettingisopus1mmergeenabledutils
Detected imports
../services/analytics/index.js../utils/model/model.js../utils/settings/settings.js
Source notes
This page embeds the full file contents. Small or leaf files are still indexed honestly instead of being over-explained.
Full source
import { logEvent } from '../services/analytics/index.js'
import {
getDefaultMainLoopModelSetting,
isOpus1mMergeEnabled,
parseUserSpecifiedModel,
} from '../utils/model/model.js'
import {
getSettingsForSource,
updateSettingsForSource,
} from '../utils/settings/settings.js'
/**
* Migrate users with 'opus' pinned in their settings to 'opus[1m]' when they
* are eligible for the merged Opus 1M experience (Max/Team Premium on 1P).
*
* CLI invocations with --model opus are unaffected: that flag is a runtime
* override and does not touch userSettings, so it continues to use plain Opus.
*
* Pro subscribers are skipped — they retain separate Opus and Opus 1M options.
* 3P users are skipped — their model strings are full model IDs, not aliases.
*
* Idempotent: only writes if userSettings.model is exactly 'opus'.
*/
export function migrateOpusToOpus1m(): void {
if (!isOpus1mMergeEnabled()) {
return
}
const model = getSettingsForSource('userSettings')?.model
if (model !== 'opus') {
return
}
const migrated = 'opus[1m]'
const modelToSet =
parseUserSpecifiedModel(migrated) ===
parseUserSpecifiedModel(getDefaultMainLoopModelSetting())
? undefined
: migrated
updateSettingsForSource('userSettings', { model: modelToSet })
logEvent('tengu_opus_to_opus1m_migration', {})
}