# Rename and delete ICDs

> Rename ICDs, messages, and fields, or delete them.

Rename an [ICD](https://docs.synnaxlabs.com/reference/hardware/icds) to give it a clearer name. Delete an ICD that no task uses any more.

## Rename ICDs

**Console**

Right-click the ICD in the **ICDs** toolbar and select **Rename**. You can also click the name at the top of the ICD’s tab.

**Python**

```python
client.icds.rename(oven.key, "Oven 2")
```

**TypeScript**

```typescript
await client.icds.rename(oven.key, "Oven 2");
```

Tasks refer to an ICD by key. They continue to work after a rename, and they do not need a redeploy.

### Rename messages and fields

Open the ICD, select the message, and change its **Name**. To rename a field, change the **Name** in its line of the fields table. Tasks refer to messages and fields by key, so they continue to read them.

A new field name applies only to channels that a later deploy creates. A channel that the field already writes keeps its name. A running task that reads the message shows **Redeploy**.

## Delete ICDs

> You cannot undo a delete.

**Console**

Select one or more ICDs in the **ICDs** toolbar. Right-click the selection, select **Delete**, and confirm.

**Python**

```python
client.icds.delete(oven.key)
client.icds.delete([oven.key, pump.key])
```

**TypeScript**

```typescript
await client.icds.delete(oven.key);
await client.icds.delete([oven.key, pump.key]);
```

You cannot delete an ICD that a task uses. Synnax refuses the delete, and the error names the task. Remove the entries that use the ICD from the task, or delete the task, then delete the ICD.

### Remove messages and fields

Open the ICD. To remove messages, select them, right-click, and select **Remove**. To remove a field, click at the end of its line in the fields table.

A task that reads a removed message shows “Message not found” in place of the message, and it does not deploy. Remove that message from the task to deploy it again.

When you open a task, the Console drops the binding of each removed field. After you deploy the task again, the channel of that field gets no new data. A task that code configures with a binding of a removed field does not deploy, and the error says that the field does not exist in the message.
