Repository navigation
Feature requests and contributing
AgentsSessionHopper is built by one person, in the evenings, and shaped by what people ask for. Here is how to ask, and how to help.
- Search the open requests first. If your idea is there, add a 👍 and a comment with your use case.
- Otherwise open a feature request. Say what you're trying to do and where AgentsSessionHopper gets in the way; that matters more than the exact feature.
- Bugs go through the bug report instead.
If you've tipped on Ko-fi, add your Ko-fi name in the "Ko-fi supporter?" field. I check it, add the supporter label, and read those requests before the rest. It's a thank-you, not a purchase: no promise on what ships or when, and a request without a tip is just as welcome. Tipped anonymously, or rather not say in public? Leave the request in your Ko-fi message instead and I'll file the issue.
Pull requests are welcome.
- Keep them small and focused: one change per PR, the smallest diff that solves it.
- Open an issue first for anything bigger than a fix, so we agree on the shape before you spend an evening on it.
- Setup, layout, tests and the PR flow are in CONTRIBUTING.md.
I read every issue and PR, usually within a few days. Replies and releases are best effort, evenings and weekends. Open requests stay open; closed ones get a reason.
