Skip to content

fix typo #22

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

Merged
ChengZhang-98 merged 1 commit into from
Feb 19, 2026
Merged

fix typo #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion docs/control/learn/session_id.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ to continue an existing multi-turn session.

Here are {==**the only two scenarios where you have to manually set session IDs**==}:

1. For Sequrity Client, if you want to start a new session, you show explicitly set the `session_id` parameter to `None` in [`chat.create` method][sequrity.control.resources.chat.ChatResource.create], [`messages.create` method][sequrity.control.resources.messages.MessagesResource.create], etc.
1. For Sequrity Client, if you want to start a new session, you need to explicitly set the `session_id` parameter to `None` in [`chat.create` method][sequrity.control.resources.chat.ChatResource.create], [`messages.create` method][sequrity.control.resources.messages.MessagesResource.create], etc.
2. For both REST API and Sequrity Client, if the request messages you send do not contain any tool result messages from previous interactions.

For example, the response of the first turn is only a policy violation message without any tool calls, and you want to continue the session for the second turn, then you need to manually set the session ID for the second turn.