-
Notifications
You must be signed in to change notification settings - Fork 46
AIT threading feature documentation #3076
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.
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
base: AIT-129-AIT-Docs-release-branch
Are you sure you want to change the base?
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
aebe2c1 to
ea0ac8d
Compare
1fca0f7 to
6c00e62
Compare
ait/features: chain of thought Documents patterns for exposing reasoning output from models along with final output.
6c00e62 to
3990c2b
Compare
|
Following discussions, I've updated this with an approach oriented around chain of thought, exposing both an inline and threading based approach according to the desired UX. cc @paddybyers |
| // Derive reasoning channel name from responseId and | ||
| // use rewind to retrieve historical reasoning | ||
| const reasoningChannel = realtime.channels.get(`{{RANDOM_CHANNEL_NAME}}:${responseId}`, { | ||
| params: { rewind: '2m' } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is 2m enough in general?
AIT-213