Report a bug / request a feature
Bugs and feature requests both go to GitHub Issues. klink's release cadence is driven by real-user reports — several fixes already shipped (tool discoverability, error message wording, starter gaps) started as a single user issue, not something dreamed up behind closed doors.
- Chinese or English is fine — write whichever is more comfortable.
- The more concrete (layout scale, which RPC/MCP tool you called, expected vs. actual result, the shortest reproducible steps), the faster the fix; "it doesn't work" is hard to act on.
- If you can, paste the raw error text from
klink.statusor the failing tool — the error message itself usually already names the next step.
Questions & showing your use
Questions are just as welcome on GitHub Issues — a question is a perfectly fine issue on its own; you don't need to first decide whether it "really counts" as a bug.
- For the project overview, README, and release history, see the repository itself.
- For self-serve answers first, check the tutorials overview — most "how do I use tool X" questions are already covered by an illustrated tutorial or chat walkthrough.
- Want to show off a layout you drew or a flow you got working with klink? Open an issue for that too — screenshots and scripts welcome.
Contributing
To contribute code or docs, start with CONTRIBUTING.md in the repository — it carries the current branch, test, and commit conventions.