Rename app
renameProjectRename one owned project — the Settings page’s own Save, for the name alone; it is the fix for a name chosen badly when the code arrived. Nothing else changes: the code, the live address, the deployments, the database and every domain connection stay exactly as they are, and so do the environment settings, except that before the app’s first deploy a public setting holding the address that deploy would give it moves to the new name’s address. That is why it needs no confirmation and takes no confirmed field. A name carrying what looks like a credential or a token is refused. The answer is the project’s settings row, as the Settings page reads it back after saving. It cannot rename another account’s project, which answers exactly as the dashboard does.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>",
"name": "<name>"
},
"name": "renameProject"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| projectId | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| source | Yes | ||
| createdAt | Yes | ||
| framework | Yes | ||
| projectId | Yes | ||
| deploymentPending | Yes |