fix(antigravity): replace Set-Content with WriteAllText to avoid UTF-8 BOM (#367)

[NyxSpecter4]

Fixes monk-io#367

Root Cause: jsonc-parser v3.3.1 (used by VS Code and Antigravity) returns the parsed object but logs errors: [{ offset: 0, error:1 }] (InvalidSymbol) when Windows PowerShell writes a UTF-8 BOM (0xEF 0xBB 0xBF).

Fix: Replace Set-Content -Encoding UTF8 with [System.IO.File]::WriteAllText using (New-Object System.Text.UTF8Encoding $false) to write without BOM.

File Changed: scripts/start-monk-agent.ps1

Test: Check that offset 0 is byte 0x7B ({) not 0xEF (BOM start)

Branch: fix/windows-utf8-bom from NyxSpecter4/monk-plugin

Author: Meli (via direct commit)

[qodo-code-review]

ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: f3187eb9-00fc-49c5-862f-5e9721b03459

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}