Follow-up: still broken on 3.17.8, new error signature.
@mohitjain you said this was identified/fixed and would land after 3.13.x. On 3.17.8 (commit 2fdd31c9f33f7fbe501f2d57772dc5bf64b63620, arm64) Plan → Build in Cloud still fails. It is no longer a silent no-op.
Actual
UI dialog:
Failed to migrate agent
[invalid_argument] Error
Tried twice (~14s apart). Both times the same dialog.
Renderer (window1_wb0/renderer.log):
2026-08-24 14:58:34.399 [error] [GlassAgentMigrationService] Pipeline migration failed. [invalid_argument] Error
2026-08-24 14:58:48.444 [error] [GlassAgentMigrationService] Pipeline migration failed. [invalid_argument] Error
~1 minute earlier, same renderer, ENOPRO against existing Background Agent remotes (not claiming these are this migrate’s id — they were already in the log):
ENOPRO: No file system provider found for resource
‘vscode-remote://background-composer%2Bbc-…/workspace/.cursor/sandbox.json’
Repro
- Open a multi-root local workspace (several git folders in one window).
- Use a Plan in the current agent chat.
- Click Build in Cloud.
- Dialog above; cloud agent does not start.
Expected
Cloud agent starts from the plan, or a specific reason (no GitHub remote, no cloud target, etc.) — not a generic [invalid_argument] Error.
Environment
- macOS 26.5.2 (Build 25F84), Darwin arm64, Apple M3
- Cursor IDE 3.17.8 2fdd31c9f33f7fbe501f2d57772dc5bf64b63620 arm64
- VS Code version: unknown — About Cursor copy unavailable
- Request ID: unknown — not shown on the dialog; not on the GlassAgentMigrationService lines
- Share Data: not captured for this failure
Does this stop you from using Cursor?
No — Cursor works, but Build in Cloud from this plan does not.
Related: 3.17.8: auto move_agent_to_root treats local multi-root as multi-repo cloud agent (same 3.17.8 train, multi-root vs cloud-agent; different trigger).
