Azure / Azure/bicep

Bicep Connection Closed Error in Claude Code

Open
#19,213 1 comment 0 reactions 0 assignees View on GitHub
enhancement Needs: Upvote
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

Does this occur consistently? It only started now, but have occurred at least 3 times in the last 30 minutes.
Repro steps:
1. Don't know, running Claude Code in Planning mode at the moment.

Action: bicep.lsp-error
Error type: Error
Error Message: Connection closed

Version: 0.41.2
OS: win32
OS Release: 10.0.26200
Product: Visual Studio Code
Product Version: 1.110.0
Language: en

Call Stack

```
extension.js:2:2664731extension.js:2:2664731
callWithTelemetryAndErrorHandlingSync extension.js:2:963805
Object.closed extension.js:2:2664639
LanguageClient.handleConnectionClosed extension.js:2:1844515
LanguageClient.handleConnectionClosed extension.js:2:2019208
extension.js:2:1844132extension.js:2:1844132
CallbackList.invoke extension.js:2:1787630
Emitter.fire extension.js:2:1788418
closeHandler extension.js:2:1772729
CallbackList.invoke extension.js:2:1787630
Emitter.fire extension.js:2:1788418
SocketMessageWriter.fireClose extension.js:2:1800214
Socket. extension.js:2:1801025
```

Contributor guide

Open the contributing guide

Research direction

Start with the bicep.lsp-error report and the extension.js call stack in the issue, then try to reproduce it in Claude Code Planning mode on Windows with Bicep 0.41.2 and VS Code 1.110.0. Done means the connection-closed cause is identified and the issue has a verified resolution or a documented non-reproduction.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.