Pre-submit Checks

• I have searched Warp feature requests and there are no duplicates
• I have searched Warp docs and my feature is not there

Describe the solution you'd like?

Add LSP Support

Summary

Warp has built something incredible: the best terminal experience, powerful AI agents, modern UX, and blazing-fast performance. You're one feature away from creating an unbeatable development environment that no competitor could match.

That feature is Language Server Protocol (LSP) support.

The Current Gap

Right now, Warp excels at:

• Terminal workflows (best in class)
• AI-driven code generation (Agent Mode, codebase context)
• Quick file edits (syntax highlighting, find/replace)
• Performance (Rust-based, incredibly fast)

But developers still need to switch to VS Code/Cursor/JetBrains for:

• Intelligent autocomplete while coding
• Inline error detection and warnings
• Hover documentation
• Code actions and quick fixes

This context-switching breaks the flow that Warp is trying to perfect.

Why This Matters (Even With Your ADE Philosophy)

I understand Warp's vision: "developers will write less code by hand, so why optimize for hand-editing?"

Here's why LSP still fits that vision:

1. Agents aren't perfect (yet)

Even the best AI agents generate code that needs manual refinement:

• Variable names need adjusting
• Edge cases require tweaking
• Integration points need manual connection
• Code review requires understanding what was generated

With LSP: Developers can make these adjustments efficiently with autocomplete, inline errors, and quick fixes without leaving Warp.

Without LSP: They copy the code to VS Code, make edits there, copy back. Flow broken.

2. The best workflow is hybrid

Real-world development isn't "all AI" or "all manual" it's both.

3. LSP enhances AI, not replaces it

LSP and AI agents are complementary:

• AI agents: Generate large code changes, understand codebase context, automate workflows
• LSP: Provide instant feedback while editing, catch errors early, help navigate unfamiliar code

The combination is more powerful than either alone.

4. Not all code is appropriate for AI generation

• Legacy codebases with complex business logic
• Performance-critical optimizations
• Embedded systems / low-level programming
• Learning new frameworks (where you want to write manually to understand)

These scenarios benefit from traditional IDE features.

If you add LSP, there's no competition. You'd have the only tool that combines:

• Best terminal
• Best AI agents
• Best performance
• Full IDE capabilities

Real-World Use Cases

Use Case 1: CS Student (My Perspective)

I'm a first-year CS student. I love Warp's terminal and AI agents. But when coding assignments:

1. I start in Warp, use agents to generate initial structure
2. Switch to VS Code to actually write the logic (need autocomplete for library methods)
3. Come back to Warp to run/test
4. Go back to VS Code to debug based on errors

With LSP in Warp: I'd never leave. Agent generates structure, I fill in logic with autocomplete, run tests, iterate—all in one place.

Use Case 2: Learning New Frameworks

When learning React/Next.js/whatever:

• Agent generates boilerplate
• I need autocomplete to discover available props/methods
• LSP shows inline docs so I learn the API
• I write code manually to understand patterns

Right now: I have to use VS Code for this. With LSP: I could learn entirely in Warp.

Technical Feasibility

You've already built most of what's needed:

• Text editor with syntax highlighting
• File tree and navigation
• Codebase indexing (for AI context)
• Rust-based architecture (LSP clients exist in Rust)

LSP integration would:

• Use existing LSP infrastructure (it's a standard protocol)
• Leverage your existing editor component

Inspiration: Zed (also Rust-based) has excellent LSP integration. Helix (also Rust) has LSP. The patterns are proven.

Why This Doesn't Contradict Your Vision

Your vision: "Agentic Development Environment"

LSP doesn't fight this, it completes it:

1. ADE = Agents + Developer working together

   • Agents generate code
   • Developer reviews/edits with LSP assistance
   • Both are empowered

2. You're already building an editor

   • You have syntax highlighting, find/replace, file tree
   • LSP just makes that editor actually competitive
   • It's the natural evolution of what you've started

3. The future is both

   • Yes, AI will write more code
   • But humans will always need to read, understand, and refine it
   • LSP makes that process efficient

What Developers Are Saying

From your own blog post about building the code editor:

"I found myself wanting features like LSP, find/replace, and a better experience for viewing multiple files."

Your own intern recognized this gap. Your users feel it too.

The Bottom Line

Warp is incredible. You've built the best terminal, the best AI agent system, the best UX. You're so close to creating the ultimate development environment.

LSP is the missing 10% that would make Warp the 100% solution.

Without it, developers have to maintain a dual setup:

• Warp for terminal + AI
• VS Code/JetBrains for actual coding

With it, Warp becomes the only tool they need.

Respectful Acknowledgment

I know you have a product vision and limited resources. I'm not suggesting you abandon your ADE philosophy, I'm suggesting LSP would strengthen it.

You're building the future of development. LSP support would ensure that future is built entirely in Warp, not split between Warp and traditional IDEs.

---

Thank you for building Warp. It's already changed how I work. With LSP, it could become the only development tool I ever need.

Would love to hear the team's thoughts on this. Happy to discuss further or help beta test if this moves forward.

---

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

Operating system (OS)

Windows

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None