update_chat_command
Modify an existing chat command by ID: edit its content, schedule, run limits, or activation status, leaving unspecified fields unchanged.
Instructions
Update an existing chat command by ID.
Omitted fields are left unchanged. Schedule fields (cron_schedule,
sink_configs, run_as_user, assistant_name, etc.) follow the
same partial-update semantics as the PAPI. Use clear_max_runs=True to
remove an existing run cap (MCP cannot send bare null for max_runs).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | New command name. | |
| max_runs | No | Replace the run budget (must be >= 1 when scheduling). | |
| scope_id | No | New scope ID. | |
| is_active | No | Set active/inactive. | |
| command_id | Yes | The command ID to update. | |
| scope_type | No | New scope type. | |
| description | No | New description. | |
| run_as_user | No | Replace the run-as user email. | |
| sink_configs | No | Replace delivery targets for scheduled runs. | |
| cron_schedule | No | New cron expression, or empty string to clear scheduling. | |
| assistant_name | No | Replace the persona for scheduled runs (workspace prefix optional). | |
| clear_max_runs | No | When true, remove the run budget cap (unlimited scheduled runs). | |
| workspace_name | Yes | The workspace the command belongs to (e.g. 't-oncall'). | |
| command_content | No | New markdown content. | |
| schedule_paused | No | Pause or resume the cron schedule. | |
| reset_runs_completed | No | When true, reset runs_completed to 0 (e.g. after raising max_runs). | |
| auto_approve_readonly | No | Toggle auto-approve for read-only tasks on scheduled runs. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |