CONTACT / CLEAR ROUTING
Send each request to the place that can act on it.
GoClaw does not use a public form that collects sensitive information. Choose the channel by request type and always remove API keys, verification codes, and user content.
Product access and feedback
Open an issue with the use case, expected capacity, and region. Never attach provider credentials.GitHub Issues ↗
Runtime and integration
Include reproduction steps, a non-sensitive request ID, error code, and redacted time range. CLI doctor and the docs cover initial diagnosis.Open documentation
Route security separately
Do not disclose an unpatched vulnerability in a public issue. Read the security and responsible disclosure page and provide only the minimum necessary evidence.Security and disclosure
Provider and research work
Provider proposals should identify API documentation, region, billing boundaries, lifecycle capability, and an available test environment. Public references may be attached to an issue.GitHub Issues ↗View roadmap