microsoft / microsoft/vscode-websearchforcopilot

Web Search not working

Open
#43 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
65
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Type: Bug

Request Failed: 400 {"error":{"message":"tools are required when tool choice is specified","code":"invalid_request_body"}}

Extension version: 0.1.2
VS Code version: Code 1.102.1 (7adae6a56e34cb64d08899664b814cf620465925, 2025-07-15T16:41:17.147Z)
OS version: Windows_NT x64 10.0.26100
Modes:

System Info
Item Value
CPUs Intel(R) CoreTM Ultra 7 165U (14 x 2688)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) undefined
Memory (System) 15.58GB (0.93GB free)
Process Argv --crash-reporter-id b62bcda0-d3c8-440d-b76a-ba7327786a82
Screen Reader no
VM 0%
A/B Experiments
vsliv368:30146709
binariesv615:30325510
2e7ec940:31000449
nativeloc1:31344060
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
hdaa2157:31222309
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
c7cif404:31314491
pythonpulldiag:31343502
996jf627:31283433
pythonrdcb7:31342333
usemplatestapi:31297334
0aa6g176:31307128
747dc170:31275177
6518g693:31334701
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
pylancequickfixt:31350061
nes-only-ctrl:31349245
9d2cg352:31346308
convertlamdaf:31350062
usemarketplace:31343026
nesew2to5:31336538
agentclaude:31335814
nes-diff-11:31337487
replacestringexc:31350595
nes-set-on:31340697
6abeh943:31336334
envsdeactivate2:31352071
yijiwantestdri0626-c:31336931
0927b901:31350571
f76d9909:31348711
1je7-usegpt41:31346762
0cj2b977:31350606
a02b4192-color:31352028

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing Web Search from the extension at version 0.1.2 in the reported VS Code and Windows environment, then inspect the request that produces the 400 error. Done means Web Search completes without the reported invalid_request_body response; the issue does not identify a source file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
api, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.