Originally proposed to roo regarding structured outputs #915
nikhil-swamix
started this conversation in
1. Feature requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Original> RooCodeInc/Roo-Code#5218
What specific problem does this solve?
to
effect
this will optimize context, lower noise, and models trained for tool use will skyrocket in quality. there are many obvious advantages, and unknown advantages im forecasting, (please help me brainstorm). parameter of tools and descriptions can be described inline, and json, ensures no extra keys are generated, for example xml needs a closing tag, while json only key value...
reference
https://platform.openai.com/docs/guides/structured-outputs?api-mode=chat
observations
i have used structured outputs in production, and have never disappointed me, + a nice speedup of 25% is observed as it just fills in the slots.
models are getting increasingly well, and old prompt of cline (which i believe were designed to bypass some limitations) now hampers true potential of models.
Additional context (optional)
How should this be solved? (REQUIRED if contributing, optional otherwise)
was the original proposer of 🙂, ""Enable multi-file AI processing: Modify the request handler to accept multiple files in a single request and process them together, reducing round trips."
https://www.linkedin.com/posts/nikhilswamiofficial_ai-coding-software-activity-7334746641368813568-z3ID?utm_source=share&utm_medium=member_desktop&rcm=ACoAAC9XzsUBRi1otei0-sS2j4STv4tVo5T9viY
Beta Was this translation helpful? Give feedback.
All reactions