Troubleshooting
Report a bug
Found something broken? Here's the fastest way to tell us.
Beta software has rough edges. When you hit one, a good report gets it fixed faster than a vague one.
Where to report
Bugs go to scan.plccode.ai — our tracker. You can also reach it from the Report a bug link in the footer of any docs page.
What makes a report useful
You don't need a formal write-up. Just enough that someone can reproduce it:
- What you did — the steps, in order.
- What you expected — what should have happened.
- What actually happened — the wrong result, error text, or a screenshot.
- Where — which project, page, or routine, if it's specific.
A screenshot of the actual screen beats a paragraph describing it. If there's an error message, copy the exact text — even the part that looks like gibberish.
Security issues
If you've found something that looks like a security problem, don't post the details in a public report. Flag it as security-sensitive in the tracker, or contact the team directly, so it can be handled quietly.