Report a bug

Mail bugs@rochet.vnsf.xyz. There is no tracker to sign up for and no account to make.

What to include

The two commands below answer most of what I would otherwise have to ask you, so paste both if you can. Everything else is what you were doing.

rochet --version
rochet doctor

What you did — enough to try it here. “Landed a workspace with uncommitted changes” is plenty; a full transcript is not needed.
What happened, and what you expected instead. These are two different sentences more often than they look.
Which half — the browser window, or the terminal running rochet. If the window went blank or a panel showed an error, the browser console usually has the real message.
Anything the daemon printed around the time it went wrong.

Please don’t send

Your token, or any URL containing one. rochet url and the address in your browser both carry it, and it is the only thing standing between someone who can reach your daemon and an agent running in your repositories. If you think you have already pasted one somewhere, rochet rotate-token issues a new one and invalidates the old.

Beyond that, send only what you are comfortable sending. Repository contents, prompts and file paths are yours, and a report is almost always reproducible without them — if I need something specific I will ask.

Security problems

Mail the same address and say so in the subject line. The daemon is a network service and is written as one, so anything that gets past the token, reaches beyond loopback, or lets a page in another origin talk to it is worth telling me about. Please give me a chance to ship a fix before writing it up publicly.

Feature requests

Same address, and worth sending — but know that Rochet is one person’s project and the answer is often “not soon”. The front page is honest about where it currently stands.