Support & Community > Community
Contributing to Derp
# Contributing to Derp Derp's client is open source under [AGPL v3](https://github.com/derpdotdev/derp/blob/master/LICENSE-AGPL) at [`derpdotdev/derp`](https://github.com/derpdotdev/derp), and there's room for every kind of contribution — from a one-line bug report to a full feature PR, a new theme, or a workflow that ships to every Derp user. For the full code contribution flow, see [`CONTRIBUTING.md`](https://github.com/derpdotdev/derp/blob/master/CONTRIBUTING.md). ## Ways you can contribute * **Report a bug or request a feature** - [File an issue](https://github.com/derpdotdev/derp/issues/new/choose) in [`derpdotdev/derp`](https://github.com/derpdotdev/derp), or [explore existing issues](https://github.com/derpdotdev/derp/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) to comment on or upvote ones that matter to you. Clear reproductions and upvotes help Derp prioritize. * **Contribute code** - Claim any issue labeled `ready-to-spec` or `ready-to-implement`, then open a spec or code PR. [`CONTRIBUTING.md`](https://github.com/derpdotdev/derp/blob/master/CONTRIBUTING.md) covers the spec format, tests, `./script/presubmit`, and the PR template. * **Build a theme** - Submit a new color scheme or improve an existing one at [`derpdotdev/themes`](https://github.com/derpdotdev/themes). * **Share a workflow** - Add reusable command patterns to [`derpdotdev/workflows`](https://github.com/derpdotdev/workflows). Merged workflows ship to every Derp user. * **Publish Derp Drive objects** - Share Workflows, Notebooks, Rules, and Prompts publicly from [Derp Drive](/knowledge-and-collaboration/derp-drive/). * **Find an issue to pick up** - Browse [Derp's live agent dashboard](https://build.derp.dev), which shows the work Derp's agents are tackling across `derpdotdev/derp`. Use it to spot gaps, avoid duplicate work, and surface issues that haven't been claimed yet. * **Help others in the community** - Answer questions in the [Derp community Slack](https://go.derp.dev/join-preview), and join conversations in [GitHub Discussions](https://github.com/derpdotdev/derp/discussions). ## Send feedback and bug reports The fastest way to file a bug or feature request is the [`/feedback`](/support-and-community/troubleshooting-and-support/sending-us-feedback/#using-feedback-in-derp) slash command inside Derp. It drafts and files a GitHub issue without leaving the terminal. Other channels: * File an issue directly in [`derpdotdev/derp`](https://github.com/derpdotdev/derp/issues/new/choose). * Press `⌘+Shift+F` (macOS) or `Ctrl+Shift+F` (Windows/Linux) to open the in-app feedback dialog. On macOS, you can also use the **Send Feedback** option in Derp's Help menu. * Email [privacy@derp.dev](mailto:privacy@derp.dev) for privacy questions. For logs, crash reports, CPU samples, and AI conversation IDs, see [Sending feedback and logs](/support-and-community/troubleshooting-and-support/sending-us-feedback/). ## Reporting security issues :::danger Do not file public issues for security vulnerabilities. ::: Email [security@derp.dev](mailto:security@derp.dev) with reproduction steps, impact, and any proof of concept. We'll acknowledge receipt and coordinate a fix and disclosure. Full guidance is in [`CONTRIBUTING.md`](https://github.com/derpdotdev/derp/blob/master/CONTRIBUTING.md#reporting-security-issues). ## Code of conduct Derp's open source repositories follow the [Contributor Covenant](https://www.contributor-covenant.org/) v2.1. Read the [full text](https://github.com/derpdotdev/derp/blob/master/CODE_OF_CONDUCT.md), or report violations to [derp-coc@derp.dev](mailto:derp-coc@derp.dev).Contribute to Derp's open source client by filing issues, opening pull requests, building themes, and sharing workflows.
Derp's client is open source under AGPL v3 at derpdotdev/derp, and there's room for every kind of contribution — from a one-line bug report to a full feature PR, a new theme, or a workflow that ships to every Derp user. For the full code contribution flow, see CONTRIBUTING.md.
Ways you can contribute
Section titled “Ways you can contribute”- Report a bug or request a feature - File an issue in
derpdotdev/derp, or explore existing issues to comment on or upvote ones that matter to you. Clear reproductions and upvotes help Derp prioritize. - Contribute code - Claim any issue labeled
ready-to-specorready-to-implement, then open a spec or code PR.CONTRIBUTING.mdcovers the spec format, tests,./script/presubmit, and the PR template. - Build a theme - Submit a new color scheme or improve an existing one at
derpdotdev/themes. - Share a workflow - Add reusable command patterns to
derpdotdev/workflows. Merged workflows ship to every Derp user. - Publish Derp Drive objects - Share Workflows, Notebooks, Rules, and Prompts publicly from Derp Drive.
- Find an issue to pick up - Browse Derp's live agent dashboard, which shows the work Derp's agents are tackling across
derpdotdev/derp. Use it to spot gaps, avoid duplicate work, and surface issues that haven't been claimed yet. - Help others in the community - Answer questions in the Derp community Slack, and join conversations in GitHub Discussions.
Send feedback and bug reports
Section titled “Send feedback and bug reports”The fastest way to file a bug or feature request is the /feedback slash command inside Derp. It drafts and files a GitHub issue without leaving the terminal.
Other channels:
- File an issue directly in
derpdotdev/derp. - Press
⌘+Shift+F(macOS) orCtrl+Shift+F(Windows/Linux) to open the in-app feedback dialog. On macOS, you can also use the Send Feedback option in Derp's Help menu. - Email privacy@derp.dev for privacy questions.
For logs, crash reports, CPU samples, and AI conversation IDs, see Sending feedback and logs.
Reporting security issues
Section titled “Reporting security issues”Email security@derp.dev with reproduction steps, impact, and any proof of concept. We'll acknowledge receipt and coordinate a fix and disclosure. Full guidance is in CONTRIBUTING.md.
Code of conduct
Section titled “Code of conduct”Derp's open source repositories follow the Contributor Covenant v2.1. Read the full text, or report violations to derp-coc@derp.dev.