Report a problem or request a feature from your AI
On this page
When something in Pennyweight fails, or you want it to do something it can't, tell your AI. It can send a bug report or a feature request to the Pennyweight team, and you see exactly what will be sent before it goes. You need your AI connected first: see connect your AI.
Bug report or feature request
- Bug report. A tool failed, data looks wrong, or the app misbehaved.
- Feature request. You tried to do something Pennyweight doesn't support.
Your AI may bring it up first. When a tool fails unexpectedly, or you ask for something Pennyweight can't do, Pennyweight tells your AI which of the two to offer. It also asks your AI to offer once and to ask you before sending anything.
How to do it
- Tell your AI what went wrong, or what you wanted to do. Plain words are enough.
- Your AI drafts the report and asks Pennyweight for a preview. The preview is the exact text the team would receive, after Pennyweight removes financial details.
- Read the preview. Ask your AI to change anything you don't want sent.
- Say yes. Your AI sends it and tells you it went through.
That didn't work — show me what you'd send the Pennyweight team
Draft a feature request about moving transactions between ledgers and show it to me first
How do I send a bug report or a feature request to the Pennyweight team? Just explain, don't draft or send anything.
If your request is about moving transactions between ledgers, read move a transaction between ledgers first for what works today.
What you'll see
Your AI shows you the preview and asks for your OK. Removed details appear as placeholders such as <CARD> or $<AMOUNT>, and Pennyweight tells your AI which kinds it removed. A bug report needs a one-line summary and a description; it can also say what you expected, what happened instead, and the steps to reproduce it. A feature request needs what you were trying to do, what stopped you, and what you'd like to happen.
After you approve, your AI confirms the report was sent. If you already sent the same report and it's still open, Pennyweight adds to the count on that report instead of filing a second one.
What gets removed
Before the preview is built, Pennyweight removes card numbers, bank account and routing numbers, Social Security numbers, IBANs, crypto wallet addresses, email addresses, phone numbers, dollar amounts and Pennyweight's internal ids. The report doesn't carry your user id or workspace id. Pennyweight stores an anonymous reference instead.
Good to know
- Names aren't removed. Personal names and merchant names are not caught automatically, so check the preview before you approve it.
- Reports aren't encrypted with your key. The team has to read them, so they are stored as plain text, apart from your encrypted data.
- No status updates. Your AI gets one confirmation when the report is sent. It has no way to look up the report's status later.
- 10 per hour. Previews and sends both count, and bug reports and feature requests share the same limit. After that your AI gets a "too many" error; try again later. See too many requests.
- Approve within 15 minutes. A preview's approval expires after 15 minutes. If you change the text, your AI makes a new preview.
- Works on an expired plan. If your subscription has lapsed and your workspace is read-only, you can still send bug reports and feature requests.
- For anything else, contact support. Ask your AI to open the support page, which is pennyweight.ai/contact. See open the web app from chat. Bulk edits and imports use the same preview-then-approve step: see why your AI shows a preview.