# Warp Agentic Development Environment Technical Wiki > An Explain Like I'm 5 guide to Warp, a modern GPU-accelerated terminal emulator built in Rust and equipped with powerful agentic AI capabilities. This is a Grok-Wiki source-grounded repository wiki. Use the complete Markdown link when an agent needs the full repo context. ## Context Links - [Complete Markdown wiki](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160/llms-full.txt) - [Complete Markdown alias](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160.md) - [Human interactive wiki](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160) - [GitHub repository](https://github.com/warpdotdev/warp) ## Repository - Repository: warpdotdev/warp - Generated: 2026-05-22T03:23:07.413Z - Updated: 2026-05-22T03:46:34.046Z - Runtime: Antigravity CLI - Format: Explain Like I'm 5 - Pages: 6 ## Pages - [Explain It Simply](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160/pages/01-explain-it-simply.md): Imagine a terminal combined with a smart helper robot. Warp is an agentic development environment where you can use a built-in AI companion or connect other AI coding agents (like Claude Code or Codex) to perform tasks for you. The most important things to remember are: Warp is built with a custom GPU-accelerated UI framework (WarpUI) in Rust, interacts with AI agents using isolated "skills", and serves as a unified workspace for terminal sessions, drive configurations, and code files. - [Developer Skills & Environment Setup](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160/pages/02-developer-skills-environment-setup.md): How do you set up this terminal-robot's environment? By running script/bootstrap, which installs Cargo dependencies and restores shared agent skills from a lock file called skills-lock.json. This lock file works like a toy chest list, ensuring everyone has the same common skills. Developers build with script/run, test with cargo nextest, and verify formatting and clippy lints with script/presubmit before opening a pull request. - [WarpUI Framework: The Entity-Handle Pattern](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160/pages/03-warpui-framework-the-entity-handle-pattern.md): How does Warp draw its screens? Instead of standard UI toolkits, it uses a custom UI framework built on the Entity-Component-Handle pattern. Think of it like a puppet show where a global App puppeteer owns all the puppets (views and models), and views talk to each other only by holding safe references (ViewHandle). It is Flutter-inspired, uses an Actions system for events, and requires creating a MouseStateHandle exactly once during construction to track mouse inputs—otherwise, clicking won't work! - [The Terminal Engine & Shell Control](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160/pages/04-the-terminal-engine-shell-control.md): Under the hood, how does the terminal act like a terminal? It reads and writes commands using Tokio and a customized version of Alacritty's ANSI parser. But be extremely careful with the terminal model: calling TerminalModel::lock() at the wrong time can cause a deadlock (the dread "beach ball of death") where two parts of the system are waiting for each other forever. The engine avoids this by passing already-locked references down the call stack instead of acquiring new ones. - [Warp AI: Built-in Agents & Codebase Context](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160/pages/05-warp-ai-built-in-agents-codebase-context.md): How does the built-in AI help you? It isn't just a text box; it is connected to a skill provider and codebase indexer that scans file paths and reads skills. The system can parse special instructions to let agents plan, triage issues, review PRs, and run shell tools, keeping the design provider-neutral so you can bring any AI provider (like Claude or GPT). - [Connecting the Dots: A Simple Recap](https://grok-wiki.com/public/wiki/warpdotdev-warp-a2a3b9202160/pages/06-connecting-the-dots-a-simple-recap.md): Let's review the big picture: Warp is like a premium dashboard for your terminal, powered by a customized Rust graphics engine (WarpUI) and driven by AI helpers (Oz and external agents). To keep it running smoothly, remember the Golden Rules: bootstrap your skills properly, never create duplicate model locks, and let the entity-handle pattern keep your UI threads safe and responsive. Next, jump into CONTRIBUTING.md and read the code under crates/warpui_core to see how the rendering magic works! ## Source Files - `Cargo.toml` - `CONTRIBUTING.md` - `crates/ai/src/lib.rs` - `crates/ai/src/paths.rs` - `crates/ai/src/skills/parse_skill.rs` - `crates/ai/src/skills/skill_provider.rs` - `crates/ai/src/workspace.rs` - `crates/warp_terminal/src/lib.rs` - `crates/warp_terminal/src/model/escape_sequences.rs` - `crates/warp_terminal/src/model/indexing.rs` - `crates/warp_terminal/src/model/mouse.rs` - `crates/warpui_core/src/core/app.rs` - `crates/warpui_core/src/core/entity.rs` - `crates/warpui_core/src/core/view/context.rs` - `crates/warpui_core/src/core/view/handle.rs` - `crates/warpui_core/src/core/view/mod.rs` - `crates/warpui_core/src/presenter.rs` - `FAQ.md` - `README.md` - `script/bootstrap` - `script/presubmit` - `script/resolve_common_skills` - `script/run` - `skills-lock.json` - `WARP.md`