From c4194b834585b1bd8e969a24e98c5e4511746ed9 Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Sun, 26 Apr 2026 23:39:38 -0700 Subject: [PATCH] docs(voice-call): note SecretRef support for twilio.authToken and tts.providers.*.apiKey Trace to db09f68ce5 (Support SecretRef for voice-call credentials and bundled plugin SecretInputs #72607). The reference page docs/reference/secretref-credential-surface.md listed the new entries in the same SHA, but docs/plugins/voice-call.md showed only plain-string credentials without pointing to the SecretRef surface. --- docs/plugins/voice-call.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/plugins/voice-call.md b/docs/plugins/voice-call.md index 29fbb36a16e..d6d74abe841 100644 --- a/docs/plugins/voice-call.md +++ b/docs/plugins/voice-call.md @@ -91,6 +91,10 @@ Gateway startup logs a setup-incomplete warning with the missing keys and skips starting the runtime. Commands, RPC calls, and agent tools still return the exact missing provider configuration when used. + +Voice-call credentials accept SecretRefs. `plugins.entries.voice-call.config.twilio.authToken` and `plugins.entries.voice-call.config.tts.providers.*.apiKey` resolve through the standard SecretRef surface; see [SecretRef credential surface](/reference/secretref-credential-surface). + + ```json5 { plugins: {