fix: use metadata_only=true when fetching account sandboxes

[sweetmantech]

Summary

• Adds metadata_only=true query param to the getAccountSandboxes() API call
• This tells the API to skip expensive Sandbox.get() calls since Tasks only needs snapshot_id and github_repo
• Companion PR to feat: add metadata_only param to GET /api/sandboxes api#215

Root Cause

The setup-sandbox task was failing with Error: Status code 410 is not ok because GET /api/sandboxes was making 100+ parallel Sandbox.get() API calls to Vercel, which caused the newly created sandbox to become unavailable by the time setupSandboxTask tried to use it.

Test plan

• Deploy alongside API PR and verify setup-sandbox task completes successfully

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@sweetmantech has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 36 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sweetmantech/myc-4201-bash-debug-failing-setup-sandbox-task

---

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 and usage tips.}