Moving Your Settings to Focused Tables
Nash 0.10.3 reorganizes nash.toml into smaller tables with shorter key names.
Pane highlights, pane numbers, agent status, agent alerts, and cursor wakes now
have their own sections rather than sharing broad groups of prefixed settings.
This is an upgrade that needs attention if you customized the file. The old keys are no longer read. Keeping an old value in place does not preserve the behavior it controlled, even if the file remains valid TOML.
Migrate Values, Not Whole Sections
Move your existing nash.toml aside, keeping it as a reference. Start Nash so
it generates a fresh file, then copy your custom values into the matching new
tables. The default location is ~/.config/nash/nash.toml; use your actual
configuration directory if you have overridden it.
The new sections include [pane.highlight], [pane.numbers], [agent.status],
[agent.alerts], and [cursor.wake]. Find the setting in the generated file
before carrying its value across. Pasting an old section back wholesale leaves
you with names the new release ignores.
Agent badges provide a concrete example. Before this release, their settings
lived under [pane] with a pane_agent_status_ prefix. They now live under
[agent.status]. To put a badge at the bottom right, set position to
"bottom_right" there. To omit seconds from its completion timestamp, set
finished_format to '%H:%M' in that same table. The
agent configuration guide
shows these names and their defaults.
Do Not Rely on an Automatic Rename
Normal configuration sync adds missing defaults; it is not a substitute for this manual migration. An old key alongside a new default can look like a preserved customization while no longer affecting anything.
Work through the settings you actually changed and check their visible behavior after migration. Keep the old file until you have checked the result. The configuration sync reference explains the normal merge behavior and how to inspect bundled defaults; the 0.10.3 table reorganization still requires moving your values yourself.
Separate the Persistent Mark from Its Trail
The pane-highlight wake can now have a different thickness from the permanent
indicator. Its default is 2pt; zero hides the wake. This lets you keep a
persistent focus marker without requiring its trailing effect to have the same
visual weight. This is a pane-highlight control, distinct from cursor wake
settings.
Matrix fades also change in 0.10.3. On entry, terminal characters become green
glyphs before the running code takes over. On exit, text returns from the top
down as runners leave and the background fades back. For a natural finish rather
than a fixed exit duration, set the fade-out effect's duration_ms to an empty
string (""). Use the generated file to locate that effect's setting rather
than copying an older configuration section.