[RESOLVED] No more VS Code autocompletion when creating a WAPT package

Share your tips or issues concerning the WAPT Console or WAPT Agent here
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Answer
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 18, 2026 - 4:40 PM

Hello,

I've recently encountered a problem with VS Code when creating my WAPT packages.

When I generate a package template and the folder opens in VS Code, I lose autocompletion. I can't get suggestions for native functions (like print) or setuphelpers.

However, if I open a blank folder, everything works normally.

If anyone can shed some light on this, I'd be very grateful! :D

Thanks in advance.
Last edited by stan on June 23, 2026 - 4:03 PM, edited 1 time.
User avatar
dcardon
WAPT Expert
Messages: 1978
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 18, 2026 - 6:03 PM

Hi Stan,

what version of Wapt are you using, etc.?

Could you try deleting/renaming the vscode directory in your AppData folder? That often solves the problem. Personally, I don't use vscode; I'm more of an old-school developer with PyScripter3. :-)

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 19, 2026 - 09:24

Good morning,

Here is the information:

Code: Select all

WAPT Enterprise version 2.6.1.17813

OS Server : Debian 12

OS de la machine d'administration : Windows 11 25H2.
Yes, I've already done that and nothing changes.
For PyScripter3, it's really the last resort if I can't solve the problem with VSCode :)

Sincerely,

Stan
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 23, 2026 - 4:03 PM

After downgrading VSCode to version 1.116.0, autocompletion works.

This issue is therefore resolved. :)
Sincerely,

Stan

-

Information:

Code: Select all

OS Administration : Windows 11 25H2
OS Server : Debian 12
WAPT Version : 2.6.1.17813
VSCode Version : 1.116.0
italbot
Messages: 78
Registration: Sep 26, 2023 - 3:50 p.m.

June 24, 2026 - 11:39

Hello,

Noted. After installing version 1.125.0 of VS Code, I still have autocompletion. The problem might be with an extension rather than VS Code itself.

Sincerely,

Ingrid
Tranquil IT
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 24, 2026 - 11:41

Hello,

I removed everything, I only added the Python extension, the same for 1.116.0 and 1.125.0. And only 1.116 works with autocompletion.
Sincerely,

Stan

-

Information:

Code: Select all

OS Administration : Windows 11 25H2
OS Server : Debian 12
WAPT Version : 2.6.1.17813
VSCode Version : 1.116.0
User avatar
dcardon
WAPT Expert
Messages: 1978
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 25, 2026 - 6:01 PM

Hi Stan,

was this related to viewtopic.php?t=4715 ?

Does it now work correctly with the latest version of VS Code?

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 25, 2026 - 6:33 PM

Hello,

I don't think so, I'll try updating VScode tomorrow to see if that changes anything.
Sincerely,

Stan

-

Information:

Code: Select all

OS Administration : Windows 11 25H2
OS Server : Debian 12
WAPT Version : 2.6.1.17813
VSCode Version : 1.116.0
stan
Messages: 37
Registration: May 26, 2025 - 10:16 p.m.

June 26, 2026 - 12:06

Good morning,

I found the solution. The problem comes from a setting in VS Code, and not from the interpreter or "debugpy".

In the latest versions of VS Code, if GitHub Copilot is enabled, I believe VS Code applies this behavior by default:
JSON

Code: Select all

"editor.quickSuggestions": {
    "other": "offWhenInlineCompletions"
}
This setting disables the standard autocomplete list (Pylance) in favor of Copilot's online suggestions. This is why WAPT functions no longer appear.

To resolve this conflict, you need to force the display of suggestions. I propose adding this default configuration to the settings.json file generated by WAPT:
JSON

Code: Select all

"editor.quickSuggestions": {
    "other": "on"
}

Here's a short video showing how it works (in the video I use `true` when it should be "on", I think it's already "on" by default, so that's why it worked):
https://youtu.be/I572GGS2ufE
Sincerely,

Stan

-

Information:

Code: Select all

OS Administration : Windows 11 25H2
OS Server : Debian 12
WAPT Version : 2.6.1.17813
VSCode Version : 1.116.0
Answer