Answer: To configure authentication for a remote subagent in Gemini CLI, add an `auth` block to your agent's frontmatter. Supported auth types are `apiKey`, `http`, `google-credentials`, and `oauth`. Status: Confirmed Entry: tool/gemini-cli/permissions-and-security/remote-subagent-authentication Revision: 1 Digest: sha256:0db05b6765070416 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:18:16Z Last changed: 2026-11-13T03:18:16Z Last verified: 2026-11-20T12:52:28Z Next check: 2026-11-21T12:52:28Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of configuration method | Add an `auth` block to your agent's frontmatter | [1] | 2026-11-20 auth type: apiKey | apiKey | [1] | 2026-11-20 auth type: http | http | [1] | 2026-11-20 auth type: google-credentials | google-credentials | [1] | 2026-11-20 auth type: oauth | oauth | [1] | 2026-11-20 default API key header name | X-API-Key | [1] | 2026-11-20 auth retry limit | 2 retries | [1] | 2026-11-20 Sources: [1] Google. "Remote Subagents". https://geminicli.com/docs/core/remote-agents.md Role: primary. Accessed: 2026-11-20T12:52:28Z Quote: "Add an `auth` block to your agent's frontmatter to configure credentials." (Supports: configuration method) Quote: "| `apiKey` | Send a static API key as an HTTP header." (Supports: auth type: apiKey) Quote: "| `http` | HTTP authentication (Bearer token, Basic credentials, or any IANA-registered scheme)." (Supports: auth type: http) Quote: "| `google-credentials` | Google Application Default Credentials (ADC). Automatically selects access or identity tokens." (Supports: auth type: google-credentials) Quote: "| `oauth` | OAuth 2.0 Authorization Code flow with PKCE. Opens a browser for interactive sign-in." (Supports: auth type: oauth) Quote: "Header name to send the key in. Default: `X-API-Key`." (Supports: default API key header name) Quote: "All auth providers automatically retry on `401` and `403` responses by re-fetching credentials (up to 2 retries)." (Supports: auth retry limit) Published: 2026-10-16T02:36:07Z Snapshot SHA-256: 8bdfde65084df86a28fa0367e820bea431e93e8f2346d2e2c3b15071f3989906 (captured 2026-11-13T03:18:16Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:18:16Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:52:28Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:52:28Z Last attempt: 2026-11-20T12:52:28Z Notes and limitations: Extracted automatically from a single official source (section "Authentication"). Related: https://latestn.com/tool/gemini-cli/permissions-and-security/restrict-tool-access How do I restrict which tools Gemini CLI users can access? https://latestn.com/tool/gemini-cli/permissions-and-security/rule-matching-priority How does Gemini CLI match policy rules and resolve conflicts using priority tiers? https://latestn.com/tool/gemini-cli/permissions-and-security/sandbox-expansion-outside-workspace How do I include files outside the workspace in the Gemini CLI sandbox? https://latestn.com/tool/gemini-cli/permissions-and-security/plan-mode-tool-restrictions What tools are restricted in Gemini CLI Plan Mode? https://latestn.com/tool/gemini-cli/permissions-and-security/plan-mode-yolo-availability Is Gemini CLI's enter_plan_mode tool available in YOLO mode? https://latestn.com/tool/gemini-cli/permissions-and-security/proxy-allowed-domains How do I restrict which domains the Gemini CLI sandbox proxy allows? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:18:16Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/gemini-cli/permissions-and-security/remote-subagent-authentication/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/gemini-cli/permissions-and-security/remote-subagent-authentication POST: https://latestn.com/dispute/tool/gemini-cli/permissions-and-security/remote-subagent-authentication with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/gemini-cli/permissions-and-security/remote-subagent-authentication?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure authentication for a remote subagent in Gemini CLI? Revision 1, last verified 2026-11-20T12:52:28Z. https://latestn.com/tool/gemini-cli/permissions-and-security/remote-subagent-authentication (accessed 2026-11-21T09:56:49Z). @misc{LatestN_tool_gemini_cli_permissions_and_security_remote_subagent_authentication_r1, title = {How do I configure authentication for a remote subagent in Gemini CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/gemini-cli/permissions-and-security/remote-subagent-authentication}}, note = {Revision 1; digest sha256:0db05b6765070416; last verified 2026-11-20T12:52:28Z; accessed 2026-11-21T09:56:49Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/gemini-cli/permissions-and-security/remote-subagent-authentication