Skip to content

docs: document conversation API max_tokens, remove dead parameters field - #5275

Merged
msfussell merged 2 commits into
dapr:v1.18from
CasperGN:feat/conversation-max-tokens-v1.18
Aug 12, 2026
Merged

docs: document conversation API max_tokens, remove dead parameters field#5275
msfussell merged 2 commits into
dapr:v1.18from
CasperGN:feat/conversation-max-tokens-v1.18

Conversation

@CasperGN

Copy link
Copy Markdown
Contributor

Thank you for helping make the Dapr documentation better!

Please follow this checklist before submitting:

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)
  • Read the contribution guide
  • Commands include options for Linux, MacOS, and Windows within tabpane
  • New file and folder names are globally unique
  • Page references use shortcodes instead of markdown or URL links
  • Images use HTML style and have alternative text
  • Places where multiple code/command options are given have tabpane

In addition, please fill out the following to help reviewers understand this pull request:

Description

Relates to dapr/dapr#10317 fixes

Issue reference

Relates to dapr/dapr#10317 fixes

The alpha2 conversation API reference advertised the parameters field
("Parameters for all custom fields") and its tool-calling example even
showed passing max_tokens through it, but the runtime never read the
field, so those examples silently did nothing (dapr/dapr#10317).
Now that dapr 1.19 adds a first-class maxTokens request field and every
conversation component supports a maxTokens metadata default:
- Document maxTokens in the request body table (provider mapping,
precedence over the component default, and the length finish reason).
- Drop the parameters field from the table and both request examples;
the model override in the tool-calling example moves to metadata,
which is the functional mechanism.
- Add the maxTokens spec metadata row to anthropic, aws-bedrock,
googleai, hugging-face, mistral, ollama, and openai; refresh the
deepseek wording to the new default-plus-override semantics; document
echo's word-based cap for local testing.
Signed-off-by: Casper Nielsen <casper@diagrid.io>
# Conflicts:
#	daprdocs/content/en/reference/api/conversation_api.md
@CasperGN
CasperGN requested review from a team as code ownersAugust 4, 2026 09:38
@CasperGNCasperGN added the waiting-on-code-pr The code PR needs to be merged before the docs are updated label Aug 5, 2026
Signed-off-by: Casper Nielsen <casper@diagrid.io>

@sicoylesicoyle left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thank you!

@msfussell
msfussell merged commit f337722 into dapr:v1.18Aug 12, 2026
7 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-on-code-prThe code PR needs to be merged before the docs are updated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@CasperGN@sicoyle@msfussell