Feature requests and contributing

Feature requests and contributing

claude-jam is alpha and built by one person, in the evenings. The fastest way to get a feature is to help finish it: most gaps are in the roadmap and open for a PR. Here is how to ask, and how to help.

Request a feature

1. Search the open requests first. If your idea is there, add a 👍 and a comment with your use case.
2. Otherwise open a feature request. Say what you're trying to do and where claude-jam gets in the way; that matters more than the exact feature.
3. Bugs go through the bug report instead.

Ko-fi supporters go first

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.

Contribute code

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.

What to expect

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.