From 7b72e902a3a58014270af91165fef5f4dfa17c2c Mon Sep 17 00:00:00 2001 From: Abhijay Jain Date: Tue, 29 Sep 2026 01:31:47 +0000 Subject: [PATCH] docs: warn about keyring hang in unattended ACP environments (#12173) --- documentation/docs/guides/goose-cli-commands.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/documentation/docs/guides/goose-cli-commands.md b/documentation/docs/guides/goose-cli-commands.md index 92c3f8e6f..22b631966 100644 --- a/documentation/docs/guides/goose-cli-commands.md +++ b/documentation/docs/guides/goose-cli-commands.md @@ -716,6 +716,16 @@ goose acp This command is automatically invoked by ACP-compatible clients and is not typically run directly by users. The client manages the lifecycle of the `goose acp` process. See [Using goose in ACP Clients](/docs/gdk/acp) for details. ::: +:::warning Unattended environments +goose uses the system keyring by default. On macOS, reading a credential may display a Keychain authorization prompt. If your ACP client runs goose without a user available to respond, keyring access can block indefinitely. + +Disable keyring access for that process and provide provider credentials through environment variables: + +```bash +GOOSE_DISABLE_KEYRING=1 OPENAI_API_KEY='...' goose acp +``` +::: + --- #### serve [options]