You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🤖 refactor: normalize runtimeConfig in config file on load
Instead of applying DEFAULT_RUNTIME_CONFIG on-the-fly, we now migrate
missing runtimeConfig to the config file during load. This makes the
config file the single source of truth and eliminates runtime conversion.
Changes:
- Removed ensureRuntimeConfig() and getDefaultRuntimeConfig() methods
- Apply DEFAULT_RUNTIME_CONFIG directly when loading workspaces
- Save normalized config back to disk (configModified = true)
- All 4 workspace loading paths now write runtimeConfig to config
Benefits:
- Config file is normalized once, not on every read
- Simpler code - no runtime conversions needed
- Easier to remove this migration code in the future
Copy file name to clipboardExpand all lines: docs/vscode-extension.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
# VS Code Extension
2
2
3
-
The cmux VS Code extension allows you to quickly jump into your cmux workspaces directly from Visual Studio Code or Cursor.
3
+
The cmux VS Code extension allows you to quickly jump into your cmux workspaces directly from Visual Studio Code or Cursor. This enables a more seamless back and forth between a purely agentic workflow and traditional editing. It's
4
+
especially useful for completing the "last mile" of a task or establishing the initial architecture.
0 commit comments