warpdotdev
VSCode / VS Code / Virtual Studio Code Embedding
I largely use the VSCode integrated terminal when developing, due to the easy integration into my workflow and ability to lay out within the VSCode UI.
It'd be great to use Warp, either as the terminal for the integrated terminal prompt (using a custom profile, see https://code.visualstudio.com/docs/editor/integrated-terminal#_terminal-profiles) or even as a separate extension.
if I have Warp selected in vscode as my external terminal program, normally I should be able to run the command "Open New External Terminal" and have a new prompt in that program, at the root of the project that I ran the command from. Currently this doesn't work. Focus is switched to Warp but I do not get the prompt in my project folder.
@o1lo01ol1o From #605
Describe the solution you'd like?
I'd like to use warp as a terminal in emacs and vscode
Is your feature request related to a problem? Please describe.
Half my terminal time is spent running cli commands in IDE windows. I'm aware that I could just switch to a dedicated terminal, but that's a context switch that I nearly never undertake.
Additional context
No response
I need this :) I spend all day in my IDE, using the integrated terminal will be just far more efficient for me until Warp is capable of it
Would love VS Code remote SSH integration with warp, would fully switch over then!
Has anyone found a hack or workaround for now? Loving Warp but hate having to jump between the two applications. 🙂
VS Code and PHPStorm alike only allow shell applications, warp is not a shell application in itself, it wraps itself around one, warp cannot be integrated into these IDE's without sacrificing majority of the features that make Warp a great product, it'll dilute down to just being another Git Bash. Perhaps a plugin is the only way forward here but warp definitely wont be able to integrate into these IDE's by the standard means, like you would with git bash for example.
Chances are this kind of integration wouldn't technically be possible until a WASM version of Warp exists.
Chances are this kind of integration wouldn't technically be possible until a WASM version of Warp exists.
Is this the main reason WASM is being prioritized over Linux and Windows (in that order)? Is this feature request going into the timeline or being tracked?
I would wager that the amount of overlap between Visual Studio Code (VS Code) users and people who are using or want to use Warp is very high, which includes myself.
if I have Warp selected in vscode as my external terminal program, normally I should be able to run the command "Open New External Terminal" and have a new prompt in that program, at the root of the project that I ran the command from. Currently this doesn't work. Focus is switched to Warp but I do not get the prompt in my project folder.
Same issue for us IntelliJ guys. Or you can choose what terminal executable through IDE but warp is different.
@bmitc It isn't the primary reason, the nice thing about a WASM version is that users across any platform will be able to use Warp to some degree (in the browser). It's also because our business model (see our pricing page) is a freemium model. Free for everyone with compelling features that teams and enterprises would want to pay for. A WASM version is in many ways a prerequisite to some of the ideas the Warp team has have for team and enterprise.
This is my (personal) understanding of the situation, I hope this helps.
As I understand, the main use case is switching quickly between the terminal and VSCode. The Hotkey global window might get it 90% of the way there. Here are the docs.
Using it would look something like this: https://www.loom.com/share/5e9e80960f7e45e38316f8cae3416352
Steps
- Make a new desktop
- Fullscreen VSCode in the new desktop
- Set up Hotkey window in Warp
- Code away
Let me know what you all think!
Thanks for the information @elviskahoro! That was helpful. Looking forward to when I can use Warp on Windows and/or VS Code! I use it on macOS for work and am liking it.
As I understand, the main use case is switching quickly between the terminal and VSCode. The Hotkey global window might get it 90% of the way there. Here are the docs.
Using it would look something like this: https://www.loom.com/share/5e9e80960f7e45e38316f8cae3416352
Steps
- Make a new desktop
- Fullscreen VSCode in the new desktop
- Set up Hotkey window in Warp
- Code away
Let me know what you all think!
its helpful but not enough, for example, I got two or more window of vscode , its the better if I trigger warp global hotkey and activate warp (if warp have not launch will new one) , and then go to the root path of the workspace where I trigger hotkey (maybe I need a vscode hotkey to activate warp and pass the workspace path), but its seem like no way to do like one of those. I find a way to do like this in vscode: shift + command + c can open an external terminal under the current directory, the external terminal should be the default terminal,so in other way, if warp can be set as the mac default terminal, it can work like that. as far as I know, iterm2 can do it.
@Nauxscript the main thing is changing the external terminal setting to Warp.app
does this screenshot help
?
its helpful but not enough, for example, I got two or more window of vscode , its the better if I trigger warp global hotkey and activate warp (if warp have not launch will new one) , and then go to the root path of the workspace where I trigger hotkey (maybe I need a vscode hotkey to activate warp and pass the workspace path), but its seem like no way to do like one of those. I find a way to do like this in vscode:
shift+command+ccan open an external terminal under the current directory, the external terminal should be the default terminal,so in other way, if warp can be set as the mac default terminal, it can work like that. as far as I know, iterm2 can do it.
Like @elviskahoro said, we recently launched support for Shift-Cmd-C from VSCode in the latest release! Check out the docs here. Let me know if that's what you meant and if that helps get us closer to a 90% solution.
its helpful but not enough, for example, I got two or more window of vscode , its the better if I trigger warp global hotkey and activate warp (if warp have not launch will new one) , and then go to the root path of the workspace where I trigger hotkey (maybe I need a vscode hotkey to activate warp and pass the workspace path), but its seem like no way to do like one of those. I find a way to do like this in vscode:
shift+command+ccan open an external terminal under the current directory, the external terminal should be the default terminal,so in other way, if warp can be set as the mac default terminal, it can work like that. as far as I know, iterm2 can do it.Like @elviskahoro said, we recently launched support for
Shift-Cmd-Cfrom VSCode in the latest release! Check out the docs here. Let me know if that's what you meant and if that helps get us closer to a 90% solution.
Lame solution 😵💫, but I'm glad we can finally use it together. 🥳🥳🥳 I love wrap!
its helpful but not enough, for example, I got two or more window of vscode , its the better if I trigger warp global hotkey and activate warp (if warp have not launch will new one) , and then go to the root path of the workspace where I trigger hotkey (maybe I need a vscode hotkey to activate warp and pass the workspace path), but its seem like no way to do like one of those. I find a way to do like this in vscode:
shift+command+ccan open an external terminal under the current directory, the external terminal should be the default terminal,so in other way, if warp can be set as the mac default terminal, it can work like that. as far as I know, iterm2 can do it.Like @elviskahoro said, we recently launched support for
Shift-Cmd-Cfrom VSCode in the latest release! Check out the docs here. Let me know if that's what you meant and if that helps get us closer to a 90% solution.
yes i have use shift + cmd + c hotkey a few day. in the last version of vscode (1.68.x), if i use this hotkey to open Warp, the new tab of warp would not open on the vscode workspace root path. But now the tab path is correct in vscode version 1.69.0.
there is the setting for someone want to use Warp on vscode（its not really "on vscode" exactly, but use them in easy and comfortable way）：
add in vscode setting.json
{
...// your setting
"terminal.external.osxExec": "Warp.app",
...// your setting
}
@vjindal0112, both solutions (hotkey window and shift+cmd+c) come to solve the same problem but I couldn't make it work together. I.e. when I press shift+cmd+c it opens a new Warp session but in a separate window but when I use the hotkey it opens the pinned window unrelated to the window opened with shift+cmd+c. Also, the hotkey doesn't work if there is no running Warp session.
Any chance we can make it work together? It would be a sufficient replacement for the VSCode integration.
This is really really difficult eng wise. Just being transparent so people don't get their hopes up that this would come out anytime soon. (elvis) Will share more info if things change!
--- original message --- On April 11, 2022, 10:08 AM EDT @.*** wrote:
Please add this feature
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- You received this message because you are subscribed to the Google Groups "github" group. To unsubscribe from this group and stop receiving emails from it, send an email to @.*** --- end of original message ---
user on #2305 commented:
I mostly use a terminal embedded in my IDE of choice (PyCharm / IntelliJ). This uses a configurable shell and automatically provides the context i.e. Conda environment and working directory. It would be nice to use warp in this context.
its helpful but not enough, for example, I got two or more window of vscode , its the better if I trigger warp global hotkey and activate warp (if warp have not launch will new one) , and then go to the root path of the workspace where I trigger hotkey (maybe I need a vscode hotkey to activate warp and pass the workspace path), but its seem like no way to do like one of those. I find a way to do like this in vscode:
shift+command+ccan open an external terminal under the current directory, the external terminal should be the default terminal,so in other way, if warp can be set as the mac default terminal, it can work like that. as far as I know, iterm2 can do it.Like @elviskahoro said, we recently launched support for
Shift-Cmd-Cfrom VSCode in the latest release! Check out the docs here. Let me know if that's what you meant and if that helps get us closer to a 90% solution.
@vjindal0112 Can this be integrated with hot key support too? when I open terminal using cmd+shift+c, then it's opening on separated tab. And when using hot key, it opens on the same tab as i use, but in that case the instance is always same.
@wangmir Take a look at the Global hotkey window feature, it should help with your use case. https://docs.warp.dev/features/windows/hotkey-window
+1 This should be the "most wanted feature"!!! Warp's 10.000 USD reward for good old Billy "The integrated" Wizkiss.
Just imagine the sheer number of Youtube videos that would be made with banging headlines "New AI and terminal in VScode" and so on. Heck, any homeless person with a youtube channel and 30 followers will be putting on Lulumemons and go trawling for likes.. - written by GPT-4.0 (I am not liable)
🖖They've gone Plaid! Less than 24 hours from the last feature request and devs releases 2023.03.23 (v0.2023.03.21.08.02) - Absolutely amazing, fantastic product by the way - Light years from the competition
- New features:
- Added VSCode Insiders as a supported code editor
By the way, how many Borg does it take to change a light bulb? 💡 All of them, because they are one! 🤖
Why is it that the same three people have been downvoting this feature request?
- is there some downside to this feature?