Skip to content

docs: document custom title generation prompts #741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
DevinVinson wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

docs: document custom title generation prompts #741

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5b7e891
docs: document custom title generation prompts
DevinVinson Aug 20, 2026
d751eb5
docs: use renamed title prompt field
DevinVinson Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions sdk/arch/agent-server.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,6 +123,27 @@ conversation.close()

If the server was started without `OH_SESSION_API_KEYS_0`, remove the `api_key=...` argument.

## Customize Conversation Title Generation

When creating a conversation through `POST /api/conversations`, set
`prompt` to replace the default user prompt used for automatic
title generation. The value can contain these placeholders:

- `{conversation_content}` - The first user message, truncated to 1,000 characters.
- `{max_length}` - The maximum generated title length.

```json
{
"autotitle": true,
"prompt": "Create a title under {max_length} characters for: {conversation_content}"
}
```

If `{conversation_content}` is not present, the Agent Server appends the first
user message to the custom prompt. Empty or omitted values keep the default
title-generation behavior. Prompts can contain up to 2,000 characters and are
stored with the conversation in `meta.json`.

## Expose It Safely

If another service runs on the same machine, keep the server bound to `127.0.0.1` and let that service connect locally.
Expand Down
Loading