Tidier Warp — a community fork of Warp for people who want a fast, modern terminal without the AI overlay, plus a few quality-of-life additions for keyboard-driven workflows and git review.
Status: planning / pre-alpha. Forked from
warpdotdev/warp@d0f045c0on 2026-04-29. None of the differences below are implemented yet — this README is the roadmap.
Warp is an excellent terminal. twarp aims to be a leaner, AI-free distribution of it with a few focused additions. If you want an agent in your terminal, run one yourself (e.g., claude) — but the terminal itself shouldn't be an AI.
twarp removes Warp's AI features — the agentic mode, cloud-agent surfaces, in-line AI suggestions, AI command help, anything that calls out to an LLM from inside the terminal. The terminal is the terminal.
In practice this means ripping out the agent UI, the cloud-mode codepaths, the AI command palette, and any LLM-backed completion. Telemetry that exists solely to support those features goes with them.
Build progress for all five sections below is tracked in roadmap/ROADMAP.md.
A keyboard shortcut to assign a color to the active tab — useful for visually distinguishing workflows at a glance ("red tab is prod, green tab is local").
Tentative defaults (configurable):
| Shortcut | Color |
|---|---|
⌘⌥1 |
Red |
⌘⌥2 |
Orange |
⌘⌥3 |
Yellow |
⌘⌥4 |
Green |
⌘⌥5 |
Blue |
⌘⌥6 |
Purple |
⌘⌥7 |
Pink |
⌘⌥8 |
Gray |
⌘⌥0 |
Reset |
Upstream is already exploring per-tab color indication on oz-agent/APP-4321-active-tab-color-indication — twarp will likely build on top of that work rather than re-invent it.
⌘⌥R triggers the same rename flow that double-clicking a tab title invokes — focus the active tab's title, enter inline edit mode, commit on Enter / cancel on Escape. The rename interaction already exists; this just adds a keyboard path into it so you don't have to reach for the trackpad to rename a tab.
A declarative way to bind a keyboard shortcut to a sequence of terminal actions: open a new tab, type text, press keys, wait, type more. Lets you turn frequent multi-step workflows into one keystroke.
Two driving examples:
⌘⇧D— open a new tab and auto-typeclaude(with enter).⌘⇧A— open a new tab, typeclaudeand enter, wait a couple of seconds, then type/address-code-review-comments ultrathinkand enter.
Sketch of the config format (final shape TBD):
shortcuts:
- keys: cmd+shift+d
actions:
- new_tab
- type: "claude"
- press: enter
- keys: cmd+shift+a
actions:
- new_tab
- type: "claude"
- press: enter
- wait: 2s
- type: "/address-code-review-comments ultrathink"
- press: enterThe intent is for the shortcut system to be powerful enough that "open Claude in a fresh tab and feed it a slash command" is one keystroke, and small enough that the config stays readable.
A built-in side panel for reviewing the current repo's changes — modeled directly on VS Code's Source Control view, behavior-for-behavior where it makes sense.
Goals:
- See working-tree changes and staged changes separately, with file counts at each level.
- Click a file to view the diff inline.
- Stage / unstage / discard at file or hunk level.
- Show the git Timeline (file history) for the focused file.
- Commit message input + commit / push / pull from the same panel.
The aim is parity with VS Code's panel for the operations a terminal user already does dozens of times a day, so you don't need to switch out of the terminal to review changes before committing.
twarp keeps warpdotdev/warp as upstream and cherry-picks selectively rather than bulk-merging. We deliberately don't run git merge upstream/master, because that re-fights the AI-deletion every cycle.
Workflow:
git fetch upstreamperiodically.git log upstream/master ^HEAD --onelineto see what's new.git cherry-pick <sha>for individual commits worth taking — perf, rendering, fixes, non-AI features. Skip AI-related commits.- Record integrated commits in
UPSTREAM_CHANGELOG.mdso we don't re-pick them.
Baseline (the state we forked from): warpdotdev/warp@d0f045c0 (2026-04-28).
Build process is unchanged from upstream Warp. See the original Warp README below for ./script/bootstrap, ./script/run, and ./script/presubmit, and WARP.md for the full engineering guide.
twarp is a fork of Warp, open-sourced by Warp Inc. on 2026-04-28. All upstream credit goes to the Warp team — twarp's modifications are limited to the four areas above.
twarp inherits Warp's licensing unchanged: the warpui_core and warpui crates are MIT, the rest of the tree is AGPL v3. See LICENSE-MIT and LICENSE-AGPL.
The section below is the original Warp README, preserved unchanged as part of the fork. Statements about Warp AI, OpenAI sponsorship, and GPT-powered agents describe upstream Warp, not twarp.
Website · Code · Agents · Terminal · Drive · Docs · How Warp Works
Note
OpenAI is the founding sponsor of the new, open-source Warp repository, and the new agentic management workflows are powered by GPT models.
Warp 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).
You can download Warp and read our docs for platform-specific instructions.
Explore build.warp.dev to:
- Watch thousands of Oz agents triage issues, write specs, implement changes, and review PRs
- View top contributors and in-flight features
- Track your own issues with GitHub sign-in
- Click into active agent sessions in a web-compiled Warp terminal
Warp's UI framework (the warpui_core and warpui crates) are licensed under the MIT license.
The rest of the code in this repository is licensed under the AGPL v3.
Warp'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 contribution flow, read our CONTRIBUTING.md guide.
Tip
Chat with contributors and the Warp team in the #oss-contributors Slack channel — a good place for ad-hoc questions, design discussion, and pairing with maintainers. New here? Join the Warp Slack community first, then jump into #oss-contributors.
Before filing, search existing issues for your bug or feature request. If nothing exists, file an issue using our templates. Security vulnerabilities should be reported privately as described in CONTRIBUTING.md.
Once filed, a Warp maintainer reviews the issue and may apply a readiness label: ready-to-spec signals the design is open for contributors to spec out, and ready-to-implement signals the design is settled and code PRs are welcome. Anyone can pick up a labeled issue — mention @oss-maintainers on an issue if you'd like it considered for a readiness label.
To build and run Warp from source:
./script/bootstrap # platform-specific setup
./script/run # build and run Warp
./script/presubmit # fmt, clippy, and testsSee WARP.md for the full engineering guide, including coding style, testing, and platform-specific notes.
Interested in joining the team? See our open roles.
- See our docs for a comprehensive guide to Warp's features.
- Join our Slack Community to connect with other users and get help from the Warp team — contributors hang out in
#oss-contributors. - Try our Preview build to test the latest experimental features.
- Mention @oss-maintainers on any issue to escalate to the team — for example, if you encounter problems with the automated agents.
We ask everyone to be respectful and empathetic. Warp follows the Code of Conduct. To report violations, email warp-coc at warp.dev.
We'd like to call out a few of the open source dependencies that have helped Warp to get off the ground: