Replies: 2 comments
|
feedback from Andrew F.
|
0 replies
|
We've implemented Goose Modes and Tool Permissions, so I think it's safe to close this discussion. Please reopen if there's more to add to this discussion. |
0 replies
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.
Uh oh!
There was an error while loading. Please reload this page.
Goose Trust Framework 馃馃敀馃懃
馃憢 Block team here - we wanted to share an initiative that we're starting and would like to hear from you whether Goose behaved in a way that met or didn't meet your expectations.
Premise
After the initial v1.0 launch, we've been hearing from developers that Goose sometimes goes off the rails and makes a flurry of changes calling tools.
"I wanted to create a new Java annotation.. Goose then decided it needed to clean up the files.. this breaks trust鈥擥oose should ask for confirmation before creating or modifying files"
"..Goose has problems editing files, like it will delete all of the file before and after the part it's working on and replace them with "rest of file here" tombstones. Anyone have ways to fix it?"
How we're thinking about it
We don't want you to lose trust using goose, so we want to put up a framework for trust.
馃摙 Call to Action
What are times that goose behaved in a way that met or didn't meet your expectations?
Can you describe that instance and what you were using goose for? How do you use goose day-to-day?
Would you use GOOSE_MODES and does the feature make sense to you?
All reactions