Reporting Bugs and Requesting Features

How to send feedback, report bugs, or request features directly from your Coppermind session.

Overview#

If you run into a problem or have an idea for something Coppermind should do differently, you can report it without leaving your conversation. Coppermind sends your feedback directly to the product team so they can triage it.

This is different from corrections (which teach Coppermind your preferences). Feedback goes to the humans building the product. Corrections stay in your memory and change how Coppermind behaves for you.

When to Use This#

• Something broke or behaved unexpectedly
• A tool returned an error you did not expect
• You want a feature that does not exist yet
• You have general feedback about the experience

How to Send Feedback#

Just describe the problem or idea in your own words:

"Report a bug: meeting prep crashed when I had no meetings on the calendar"

"Request a feature: I wish I could tag memories by project, not just by client"

"Send feedback: the onboarding flow was smooth, but the API key step was confusing"

Coppermind auto-categorizes your message as a bug, feature request, or general feedback based on what you said. You do not need to specify a category unless you want to.

What Happens Next#

1. Your feedback is sent to the Coppermind product team as an email.
2. You get a confirmation with a ticket ID for reference.
3. The team triages and responds based on severity and demand.

There is no back-and-forth in the tool itself. If the team needs more context, they will reach out to you directly.

Rate Limits#

You can send up to 5 feedback messages per hour. This prevents accidental floods and keeps the feedback channel useful.

Tips#

• Be specific about what happened. "Search is broken" is hard to act on. "When I search for 'Q2 budget' with Acme active, it returns memories from BetaCorp" gives the team something to investigate.
• Include the client mind if relevant. Mentioning which client was active when the issue occurred helps reproduce the problem.
• Don't use this for corrections. If Coppermind used the wrong tone or format, store a correction instead (see the Corrections and Feedback guide). Corrections fix your experience immediately. Bug reports go to a queue.
• Feature requests are welcome. Even if the idea seems small, the team tracks patterns. If multiple CMOs ask for the same thing, it moves up the priority list.