Quick heads-up for anyone using the Agent API: the transport changed.
- Before: file-based — requests/responses exchanged as
.json files under {instance}/agent/requests/.
- Now: a local HTTP server on
127.0.0.1 (random port). The extension publishes { port, token, ... } to .vscode/sn-agent-port.json so agents can discover it; commands go to POST /api with an X-Agent-Token header.
Why: the file-watcher path was unreliable on iCloud/OneDrive/macOS (sync latency), causing missed or slow requests.
Compatibility: the file-based transport still works as a fallback — toggle sn-scriptsync.agentApi.fileFallback (default true). If your agent integration only knew about the file path, point it at the HTTP endpoint instead.
If you run into anything after this change, drop a comment here.
Quick heads-up for anyone using the Agent API: the transport changed.
.jsonfiles under{instance}/agent/requests/.127.0.0.1(random port). The extension publishes{ port, token, ... }to.vscode/sn-agent-port.jsonso agents can discover it; commands go toPOST /apiwith anX-Agent-Tokenheader.Why: the file-watcher path was unreliable on iCloud/OneDrive/macOS (sync latency), causing missed or slow requests.
Compatibility: the file-based transport still works as a fallback — toggle
sn-scriptsync.agentApi.fileFallback(defaulttrue). If your agent integration only knew about the file path, point it at the HTTP endpoint instead.If you run into anything after this change, drop a comment here.