AgentFixboard
Fixed (verified)Last checked Goose#config#security

A malformed GOOSE_MODE silently selects the most permissive mode

When GOOSE_MODE is a typo or any token that does not parse, several ACP adapters keep going in Auto with no error. Auto is their most permissive mapping. The linked issue does not give a thrown error string for those adapters.

From GitHub

aaif-goose/goose

IssuePull request

Difficulty
Easy
Time
~5 min
Steps
2
Fixed in
v1.55.0
Last checked

Verified fix: PR #12846 merged on . Fixed in v1.55.0 (first published release whose tag contains the merge commit). Last checked .

Symptom

When GOOSE_MODE is a typo or any token that does not parse, several ACP adapters keep going in Auto with no error. Auto is their most permissive mapping. The linked issue does not give a thrown error string for those adapters.

Evidence what you'll see

  • Setting GOOSE_MODE=aut and starting a session raises no error. The adapter is launched in its most permissive mode (session/set_mode / session/set_config_option shows bypassPermissions on one of them).
  • Those adapters resolved the mode with get_goose_mode().unwrap_or(GooseMode::Auto).
  • One other ACP adapter already failed closed through the strict accessor and propagated a parse error for the same typo.

Why it happens

A missing or unreadable value should default to Auto. A malformed value was treated the same way. Pull request 12846 fails when GOOSE_MODE is malformed for those adapters, keeps Auto only when the setting is absent, and shares the mode resolver.

Affected versions

ACP adapters that used unwrap_or(GooseMode::Auto) for a malformed GOOSE_MODE. The linked issue does not name a Goose release tag for the original report beyond those adapters.

Fix steps

0 of 2 done

Your check marks stay in this browser only.

How to check it worked

  • Starting a session with GOOSE_MODE=aut fails instead of continuing in Auto. An unset GOOSE_MODE still defaults to Auto.

If it still fails

  • The linked issue does not describe a silent Auto fallback on v1.55.0. An absent setting still selects Auto by design.

Sources and credit

Summarized in our own words from these public reports. Credit goes to their authors.

Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change

Hit an error we don't cover? Submit it