You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The team has informally discussed in past how we'd like to allow Kai to run through all (or a subset of multiple issues), work to solve all the issues it is able to then stage that work in a Pull Request for a developer to access as a typical PR review.
We could see this as a literal Pull Request being created/submitted against an upstream repository,
or perhaps this is a simulate PR review experience built into the IDE where the code is staged in a branch and extra information is made available to help understand 'why' certain changes were done.
As we consider this a key part would be to produce extra contextual information from Kai to help explain why changes are being made. We imagine this would include things like the original issue that prompted the work, maybe this is an analysis issue, maybe this is a compiler error that was found from an agent, or guidance from the reflection agent...we'd want to create and capture a story of what/why Kai proceeded with the changes. Idea being that this information is presented with the final source code suggestions so that a developer can understand the reasoning/thinking Kai went through to produce the changes.
The text was updated successfully, but these errors were encountered:
The team has informally discussed in past how we'd like to allow Kai to run through all (or a subset of multiple issues), work to solve all the issues it is able to then stage that work in a Pull Request for a developer to access as a typical PR review.
We could see this as a literal Pull Request being created/submitted against an upstream repository,
or perhaps this is a simulate PR review experience built into the IDE where the code is staged in a branch and extra information is made available to help understand 'why' certain changes were done.
As we consider this a key part would be to produce extra contextual information from Kai to help explain why changes are being made. We imagine this would include things like the original issue that prompted the work, maybe this is an analysis issue, maybe this is a compiler error that was found from an agent, or guidance from the reflection agent...we'd want to create and capture a story of what/why Kai proceeded with the changes. Idea being that this information is presented with the final source code suggestions so that a developer can understand the reasoning/thinking Kai went through to produce the changes.
The text was updated successfully, but these errors were encountered: