Download this from the color session. It contains a [colors] table and metadata. It does not contain a prompt, font, shell command or program theme. The Chalk preset downloads as HuePrompt-Chalk.toml.
Your active WezTerm Lua configuration
Use the configuration file you already edit. Common user locations include ~/.wezterm.lua and ~/.config/wezterm/wezterm.lua. Windows can also use a configuration beside the executable. The exact search order matters if several files exist; see WezTerm’s configuration locations.
A backup you can open in a text editor
Copy your current Lua file before editing. Keep that copy outside the active filename. Record any existing colors, color_scheme or appearance-switching code so you can restore it.
Place the downloaded TOML file beside the active Lua file. The examples below use wezterm.config_dir, which points to that configuration directory. Do not paste your Downloads path from somebody else’s machine.
In a file that already defines wezterm and config, add these lines before its final return config. Substitute the actual downloaded filename. Use the name of your existing configuration table if it is not called config.
This intentionally assigns the palette’s colors. It replaces an earlier assignment to config.colors; a later assignment can replace it again. Keep the backup and review your file rather than adding the block in several places.
Do not add a second return midway through your file. If your configuration returns a table directly, add the colors to that table or adapt it to one named configuration table. The rest of your font, keys and launch settings should remain yours.
NEW CONFIG
Only if you do not already have a configuration, this is a complete minimal file. Keep the TOML beside it.
local wezterm = require 'wezterm'
local config = {}
local palette = wezterm.color.load_scheme(
wezterm.config_dir .. '/HuePrompt-Harbor.toml'
)
config.colors = palette
return config
The palette changes terminal colors. It leaves font choice, spacing, shell and prompt configuration at their existing defaults. Begin with an opaque window and a familiar command so you can judge the colors without changing five other things at once.
DIAGNOSTICS
Cannot open the TOML
Check the full filename, including an accidental .txt extension or a browser-added (1). Confirm it is beside the active Lua file. The JSON draft belongs in HuePrompt; it is not a WezTerm scheme.
Configuration error after pasting
Restore the backup first. Check whether you pasted a whole minimal file inside an existing table, used a different variable name, or left two final return statements. A palette is not a reason to replace the rest of a working configuration.
Default text changed, but an application did not
Inspect that application’s theme and truecolor output. The color layers manual separates those cases from a file-loading problem.
Colors change again after startup
Look for later assignments, appearance-change handlers or programs sending dynamic palette sequences. Those can supersede the initial palette. Test with your normal configuration and a plain terminal before blaming the exported values.
Format check: an original palette exported by this editor is loaded by the official WezTerm stable CLI 20240203-110809-5046fc22. This checks parsing and color values. It does not promise pixel-identical browser and native rendering, or verify every configuration plugin.
COLOR PROBE
When one program ignores your new palette, isolate what kind of color it requests before editing the scheme again. This small original probe prints default text, a named ANSI red slot, an explicit RGB value and all sixteen numbered ANSI foreground samples.
It only prints text and SGR styling sequences, then resets text styling. It does not edit configuration, change palette definitions, install packages or contact a server. Its emitted bytes were checked for the listed ANSI/RGB sequences; that does not establish how every terminal renders them.
The ANSI red changes; explicit RGB does not
This is a useful separation. The named red slot uses the palette, while the second line requests #E49B9B directly. If your editor behaves like the RGB line, inspect the editor’s own theme or color settings. Repeatedly changing the terminal’s red slot may be changing the wrong layer.
Neither default text nor ANSI samples change
Return to the active configuration path and loading errors. Compare a newly opened terminal with the existing one. Check for a later assignment or appearance-switching branch that replaces the selected colors. Keep the original working file; do not replace your keys and shell setup just to make a palette load.
The sample changes, but a selected line is unreadable
Selection uses its own foreground/background pair. Drag across the probe’s text and inspect the actual selected colors. A passing unselected foreground/background ratio does not answer this question. Use the pair-by-pair manual for selection and block-cursor checks.
The same window changes after running a program
Compare before and after that program separately from changing the config file. WezTerm documents dynamic palette changes through escape sequences. This probe deliberately does not emit those palette-changing sequences, so it can be a stable small input while you investigate the other application.
Terminal palette and dynamic-color reference: WezTerm colors and appearance. These are diagnostic branches, not a claim that one symptom uniquely identifies a fault.
Write down the terminal version, selected configuration, exact probe line and whether you were looking at selected text. If comparing two screenshots, use the same line and background. A random colourful command makes a less useful comparison because its content and application theme may change at the same time.
ROLLBACK
Restore the previous Lua file, or remove the added loader and restore the earlier color settings you recorded. Keep the new palette file if you want; an unused TOML is not applied on its own by this loader. Save the configuration and check a new terminal window. If an existing application has changed its palette dynamically, restart that application as well.
Once the colors are installed, inspect a diff, selected text and the cursor against your actual background. Use the readability manual to decide which pairs need attention.
Additional reference: WezTerm color precedence. Instructions and examples checked October 25, 2026.