Styx went open source on 9 October (Apache-2.0). 'Contributions welcome' in a README tends to get nothing, so I tried to make the first step small and specific instead.
There are two self-contained ways in: add support for another coding agent, or add another deploy target. Each has a guide with a worked example and a checklist. Matching issues are labelled 'good first issue': Aider, Goose and Amp for agents, and targets such as Netlify. The repo's CLAUDE.md is written for coding agents and people alike, so the conventions live in one file.
I also promised that new issues and pull requests get a first reply within two working days. A pull request nobody answers is a worse experience than none, so that one is for the sender's sake.
A contributor has now sent a draft Cloudflare adapter. They'd found that the way the app hands out credentials today can't limit a broad Wrangler token to one account, one Worker and one command. So the draft adds the groundwork (account and Worker selection, read-only Worker discovery, a command classifier) and keeps Cloudflare switched off until that's solved.
What I'd tell anyone else: pick two entry points, write them as if for a stranger, and answer fast.
What made you send your first pull request to a project you didn't know? And what put you off the ones you skipped?
Top comments (0)