-
Notifications
You must be signed in to change notification settings - Fork 114
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
feat: add reasoning effort to agent config model + support in core #9603
Conversation
95dbc9d
to
f067563
Compare
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.
ooc, what is reasoning effort ?
CREATE OR REPLACE FUNCTION perform_migration(backfilled boolean DEFAULT false) | ||
RETURNS VARCHAR AS $$ | ||
BEGIN | ||
IF NOT backfilled THEN | ||
RAISE NOTICE 'The backfill script: is required before applying this migation. If you already did it, run psql with --set=backfilled=1 argument.'; | ||
END IF; |
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.
what backfill is needed for that ?
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.
Removed, for some reason our migration generator adds all that stuff (I never want it personally)
@tdraier it's the amount of test time compute you want to use for o1 models: https://platform.openai.com/docs/api-reference/chat/create |
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.
LGTM
New agent config field! Show time!
Description
reasoningEffort
on theagent_configurations
table (optional)reasoning_effort
config oncore
LLM / Chat blocks for OAI provider (asextras
config).Risk
critical path for pretty much everything + database migration
Deploy Plan
core
(adds support for the config) and deployfront
(functionally a no-op)