Windows Terminal

Run this in PowerShell. It saves a JSON fragment that Windows Terminal loads by itself, so nothing in settings.json is edited:

$d = "$env:LOCALAPPDATA\Microsoft\Windows Terminal\Fragments\living-code"; New-Item -ItemType Directory -Force $d | Out-Null; Invoke-WebRequest https://raw.githubusercontent.com/living-code-theme/windows-terminal/main/living-code.json -OutFile "$d\living-code.json" -UseBasicParsing

Restart Windows Terminal. The four schemes appear in Settings → Color schemes; select one under a profile's Appearance, or set it in settings.json:

"colorScheme": "Living Code Night"

Fallback: paste the scheme objects from living-code-*.json into the schemes array of settings.json.

Run this in PowerShell. It saves a JSON fragment that Windows Terminal loads by itself, so nothing in settings.json is edited:

$d = "$env:LOCALAPPDATA\Microsoft\Windows Terminal\Fragments\living-code"; New-Item -ItemType Directory -Force $d | Out-Null; Invoke-WebRequest https://raw.githubusercontent.com/living-code-theme/windows-terminal/main/living-code.json -OutFile "$d\living-code.json" -UseBasicParsing

Restart Windows Terminal. The four schemes appear in Settings → Color schemes; select one under a profile's Appearance, or set it in settings.json:

"colorScheme": "Living Code Frost"

Fallback: paste the scheme objects from living-code-*.json into the schemes array of settings.json.

Run this in PowerShell. It saves a JSON fragment that Windows Terminal loads by itself, so nothing in settings.json is edited:

$d = "$env:LOCALAPPDATA\Microsoft\Windows Terminal\Fragments\living-code"; New-Item -ItemType Directory -Force $d | Out-Null; Invoke-WebRequest https://raw.githubusercontent.com/living-code-theme/windows-terminal/main/living-code.json -OutFile "$d\living-code.json" -UseBasicParsing

Restart Windows Terminal. The four schemes appear in Settings → Color schemes; select one under a profile's Appearance, or set it in settings.json:

"colorScheme": "Living Code Paper"

Fallback: paste the scheme objects from living-code-*.json into the schemes array of settings.json.

Run this in PowerShell. It saves a JSON fragment that Windows Terminal loads by itself, so nothing in settings.json is edited:

$d = "$env:LOCALAPPDATA\Microsoft\Windows Terminal\Fragments\living-code"; New-Item -ItemType Directory -Force $d | Out-Null; Invoke-WebRequest https://raw.githubusercontent.com/living-code-theme/windows-terminal/main/living-code.json -OutFile "$d\living-code.json" -UseBasicParsing

Restart Windows Terminal. The four schemes appear in Settings → Color schemes; select one under a profile's Appearance, or set it in settings.json:

"colorScheme": "Living Code Signal"

Fallback: paste the scheme objects from living-code-*.json into the schemes array of settings.json.