vercel-sandbox
Investigate Vercel Sandbox using current official docs, installed SDK contracts, and only then any consumer-specific integration code.
Step 1: Classify the request
Pick the narrowest reference set before answering:
| Request type | Read first |
|---|---|
| SDK/API behavior, lifecycle semantics, snapshots, stable vs beta persistence | references/api-surface.md |
| Product-level usage patterns and architectural choices | references/common-use-cases.md |
| Broken behavior, confusing docs, missing files, or suspected persistence bugs | references/troubleshooting-workarounds.md |
If the task spans categories, load only the relevant files above.
Step 2: Establish which sandbox model applies
- Inspect the installed
@vercel/sandboxversion and local types before trusting any doc page or changelog. - If local types only expose
sandboxId,Sandbox.get({ sandboxId }),extendTimeout, and snapshot-backedsource, treat the runtime as stable 1.x ephemeral sandboxes. - If local code and types expose named sandboxes,
name,persistent, session updates, or automatic resume after stop, treat the runtime as the persistent beta model.
More from getsentry/junior
nitro
Build and deploy universal JavaScript servers with Nitro v3. Use when working with nitro.config.ts, defineNitroConfig, defineHandler, defineConfig, server.ts entry, filesystem routing, route rules, useStorage, defineCachedHandler, useDatabase, definePlugin, runtime hooks, Vercel/Cloudflare deployment, or migrating from Nitro v2/nitropack.
2public-docs
Create and maintain public, user-facing product documentation for this repo's `packages/docs` app. Use when asked to write, revise, or review docs pages (tutorial/concept/reference/troubleshooting), improve docs information architecture, fix docs frontmatter/linking issues, or align docs quality with Vercel/Sentry-style standards.
2deslop
Simplifies code interfaces and removes codebase slop while preserving behavior. Use when asked to "deslop", "simplify this interface", "remove cruft", "clean up comments", or "reduce code slop". Enforces hard guardrails for smaller public surfaces, dead-code removal, and high-signal comments.
1vercel-queues
Build and operate Vercel Queues with @vercel/queue across push and poll consumers. Use when users ask about "vercel queues", "@vercel/queue", "queue/v2beta", "handleCallback", "PollingQueueClient", "receive", queue retries, visibility timeouts, idempotency keys, or queue region routing.
1slack-msw-tests
Author Slack HTTP integration tests using the repository MSW harness and fixture factories. Use when asked to add a Slack integration test, mock Slack API calls with MSW, test Slack action HTTP behavior, or assert Slack request payloads in tests.
1slack-development
Implement Slack bot behavior with correct Slack-documented message formats, inbound mention/event routing, and long-running task UX. Use when asked to "format Slack messages", "fix Slack markdown", "debug thread mentions", "improve Slack bot UX", "add streaming in Slack", or "build Slack Chat SDK behavior". Covers mrkdwn quirks, Events API payload patterns, routing guardrails, and Chat SDK implementation patterns.
1