> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rename workspace

> Change the workspace display name with a concurrent-edit guard.

`rename_workspace`

Change the workspace display name with a concurrent-edit guard. Requires an unrestricted owner or administrator.

<Note>Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.</Note>

| Access           | Behavior                                                   |
| ---------------- | ---------------------------------------------------------- |
| `projects:write` | Writes or admits work; can change or remove existing state |

This operation changes saved state. Review its inputs and retry behavior before calling.

## Example request

Connect through [MCP](/guides/connect-mcp), [CLI](/guides/connect-cli), or [HTTP](/guides/connect-http). Replace example identifiers with records from your workspace.

<CodeGroup>
  ```json MCP theme={null}
  {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "rename_workspace",
      "arguments": {
        "name": "Example workspace",
        "expectedName": "Workspace"
      }
    }
  }
  ```

  ```bash CLI theme={null}
  agentlinkops call rename_workspace --args '{"name":"Example workspace","expectedName":"Workspace"}'
  ```

  ```bash HTTP theme={null}
  curl "$AGENTLINKOPS_API_URL/v1/commands/rename_workspace" \
    -H "Authorization: Bearer $AGENTLINKOPS_API_KEY" \
    -H 'Content-Type: application/json' \
    --data '{"name":"Example workspace","expectedName":"Workspace"}'
  ```
</CodeGroup>

## Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in `structuredContent` and in a text content block; generic HTTP and CLI return the JSON result directly.

```json theme={null}
{
  "id": "ws_example",
  "name": "Example workspace"
}
```

## Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

| Field          | Type   | Presence | Meaning and constraints                                                                                       |
| -------------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------- |
| `name`         | string | Required | Human-readable name for the resource being created or updated. minLength: 1; maxLength: 200                   |
| `expectedName` | string | Required | The expected name value; allowed values and bounds are specified in this schema. minLength: 1; maxLength: 200 |

### Validation and omitted values

expectedName must equal the current workspace name; a mismatch or a change of access returns SETTINGS\_CONFLICT and nothing is written. Requires an owner or administrator with workspace-wide access.

## Output fields

Fields inside optional or nullable parents apply only when that parent exists. [Common schema conventions](/reference/schemas) explain evidence states, empty lists and extensions.

| Field  | Type   | Presence | Meaning and constraints                        |
| ------ | ------ | -------- | ---------------------------------------------- |
| `id`   | string | Required | Resource identifier returned by the operation. |
| `name` | string | Required |                                                |

[Download input schema](/schemas/rename_workspace.input.json) · [Download output schema](/schemas/rename_workspace.output.json)

## Errors and retries

This command is not annotated idempotent. After a timeout, inspect existing state before repeating a write.

See [error recovery](/reference/errors) for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

## HTTP resource routes

This operation has no separate resource alias. Use its generic command route in a matching environment.

## Continue

[get\_workspace](/reference/commands/get_workspace)

Follow the [related workflow](/guides/connect-http), inspect [capability status](/capability-status), or return to the [command index](/reference/index).