Replies: 1 comment
|
Thanks, this is a useful Windows and VS Code workflow. One small correction: terminal profiles belong in .vscode/settings.json, not tasks.json, and the trailing comma in the example should be removed for valid JSON. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Codex uses the exe. i dont. so adding a terminal dropdown in VSCode allows you to open up the venv quickly:
.vscode\tasks.json
{ "terminal.integrated.profiles.windows": { "PowerShell (MemoryOS)": { "source": "PowerShell", "args": [ "-NoExit", "-Command", "& 'C:\\memoryos\\.venv\\Scripts\\Activate.ps1'" ] }, "Codex CLI": { "source": "PowerShell", "args": [ "-NoExit", "-Command", "& 'codex'" ] }, } }All reactions