pi-agent-integration
Implement Pi-agent consumers with stable streaming, correct queue semantics, and minimal wrapper surface area.
Step 1: Classify the request
Pick the path before editing:
| Request type | Read first |
|---|---|
| Wiring or updating agent wrapper APIs/options | references/api-surface.md |
| Adding behavior in a consumer library (chat, orchestration, tools) | references/common-use-cases.md |
| Debugging broken streaming/tool/continue behavior | references/troubleshooting-workarounds.md |
If the task spans multiple categories, load only the relevant files above.
Step 2: Apply integration guardrails
- Treat
Agentas the execution engine and keep wrapper abstractions thin. - Stream user-visible text only from
message_update+assistantMessageEvent.type === "text_delta". - Bridge deltas into
AsyncIterable<string>and pass that iterable to downstream streaming surfaces.
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-sandbox
Investigate Vercel Sandbox lifecycle, timeout, snapshot, and persistence behavior. Use when users ask about Vercel Sandbox, `@vercel/sandbox`, `Sandbox.create`, `Sandbox.get`, why files disappeared, how snapshots differ from persistence, or whether Vercel's persistent sandbox beta applies.
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.
1