🐛 Biome does not start when VSCode starts that satisfy the new window condition with unopened files

[cworld1]

VS Code version

1.109.0

Extension version

3.3.0

Biome version

2.3.14

Operating system

• Windows
• macOS
• Linux

Description

Steps to reproduce

1. Launch the VSCode as a new window.
2. Open the file like test.css.

Expected behavior

As I open file like test.css, Biome should load automatically and I can use format freely. But as I use the Biome: Restart command in VSCode command palette, everything goes normally. I guess the extension has a lazy loading mechanism, but it doesn't seem to work very well.

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

No response

Logs

Before restart:


2026-02-07 19:07:02.726 [info]   ---------------------------------------- 
2026-02-07 19:07:02.726 [info]  🚀 Biome extension 3.3.0.
2026-02-07 19:07:02.726 [info]  ✨ Running in single-file mode.
2026-02-07 19:07:02.726 [error] ❌ Unable to start Biome for single file: no active editor.
2026-02-07 19:07:02.726 [info]  🚀 Created 0 Biome instance(s).
2026-02-07 19:07:02.726 [info]  🚀 Started 0 Biome instance(s).
2026-02-07 19:07:02.726 [info]  ✨ See the dedicated logging channels for more details.


After restart:


2026-02-07 19:14:11.418 [info]  ⏹️ Biome extension stopped.
2026-02-07 19:14:11.418 [info]   ---------------------------------------- 
2026-02-07 19:14:11.419 [info]  🚀 Biome extension 3.3.0.
2026-02-07 19:14:11.419 [info]  ✨ Running in single-file mode.
2026-02-07 19:14:11.419 [info]  🚀 Created 1 Biome instance(s).
2026-02-07 19:14:11.644 [info]  🚀 Started 1 Biome instance(s).
2026-02-07 19:14:11.644 [info]  ✨ See the dedicated logging channels for more details.

[cworld1]

I think the extension may need to check and try to create instance again when new file opened if there were no instance running.