Skip to content

Latest commit

 

History

History
37 lines (22 loc) · 2.54 KB

File metadata and controls

37 lines (22 loc) · 2.54 KB

webcode FAQ

Language: English | 中文

What do I need before the first launch?

Check these items to avoid common first-launch failures:

  • Install VS Code 1.106.1 or later.
  • Open a local project folder or workspace in VS Code, not just a single file.
  • The default browser mode is Edge Isolated Keepalive and does not require manual browser-extension installation; Windows usually includes Edge, while macOS needs Microsoft Edge installed first.
  • On Windows, the default POSIX mode of execute_command requires Git Bash. If Git Bash is installed in a custom path, point webcodeGateway.commandShell.path to bash.exe. You can also explicitly select a detected pwsh or powershell profile for PowerShell commands.
  • Have an account for the target web AI product and make sure its site is reachable from your network. The first launch requires signing in once inside the isolated Edge profile.

What if @webcode or /webcode does not trigger on the page?

Make sure there is a space before the trigger word, for example:

Read the current project structure. /webcode

If the page still does not trigger, refresh the current page, confirm the browser extension popup shows that it is connected, then type the trigger again. In a new conversation, if the first message forgets the trigger, webcode also shows the initialization confirmation when you click Send or press Enter.

What if the AI returns a tool call and the tool succeeds, but the page does not change?

Refresh the current page. After the refresh, webcode scans the page again and reruns the tool-result delivery flow for tool calls that still need to be handled.

What if isolated Edge opens an extra new tab when opening an AI page?

Some Microsoft Edge versions may open an extra new tab based on the isolated profile's New Tab settings. In the isolated Edge window opened by webcode, go to edge://settings/startHomeNTP, then turn off "Preload the new tab page for a faster experience" under "Start, home, and new tabs".

If the extra new tab still appears, check whether "When Edge starts" is set to "Open the new tab page", and try switching it to "Open tabs from the previous session". After changing the setting, fully close all Edge processes, then open the AI page from VS Code again.

How can I see which tools the AI called before?

Click the browser extension popup and enable logs. The summary column records each tool call, so you can review which tools the AI called and in what order.