🪟 Living Code for 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.

Expand a flavor for its activation instructions.

"colorScheme": "Living Code Night"

"colorScheme": "Living Code Frost"

"colorScheme": "Living Code Paper"

"colorScheme": "Living Code Signal"

See Windows Terminal's documentation for application settings and reload behavior. The activation instructions above identify each supported flavor; keep your other application configuration.

This port supplies theme files for Windows Terminal, not the application itself. Install the application separately and follow the installation instructions for its supported configuration format.

Found a problem? Open an issue with the app version, the flavor and a screenshot. Want Living Code somewhere else? Request a port.

Pull requests are welcome. Keep this README, port.json and images/ in sync, and use real screenshots of the app, never mockups.