Answer: You pass default authentication or application headers to OpenCode.make via the headers option, and you can also supply a custom fetch implementation. Each operation accepts request options as its final argument for an AbortSignal or per-request headers, except event subscriptions which use the base client's headers. Status: Confirmed Entry: tool/opencode/integrations/client-headers-requests Revision: 1 Digest: sha256:82fe4683d9150d41 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:55:34Z Last changed: 2026-11-13T03:55:34Z Last verified: 2026-11-20T13:44:22Z Next check: 2026-11-21T13:44:22Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of headers option | headers | [1] | 2026-11-20 custom fetch | custom fetch implementation | [1] | 2026-11-20 per-request options | request options | [1] | 2026-11-20 event subscriptions exception | subscriber-local cancellation | [1] | 2026-11-20 Sources: [1] opencode. "JavaScript | OpenCode". https://opencode.ai/docs/build/client/ Role: primary. Accessed: 2026-11-20T13:44:23Z Quote: "Pass default authentication or application headers to OpenCode.make with headers ." (Supports: headers option) Quote: "You can also supply a custom fetch implementation." (Supports: custom fetch) Quote: "Each operation accepts request options as its final argument for an AbortSignal or per-request headers." (Supports: per-request options) Quote: "Event subscriptions are the exception: they accept only subscriber-local cancellation and use the base client’s headers." (Supports: event subscriptions exception) Snapshot SHA-256: b57c06b169f30d263d200c3ace3e4cf3d5ed6f2a7ad4d4bd5ef01f4334d32706 (captured 2026-11-13T03:55:34Z) 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:55:34Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:44:22Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:44:22Z Last attempt: 2026-11-20T13:44:22Z Notes and limitations: Extracted automatically from a single official source (section "Headers and requests"). Related: https://latestn.com/tool/opencode/integrations/close-host-resources How do I release or close an opencode host's resources? https://latestn.com/tool/opencode/integrations/cloudflare-durable-object-sdk How do I use the opencode SDK inside a Cloudflare Durable Object? https://latestn.com/tool/opencode/integrations/cloudflare-route-outbound-requests How do I route outbound requests with the opencode Cloudflare SDK? https://latestn.com/tool/opencode/integrations/call-provider-directly How do I call an opencode Console provider directly from my own tools? https://latestn.com/tool/opencode/integrations/call-rpc How do I call an opencode plugin RPC over HTTP or from another plugin? https://latestn.com/tool/opencode/integrations/call-rpc-method How do I call an opencode RPC method over HTTP or from a plugin? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:55:34Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/opencode/integrations/client-headers-requests/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/opencode/integrations/client-headers-requests POST: https://latestn.com/dispute/tool/opencode/integrations/client-headers-requests with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/opencode/integrations/client-headers-requests?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I pass authentication headers or a custom fetch to the opencode client? Revision 1, last verified 2026-11-20T13:44:22Z. https://latestn.com/tool/opencode/integrations/client-headers-requests (accessed 2026-11-21T09:50:32Z). @misc{LatestN_tool_opencode_integrations_client_headers_requests_r1, title = {How do I pass authentication headers or a custom fetch to the opencode client?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/opencode/integrations/client-headers-requests}}, note = {Revision 1; digest sha256:82fe4683d9150d41; last verified 2026-11-20T13:44:22Z; accessed 2026-11-21T09:50:32Z} } 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/opencode/integrations/client-headers-requests