I’m having trouble with KiloCode and could use some help. My background is mostly in infrastructure rather than development, but I’m working on building an application.
The issue I’m facing is that when KiloCode runs commands, it creates a separate external process instead of using the integrated PowerShell terminal in VSCode. I expected it to execute npm commands directly in the VSCode terminal, but instead it opens a new terminal window that I can’t easily access.
When this happens, KiloCode prompts me asking if I want to restart the npm run dev command. The problem is that I can’t see or interact with that external terminal properly, so restarting the npm process becomes difficult without terminating everything.
I’ve attempted to modify the settings.json file for both user and workspace configurations, but none of my changes have resolved the issue. I’m running VSCode with administrator privileges on my local machine.
Has anyone encountered this behavior before? Any suggestions would be really helpful.
Had this same problem a few months back. KiloCode was grabbing the system terminal settings instead of VSCode’s integrated terminal. Fixed it by checking terminal.integrated.defaultProfile.windows in VSCode first, then making sure KiloCode matched that profile. Also check if terminal.integrated.automationShell.windows is overriding your settings. Running as admin might be causing permission conflicts with the integrated terminal. Try launching VSCode without admin rights and see if that fixes it.
maybe check KiloCode’s settings. i had a similar prob once, and it turned out i needed to toggle a setting for it to use the built-in terminal. sometimes these extensions can be picky, ya know?
Sounds like a terminal execution path issue I’ve dealt with before. KiloCode’s probably defaulting to your system’s command processor instead of using VSCode’s terminal API. Check if you’ve got environment variables like TERMINAL or SHELL messing with the extension’s terminal detection. Also make sure KiloCode has the right permissions for VSCode’s integrated terminal - some extensions need workspace trust or specific API permissions. Try disabling other terminal extensions temporarily to see if something’s conflicting. Those admin privileges might actually be causing the problem since elevated processes sometimes can’t talk to the integrated terminal properly.
restart vs code completely after changing those settings - sometimes it caches the terminal config and won’t pick up changes until you do a full restart. also check if you’ve got any shell integration settings forcing external terminals.
This is why I ditched VS Code extension headaches and automated my dev workflow instead. Rather than fight KiloCode’s wonky terminal, I built simple automation for all my npm commands and dev tasks.
I use Latenode to monitor my project folder and auto-run npm commands when needed. It executes in whatever environment I want with full output control. No more weird external terminals or permission problems.
The workflow restarts my dev server when files change, sends build notifications, and logs everything where I can actually see it. Way cleaner than fixing buggy extensions.
I rolled this out to my whole team. Everyone gets the same behavior no matter their VS Code setup. Takes 10 minutes to build, saves hours debugging extensions.
Sounds like KiloCode is skipping VSCode’s terminal completely. I’ve seen this when extensions don’t hook into the terminal API properly. Check your terminal.integrated.commandsToSkipShell setting - it might be blocking KiloCode from using the integrated terminal. Also see if KiloCode hardcoded a terminal path somewhere in its config. The extension might be calling cmd.exe or powershell.exe directly instead of going through VSCode’s terminal service. Try a fresh workspace without any terminal customizations to see if that changes anything. Extensions sometimes cache their terminal settings and you’ll need to reset those separately from VSCode’s settings.