Contributing to Warp

Warp's client is open source under AGPL v3 at warpdotdev/warp, 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 Warp user. For the full code contribution flow, see CONTRIBUTING.md.

Ways you can contribute

• Report a bug or request a feature - File an issue in warpdotdev/warp, or explore existing issues to comment on or upvote ones that matter to you. Clear reproductions and upvotes help Warp prioritize.
• Contribute code - Claim any issue labeled ready-to-spec or ready-to-implement, then open a spec or code PR. 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 warpdotdev/themes.
• Share a workflow - Add reusable command patterns to warpdotdev/workflows. Merged workflows ship to every Warp user.
• Publish Warp Drive objects - Share Workflows, Notebooks, Rules, and Prompts publicly from Warp Drive.
• Find an issue to pick up - Browse Warp's live agent dashboard, which shows the work Warp's agents are tackling across warpdotdev/warp. 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 Warp community Slack, and join conversations in GitHub Discussions.

Send feedback and bug reports

The fastest way to file a bug or feature request is the /feedback slash command inside Warp. It drafts and files a GitHub issue without leaving the terminal.

Other channels:

• File an issue directly in warpdotdev/warp.
• 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 Warp's Help menu.
• Email [email protected] for privacy questions.

For logs, crash reports, CPU samples, and AI conversation IDs, see Sending feedback and logs.

Reporting a security vulnerability

If you believe you've found a security vulnerability, follow responsible disclosure practices and do not open a public GitHub issue or pull request, as this could expose the vulnerability before a fix is available. Include reproduction steps, impact, and any proof of concept when you report it through one of the following channels:

• Email: [email protected]
• GitHub Security Advisory: Open a private advisory

We will acknowledge your report promptly and work with you to understand and resolve the issue as quickly as possible. Full guidance is in SECURITY.md.

Code of conduct

Warp's open source repositories follow the Contributor Covenant v2.1. Read the full text, or report violations to [email protected].