Use this guide when installation, a task or a documentation page does not behave as expected. You can ask for help without a private source checkout. Start with Getting started to run a released package; Authorized development is for people with source access.
Choose a route
For a product problem or documentation correction, use the CodePros support portal . It opens a customer login; use the account and support arrangement supplied to your organization. The official CodePros contact page publishes the support routes and a general contact path for access inquiries.
If you cannot sign in, use that contact page or your existing CodePros account contact. Do not assume that a public guide grants a license, source access or an account. See Licensing and access before requesting a package or repository permission. APIC and the public example repositories keep their separate licenses.
These destinations were checked on 2026-10-26 (UTC): the contact page loaded and the portal opened its customer-login route. No account sign-in or support submission was exercised. Availability and your organization’s support terms can differ.
Prepare a small report
Check the version actually on your path:
sonny version
Keep the relevant error and the page or command you followed. Use this template for a product problem or documentation correction:
Summary:
Sonny version:
Operating system and architecture:
Client and client version:
Documentation page URL and section:
Steps to reproduce with non-sensitive sample input:
Exact command or action, with secrets removed:
Expected result:
Actual result and relevant redacted error:
Frequency and impact:
Include only the information needed to reproduce the issue. Remove API keys, tokens, passwords, authorization headers and private conversation content. Review screenshots for account details and unrelated material. Do not attach a session database, an entire configuration directory or a full trace by default. Logs and tool output can contain prompts, retrieved material and file paths even when no credential is obvious. Agree on a secure channel and scope if support needs more.
Review before submitting
Confirm the destination, audience, exact text and attachments before sending. Submitting creates an external support record. This guide does not send anything or authorize a tool to submit on your behalf. Keep the returned ticket identifier. If submission times out, check for an existing record before retrying.
For a suspected security issue, avoid public posts with exploit details or private data. Use your established secure support route, or ask through the official contact page how to provide a confidential report before uploading details.
Continue your work
Use Troubleshooting for a matching symptom and its release-specific checks. Stop on an unexplained policy refusal; a support request does not authorize disabling the policy. When a fix or corrected guide arrives, repeat the smallest failing step and compare the result with your report.
Developers with authorized access should follow the repository’s current contributor policy. Public learning, commercial access and source development are separate paths; reporting a documentation problem does not require building Sonny.