Good Feedback Names the Product and Outcome
Write feedback that maintainers and agents can triage quickly.
V
Written By Val AlexanderLast updated about 2 hours ago
Good feedback helps maintainers understand the product, the user-visible outcome, and the next action.
Include These Details
Name the product surface: CastCodes, Coven, Coven Code, Coven Mobile, or OpenCoven Feedback.
Describe the outcome you want. For bugs, describe what happened and what you expected.
Add reproduction steps when they are safe to share publicly.
Link public GitHub issues, releases, docs, or discussion when they add useful evidence.
Keep Private Context Out
Do not paste secrets, tokens, private URLs, raw logs with local paths, customer-private data, or unreleased sensitive security details. Summarize the public symptom instead.
Was this helpful?
Your feedback shapes what we write next.