warp
Applicationwarpdotdev/warp
Warp is an agentic development environment built on the terminal.
Overview
Warp is an agentic development environment that enhances the terminal with AI-powered features. It supports built-in coding agents and third-party CLI agents. Built in Rust, it offers a modern, fast terminal experience with native macOS and Linux support.
README Preview
\n \n\n \n\n \n \n \n\n\n\n Website\n ·\n Code\n ·\n Agents\n ·\n Terminal\n ·\n Drive\n ·\n Docs\n ·\n How Warp Works\n\n\n> [!NOTE]\n> OpenAI is the founding sponsor of the new, open-source Warp repository, and the new agentic management workflows are powered by GPT models.\n\n\n\n## About\n\n[Warp](https://www.warp.dev) is an agentic development environment, born out of the terminal. Use Warp's built-in coding agent, or bring your own CLI agent (Claude Code, Codex, Gemini CLI, and others).\n\n## Installation\n\nYou can [download Warp](https://www.warp.dev/download) and [read our docs](https://docs.warp.dev/) for platform-specific instructions.\n\n## Warp Contributions Overview Dashboard\n\nExplore [build.warp.dev](https://build.warp.dev) to:\n- Watch thousands of Oz agents triage issues, write specs, implement changes, and review PRs\n- View top contributors and in-flight features\n- Track your own issues with GitHub sign-in\n- Click into active agent sessions in a web-compiled Warp terminal\n\n## Oz for OSS\n\nMaintaining a popular open-source project? [Apply for Oz credits](https://tally.so/r/LZWxqG) to explore [Oz for OSS](https://github.com/warpdotdev/oz-for-oss).\n\nOz for OSS is our partner program for bringing the same agentic open-source management workflows used in this repository to select partner repositories. We work directly with maintainers to implement workflows for issue triage, PR review, community management, and contributor coordination in a way that fits each project.\n\n## Licensing\n\nWarp's UI framework (the `warpui_core` and `warpui` crates) are licensed under the [MIT license](LICENSE-MIT).\n\nThe rest of the code in this repository is licensed under the [AGPL v3](LICENSE-AGPL).\n\n## Open Source & Contributing\n\nWarp's client codebase is open source and lives in this repository. We welcome community contributions and have designed a lightweight workflow to help new contributors get started. For the full con
FAQ (4)
TroubleshootingHow to fix path tab-completion not working for Dart/Flutter commands in Warp terminal?
This was a regression in Warp's completion fallback path introduced around v0.2026.09.23. Update Warp to v0.2026.09.30.08.29.stable_01 or later, which contains the fix. As a temporary workaround on the affected version, go to Settings > Features > Terminal Input and disable "Native shell completions". Note the bug only affected command-specific completions (e.g., dart path/t + Tab); general path completion with commands like ls or cat still worked.
TroubleshootingHow do I fix Cmd-T opening an Agent tab instead of a Terminal tab in Warp after changing the keyboard shortcut?
Set Warp's default session mode to Terminal. Open Settings, search for **"Default mode for new sessions"**, and change it from **Agent** to **Terminal**. After that, Cmd-T will open a new terminal tab again, even if the New Agent Tab shortcut has been removed or remapped. This is a workaround for the macOS menu-routing issue in Warp v0.2026.05.27.15.44.stable_01 and later.
TroubleshootingWhy does Warp terminal abort when running a Python script to scan Bluetooth devices on macOS?
This is caused by Warp lacking the required Bluetooth permission. Follow these steps to manually grant access:
1. Open System Settings > Privacy & Security > Bluetooth.
2. Click the '+' button and add Warp (if not listed, drag Warp from Applications into the list).
3. Ensure Warp is enabled. This works around the missing NSBluetoothAlwaysUsageDescription entitlement in Warp's Info.plist. The permanent fix requires the Warp developers to add the entitlement, as tracked in issue #6675.
TroubleshootingWhy does kubectl --context tab completion show files instead of Kubernetes contexts in Warp terminal?
This is a known bug in Warp where completions for kubectl flags like --context and --cluster fall back to file listing instead of showing contexts from your kubeconfig. There is no permanent fix yet, but you can work around it by running fish or zsh in a subshell (just type fish or zsh and press Enter), which restores the native shell completions for kubectl. Track the issue on Warp's GitHub (issue #5186) for updates.