[Seeking Input] Goose Trust Framework 🤝🔒👥

[wendytang]

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—Goose 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.

1. The first feature we have in mind is Permission Before Tool Call (PbTC) which would ask you for permission before using any extension tool calls.
2. Second is giving you the controls in the form of GOOSE_MODES so you can customize how you often you want goose to ask for permission. The 3 settings we have so far are:

GOOSE_MODE=auto (Full file modification, extension usage, edit, create and delete files freely)
GOOSE_MODE=approve (Editing, creating, deleting files and using extensions will require human approval aka PbTC)
GOOSE_MODE=chat (Engage with the selected provider without using tools, extensions, or file modification)

📢 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?