# Renaming commands

You can rename a command from its settings. 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.

## Automatic renaming

[Terminal title sequences](../terminal/osc-kitty-protocol.md) can update the sidebar title for commands, terminals, and agents when automatic renaming is enabled. The context menu includes **Disable automatic renaming** / **Enable automatic renaming** for supported process types.

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](../agents/setting-up-tools.md) > 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](./trust-security.md) when the underlying configuration is unchanged.

---

Are you a human? Read this doc on the web: https://soloterm.com/docs/commands/renaming