Renaming commands

You can rename a command from its settings, and rename any agent or terminal from its context menu. Renaming changes the label Solo uses for the process and can also update solo.yml when the command is file-backed.

What renaming changes#

Renaming updates the process name and the display name stored for that process. It does not change the shell command string or rename project files and folders.

If the command is saved in solo.yml, Solo rewrites the process key in solo.yml and records the synced file state. If the command is local-only, the rename stays local.

How to rename#

1. Right-click the command in the sidebar and choose Edit command....
2. Change the name field.
3. Confirm.

For agents and terminals, right-click the row and choose Rename agent... or Rename terminal....

You can also open the rename dialog for any selected command, agent, or terminal from the keyboard:

• Choose Rename in Context actions (Cmd+P on macOS, Ctrl+P on Windows and Linux).
• Bind the Rename process command in Settings > Hotkeys. It has no default shortcut.

Automatic renaming#

Terminal title sequences can update the sidebar title for commands, terminals, and agents when automatic renaming is enabled. To turn it off for one process, right-click the row in the sidebar and clear Settings ▸ Automatic renaming. The terminal's own right-click menu offers the same choice as Disable automatic renaming / Enable automatic renaming. The same Settings submenu also holds Notification level for the process.

Manual rename sets a display-name override. That override wins over OSC/runtime titles until the display name is cleared.

Global toggle for agents#

Agents can be noisy renamers, so there's also a global switch: Settings > Agents > Names > Automatic renaming. It's on by default. Turning it off stops all agents from updating their sidebar names from title changes, overriding any per-agent automatic renaming setting. It only affects agents — commands and terminals keep following their own per-process setting.

Notes#

• The new name must be non-empty and unique within the project.
• Renaming a solo.yml command preserves its trusted command-variant history when the underlying configuration is unchanged.