Sending feedback
Plexus has a Feedback button in the app bar, next to the search field. Use it to tell us a bug, an idea, or anything else — it reaches the team directly, with no account and no issue tracker in the way.
Because Plexus is local-first, this is the one place in the app where something you made can leave your machine. The dialog is built around showing you exactly what that is: nothing is sent until you press Send, and nothing is sent that the dialog did not put in front of you first.
Writing a report
- Click Feedback in the app bar.
- Pick Bug, Idea or Something else — it only decides which pile the report lands in.
- Write your message. Anything up to 4,000 characters.
- Optionally add your email address. It is only used to reply to you. Leave it blank and the report is anonymous — we simply have no way to answer it.
- Press Send feedback.
Attaching a screenshot
Press Attach screenshot and Plexus draws a picture of its own window. Nothing is captured before you press it, and you see the image before you send — with a Remove button if you change your mind.
It is a picture of the Plexus window only, drawn by Plexus from its own interface rather than captured from your screen. It cannot contain another application, a second monitor, an overlay, or anything behind the window — and Plexus never asks macOS for screen-recording permission. It can of course contain whatever code and file names were on screen inside Plexus, which is why you get to look at it first.
If the drawing fails on your system, the dialog offers Choose an image… instead, so you can attach a screenshot you took yourself.
Attaching diagnostic logs
Include diagnostic logs is on by default. It attaches the trail Plexus keeps of what it was doing — which sessions started and stopped, how long each stage took, and where anything went wrong.
Press Preview what's included to read the exact text that will be uploaded. That preview is not a summary; it is the bytes.
Passwords, tokens and API keys are blanked out automatically, and your home folder and username are replaced. The log deliberately keeps repository paths, branch names, worktree folder names, session ids and timings — those are what make it useful for finding your bug. Read the preview before sending if any of that is sensitive, or switch the toggle off.
If diagnostic logging is off
Diagnostic logging (Settings → Advanced) is off by default, so most of the time there is no log file to send. Plexus says so, and still attaches the activity trail it keeps in memory — which is usually enough on its own.
The dialog also offers to turn diagnostic logging on. That records much more detail, but it starts from the moment you turn it on — it cannot fill in the problem you are writing about. Turn it on, reproduce the problem, then send a second report.
Deleting a report you sent
Every report that goes through comes back with a reference code like PLX-7Q4M2-K3B9F, and Plexus keeps it so you can find it later. Email that code to timo@codedwords.com and we delete the report and everything attached to it.
You do not have to ask. Screenshots and diagnostic logs are deleted automatically after 90 days, and the message itself after 12 months.
How long logs stay on your machine
Separately from anything you send us, Plexus trims plexus-diag.log on your own disk each time it starts, keeping the last 7 days. You can change that — or switch it off entirely — with Delete diagnostic logs after (days) under Settings → Advanced; 0 keeps them forever.
What we do with it
Reports are stored in the European Union and read by us. They are not used for advertising, not fed to an AI model, and not shared or sold. The full detail — what is always sent, what is only sent if you choose it, and what never is — is in the Privacy Policy.