Can I vibecode Warp?

Build a deeply integrated, AI-native terminal assistant to serve as a personal substitute for Warp.
Use Rust for the core terminal emulator to ensure blazing fast performance, with a TypeScript/React frontend (using Tauri or Electron) for the IDE-like interface, and SQLite for local history.
Primary job: Create a block-based terminal where every command and its output are treated as discrete, navigable UI elements.
1. Block-Based Interface: Implement an interface where commands and their outputs are grouped into visual blocks. Users should be able to click, copy, collapse, and share individual blocks effortlessly.
2. Modern Input Editor: The prompt must behave like a modern text editor. Support syntax highlighting, multi-line editing, smart autocompletion, and standard IDE cursor movements (e.g., Option+Click, Cmd+Arrow).
3. AI Integration: Embed a local AI agent (using a local LLM or user-provided API key). The AI should be able to translate natural language to shell commands, explain errors found in output blocks, and propose fixes directly within the terminal context.
4. Workflows & Runbooks: Implement a "Warp Drive" equivalent—a local repository of parameterized commands, workflows, and runbooks that can be easily searched and executed via a Command Palette (Cmd+P).
5. History & Search: Maintain a highly searchable, persistent history of all commands and outputs in SQLite.
6. Environment Management: Allow saving and switching between different environment variable profiles easily.
Make the default mode single-user and private. Store user data locally. Put every secret and external credential in .env and provide .env.example. Implement the smallest polished interface that completes the core loop end to end. Include clear empty, loading, validation, success, and failure states. Use accessible keyboard navigation, labels, focus states, and sensible contrast. Validate untrusted input and never log secrets or private file contents. Write focused unit tests for the data model and the most important workflow. Add one end-to-end smoke test that proves the core loop works. Create a README with setup, permissions, architecture, data location, backup, and limitations.