Skip to content

You can use Warp as a terminal within Cursor or VS Code! This would give you the best of both worlds:

How to set it up:

  1. In VS Code/Cursor: Open Settings → Search for “terminal.integrated.defaultProfile” (for your OS)
  2. Point to Warp’s shell: Set it to use the same shell that Warp uses (bash in your case)

However, there’s an important limitation:

Warp’s AI agent features (the conversational AI you’re using now) are only available in the standalone Warp application, not when running as an embedded terminal in another editor. If you use Warp as a terminal inside Cursor/VS Code, you’ll get a standard terminal experience without Agent Mode.

Better workflow options:

  1. Dual-tool approach (recommended):

    • Use Cursor/VS Code for editing with astro dev running for HMR
    • Keep Warp open separately for AI-assisted terminal tasks, file generation, debugging
    • Both can work on the same project simultaneously
  2. Warp’s built-in editor + external preview:

    • Run astro dev in Warp’s terminal
    • Use Warp’s native editor for quick edits (it has HMR support since the dev server watches files)
    • Switch to Cursor for more complex editing sessions
  3. Cursor AI + Warp AI specialization:

    • Cursor: Code editing, refactoring, component creation
    • Warp: Build tasks, git operations, deployment, debugging, system commands

The dual-tool approach (#1) is most efficient—each tool excels at different tasks, and astro dev works regardless of which editor modifies the files.


  • need the folder and filenames in lowercase, with NO spaces, and NO .md (or .mdx) extension.
  • easily link to any heading in same/any .md/.mdx file, by adding #

[!example] Examples

  • Link to the Naming Systems page:

    [Naming Systems](/business/processes/naming/)
  • Link to the Language Standards heading on the same page:

    [Language Standards](/business/processes/naming/#language-standards)