The short version.
Security issues go to the coordinated disclosure relay on the trust and safety page. Production incidents on commercial support use the phone relay below. Community bug reports and feature requests go to the public issue tracker linked from the community page. Legal and press inquiries use the topic routes in the table.
Contact routing.
Four columns, one row per topic. Pick the topic row first, then use the primary channel. The secondary channel is a fallback if the primary is unreachable.
| Topic | Primary channel | SLO | Secondary |
|---|---|---|---|
| Security disclosure | Coordinated disclosure relay on trust & safety | Acknowledged in one business day | Phone relay, only if the email relay is unreachable |
| Production incident (commercial) | Phone relay during support hours | P1 within four business hours | Private portal ticket tagged P1 |
| Community bug report | Public issue tracker from the community page | First response within three business days | Community chat rotation |
| Feature request | Public issue tracker, feature label | Triaged within two weeks | RFC draft in docs/rfc/ (for larger ideas) |
| Press and media | Press topic, routed via the contact matrix | Within three business days | Team page press contact on rotation |
| Legal notice | Mailing address (PO Box, San Francisco) | Acknowledged on receipt | Private legal relay, managed customers only |
| Sponsorship inquiry | Sponsorship topic, routed via the contact matrix | Within five business days | Pricing page contact form |
The OpenCode phone relay.
The phone relay is +1 (415) 555-0172. It is staffed during North American business hours for commercial support customers on a P1 incident. The first spoken line is the support contract reference so the responder can confirm entitlement before triage begins.
The relay is not a general-purpose contact line. It is not a sales hotline, it is not the fastest path for a community bug, and it is not the path for a security disclosure. For everything outside P1 commercial support, the channels in the routing table above are both faster and better logged. The relay records a callback if the on-call maintainer is already on another incident.
Regions outside North America can still use the relay. It accepts international calls and the on-call rotation covers the major timezones during their local working hours. Exact coverage is published on the community page. If the on-call for your region is off-rotation when you call, the relay offers a callback window and confirms it by text.
Mailing address.
Paper correspondence and legal notices go to OpenCode PO Box.
The address is OpenCode Project, PO Box 4821, San Francisco, CA 94142, USA. The PO Box is scanned twice a week and material is logged to the legal queue. Anything that requires acknowledgment receives a short written reply by the same channel it arrived on. Do not mail secrets, security reports, or live incident payloads; the disclosure relay on the trust and safety page is the right channel for any of those.
Topic-based routing, explained.
The routing table above covers the seven topics that account for almost every inquiry. A quick guide to picking the right row saves a round-trip.
If the inquiry is about a potential vulnerability in a shipped OpenCode binary, a dependency, or an adapter, that is a security disclosure. Use the trust-and-safety relay, not the phone and not the public tracker. Filing a vulnerability publicly before coordination is complete pushes other users into the weather before a patch is available, which OpenCode treats as a harm event.
If the inquiry is about a production outage on a deployment that pays for commercial support, that is an incident. Use the phone relay for P1 and the private portal for everything else. Reference the support contract on the first line so the responder can confirm entitlement and start the clock on the right SLO.
If the inquiry is "my OpenCode install did something weird" or "I want feature X," that is a community bug or feature request. Open an issue from the community page. Public discussion is the right default: the maintainer who triages the ticket is the same one who writes the fix, and the next user who hits the same symptom finds the answer by searching the tracker.
Regional channels.
OpenCode has a volunteer rotation across the major regions so the answer comes during your working day.
The Europe rotation covers CET working hours. The Asia-Pacific rotation covers JST and AEST working hours. The Latin America rotation covers BRT working hours. The community page lists the current owner for each regional shift and the chat channel where they respond. Response times outside the North American business day are best-effort and frequently shorter than the headline SLO because the regional rotation is less saturated.
What not to send through the contact page.
A short negative list saves everyone a round-trip. Do not email live secrets to any contact channel; scrub them from transcripts before you attach. Do not send NDAs to the PO Box expecting a signature by return mail; NDAs go through the commercial support onboarding. Do not file security disclosures through the press topic; they go to the coordinated disclosure relay on the trust and safety page.
If you are not sure which channel fits, pick the public issue tracker and label the issue triage. A maintainer will re-route it within a business day and close the duplicate, and everyone else who hits the same "which channel?" question can find the resolution for free. For research and academic inquiries the code.gov referral network occasionally routes users to us; those inquiries can also land in the issue tracker with a research label.
We switched our support contract from a boutique vendor to OpenCode's commercial tier last quarter. The phone relay and the written SLOs covered what our procurement team needed on paper. The actual response times have been under the headline numbers both times we have paged.
— Tevita P. Havili, Mobile Platform Lead, Folio Plaintext
Related contact pages.
Direct links into the pages that deepen each contact route.