docs(pi): add integration docs and example

[eersnington]

Adds the Pi page at /integrations/pi, its quickstart snippets, and examples/pi-credentials.

• Quickstart: install, define the actor, add a sandbox, send a prompt, deploy.
• Configuration table and tracing.
• Bring your subscription: credentials backed by a credentials actor.
• examples/pi-credentials: a credentials actor that stores and refreshes each user's logins, and pnpm provider-login to try it.

---

This is part 3 of 3 in a stack:

•  3  docs(pi): add integration docs and example #5796 👈
•  2  feat(pi): add pi actor integration #5767
•  1  feat(sandbox-adapter): add sandbox providers for agentOS, E2B, and Daytona #5799

[claude]

Code Review

Reviewed the current diff. The pi-credentials example is small and reads well. Findings below.

1. Scripts run .ts with bare node
examples/pi-credentials/package.json:7-8 uses node src/server.ts and node scripts/provider-login.ts. Node only strips types by default from 22.18 (22.6+ with a flag), and the repo declares node >=20. examples/CLAUDE.md prescribes tsx (or srvx --import tsx). Suggest tsx src/server.ts and tsx scripts/provider-login.ts, with tsx added to devDependencies.

2. Missing pieces required by examples/CLAUDE.md

• README.md has no ## Features or ## Resources sections, and no ## Prerequisites even though provider logins or API keys are needed.
• tsconfig.json lacks rewriteRelativeImportExtensions, which the guide pairs with allowImportingTsExtensions.

3. notify switch has no fallback
scripts/provider-login.ts:35-47 handles auth_url, device_code, info and progress only. Any other event type prints nothing and the user sees a silent terminal. A default that logs the event would help, unless the type is a closed union covered by those four cases.

4. Security and robustness

• The README notes that the credentials actor exposes tokens to any client that can reach it. Still, read returns access tokens and save accepts any credential from any caller. Consider an auth check (for example onBeforeConnect) or a code comment at the actor so copy-paste use is safe by default.
• refresh writes c.state.saved[provider] after an await. Concurrent refreshes for one provider can both hit the OAuth endpoint, and with rotating refresh tokens the loser may persist a stale token. An in-flight promise per provider in vars would avoid it.
• refresh on an unknown provider passes undefined to store.modify and silently returns undefined. An explicit error fits the fail-by-default guidance.
• process.exit(0) at the end of provider-login.ts hides open handles. terminal.close() is cleaner.

5. Other

• pnpm-lock.yaml shows about 300 lines removed. Please confirm that is intended fallout and not an unrelated lockfile regeneration.
• docs/general/content/index.mdx removes 2 lines that the PR description does not mention.
• No tests. setupTest from rivetkit/test could cover save, list and read, and check that read strips the refresh token.

🤖 Generated with Claude Code

[the-company-company]

🟠 2 medium · 🔵 1 low

_{Reviewed commit e5040f4.}

[the-company-company]

🟠 2 medium · 🔵 1 low

_{Reviewed commit 89a5bd7.}

[the-company-company]

🟠 Medium · Credential actions expose provider tokens to every caller

read returns the stored API key or OAuth access token, and save also lets an unauthenticated caller replace it. Because this actor has no connection or action authorization, anyone who can reach it and select a user's actor key can steal or overwrite that user's login; the README warning does not enforce the boundary. Make the credential store inaccessible to public actor clients, or add authentication and actor-key authorization to the example before exposing these actions.

[eersnington]

no shit?