---
title: "Set a chat's own next-step suggestion mode, or clear it to follow the user's default."
method: PUT
path: "/ai/conversations/{public_id}/suggestion-mode"
tags: ["AI Chat"]
---

# Set a chat's own next-step suggestion mode, or clear it to follow the user's default.

`PUT /ai/conversations/{public_id}/suggestion-mode`

## Request

- Base URL: `/api` (relative, and the document was published on a file host, not at the API’s origin)
- URL: `/api/ai/conversations/{public_id}/suggestion-mode`
- Auth: HTTP bearer

## Path parameters

- `public_id` string, required

## Request body

- UpdateChatSuggestionModeRequest: Set a chat's own mode, or `null` to follow the user's default.
  - `mode` 'off' | 'ask' | 'always': What happens after each answer.

## Response `200`

The chat's new setting

- ChatSuggestionSettings: A chat's next-step suggestion setting.
  - `available` boolean, required: Whether this chat can have suggestions at all. Only the assistant chat can; the other fields still describe the setting for other chats.
  - `chat_mode` 'off' | 'ask' | 'always': What happens after each answer.
  - `default_mode` 'off' | 'ask' | 'always', required: What happens after each answer.
  - `mode` 'off' | 'ask' | 'always', required: What happens after each answer.
  - `source` 'chat' | 'default', required: Where a chat's effective mode comes from.

## Other responses

- `400`: Invalid mode
- `401`: Unauthorized
- `403`: Insufficient permissions
- `404`: Conversation not found
- `409`: This chat cannot have suggestions
- `500`: Internal server error

## Changes

> 81 revisions in range; 1 not diffed.

- **2026-10-20** `79089e9f49ee`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/gotempsh/apis/temps/changes/ai/conversations/:public_id/suggestion-mode/put.md)

---

[API](https://skmtc.dev/gotempsh/apis/temps.md) · [All operations](https://skmtc.dev/gotempsh/apis/temps/llms.txt) · [OpenAPI document](https://skmtc.dev/gotempsh/apis/temps/revisions/ab6d5d19e930?raw)