Live-caught 2026-08-24 during compute e2e. insta login --device on --env staging (CLI 0.0.45) prints:
https://staging.instacloud.com/device?user_code=XXXX
That URL passes Vercel deployment-protection SSO and then hits the app's own 404 ("That page doesn't exist") — the /device approval route is not served by the staging frontend at that host. console.staging.instacloud.com/device is behind the same SSO (unverified whether the route exists there).
Two things to fix:
- The staging device-approval page must exist at whatever URL the CLI prints (either add the route to the staging frontend, or point the CLI at the host that serves it).
- UX nit from Tony: the device-flow output should label the environment explicitly ("log in to STAGING") so a user can't approve against the wrong deployment.
Workaround that unblocked us: insta login --oauth github (browser OAuth, no console route dependency).
🤖 Generated with Claude Code
Live-caught 2026-08-24 during compute e2e.
insta login --deviceon--env staging(CLI 0.0.45) prints:That URL passes Vercel deployment-protection SSO and then hits the app's own 404 ("That page doesn't exist") — the
/deviceapproval route is not served by the staging frontend at that host.console.staging.instacloud.com/deviceis behind the same SSO (unverified whether the route exists there).Two things to fix:
Workaround that unblocked us:
insta login --oauth github(browser OAuth, no console route dependency).🤖 Generated with Claude Code