[betegon]

sentry init no longer runs the remote Mastra setup wizard. It prints a
Markdown guide (packages/cli/init.md) that a coding agent follows to add
Sentry to a project, the same way Railway (railway.com/agents.md) and
Vercel (vercel.com/get-started.md) hand agents a playbook:

1. Install the CLI (skipped when reading from sentry init)
2. Log in with sentry auth login
3. Map the project: which apps to set up, which SDKs each one needs (often
   more than one: TanStack Start on Cloudflare needs @sentry/cloudflare
   and @sentry/tanstackstart-react), and whether Sentry is already there,
   in which case it upgrades or extends the setup instead
4. Pick or create a Sentry project and read its DSN
5. Suggest features that fit the app (errors, tracing, logs, metrics, Session
   Replay, profiling, crons, User Feedback, AI agent and MCP monitoring) and
   ask the user which to enable
6. Install the SDKs from the current docs, never from remembered versions or
   APIs
7. Verify with a test error: sentry local run --verify, then
   sentry issue list
8. Report back from what was actually checked

The rules in steps 3, 5, and 6 come from the hosted wizard's agent prompts in
getsentry/cli-init-api: deployable contexts and one SDK per runtime,
evidence-only Crons/AI/MCP suggestions, features that need tracing, the DSN
placement policy, configuring only the chosen features, installing every
package the code imports, browser profiling's Document-Policy header, and
conversation tracking for AI agent monitoring.

Agents get the Markdown source, whether they read it through a pipe or a
pseudo-terminal that detectAgent recognizes; a person in a terminal gets it
rendered; --json returns { guide }. Like any command without input, it
takes no positionals and no flags of its own, only --json and --fields.
It sends nothing to Sentry, so it needs no login and skips the .sentryclirc
URL check (skipRcUrlCheck), which otherwise rejects a directory whose
.sentryclirc points at another Sentry host. With a self-hosted Sentry, the guide tells the agent to read the
docs.sentry.io pages as Markdown, because sentry docs needs a sentry.io
login. The docs site serves the same file at
https://cli.sentry.dev/get-started-with-sentry.md (a symlink in
apps/cli-docs/public, like install), so users can also say "Fetch
https://cli.sentry.dev/get-started-with-sentry.md and follow it" before the
CLI is installed. It isn't called init.md there, which would read as a
guide to initializing the CLI itself.

Removed

• The wizard runner, its local tools, preflight, verification, Ink wizard
  screens, and the init-eval suite (src/lib/init/, test/lib/init/,
  test/init-eval/)
• init's flags (--yes, --features, --dry-run, --team, --app,
  --no-tui), positionals ([target] [directory]), and their completer.
  Passing one now fails like it would on any other command
• WizardError, wizard prompt telemetry, SENTRY_INIT_TUI, MASTRA_API_URL
  (sentry docs always calls the hosted service), and the update-notice
  suppression for init
• @mastra/client-js and ink-spinner, plus the @ai-sdk/provider-utils@2.2.8
  patch that existed only for Mastra's copy
• Code that only the wizard called: the glob engine (scan/glob.ts),
  safe-read.ts, resolveOrCreateTeam's deferAutoCreateOnEmptyOrg,
  buildProjectIssuesUrl, and exports such as looksLikePath,
  getUncommittedFiles, and captureOAuthScopeRecoveryGate
• The zod/v3 stub's ZodType export and the GHSA-866g-f22w-33x8
  dependency-review allowance, which only Mastra's dependencies needed

Kept and moved

• The org/project/account picker moved from src/lib/init/ui/ to
  src/lib/select-ui/ and is now only what those prompts use: one
  filterable, single-choice list drawn inline. The wizard's multiselect,
  centered layout, details panel, paging, shortcut registry, and frame
  width helpers are gone. The sidecar is still
  ink-app.js, so build and packaging are unchanged. Picker tests that went
  through the wizard App now render SelectPicker directly.
• sentry docs still calls the same hosted service; its host check moved from
  init/init-service-auth.ts into docs-service.ts.
• Exit codes 61–63 are gone rather than reserved, since the CLI is still
  0.x; 64 is still used by sentry local run --verify, now named
  EXIT.VERIFY_FAILED.

Also

• Labels in the compact picker no longer disappear when a long hint fills the
  row (found while porting the tests).

• check:doc-examples now validates every sentry … command in init.md.

• init.md is embedded by an init-guide step in script/generate.ts
  (phase 1, skipped when init.md hasn't changed).

• The agent skill tells agents to use sentry init when adding Sentry.

• The installers still honor SENTRY_INIT=1: they run sentry init after
  cli setup, which no longer skips its login step for it.

Not in this PR

• The wizard workflow on the hosted Mastra worker can be retired separately;
  the worker still serves sentry docs.

Testing

Rebased on main at 9637d09:

• pnpm run typecheck, root pnpm run lint, and pnpm run ci:policy pass
• vitest run test/lib test/commands test/types test/script: 12,563 pass.
  The 22 failures are in permission and zstd tests (cli fix,
  agent-skills, completions install, db/resilient, code-scanner,
  upgrade, zstd-transport) that also fail on main in this sandbox,
  which runs as root on Node 22
• script/bundle.ts builds dist/ink-app.js with mountSelectPrompt;
  sentry init prints the guide from the bundle, with no token and a
  self-hosted .sentryclirc in the directory, and rejects --yes and
  my-org/x like any command without input; the @sentry/mcp-server
  bundle builds and its bundle test passes

https://claude.ai/code/session_017M6odVd9nWxcAefpXRLd8M

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Nov 5, 2026 7:16pm UTC

[BYK]

I still think there's value in listing all available SDKs to the agent, the version we compiled from sentry release registry, ask it to pick one from there and instruct it to use sentry docs to keep going or generate a guide or something.

[betegon]

@BYK thanks for the review, i'm making those changes.

About showing the sdks, i've had a bad experience with it in init in the past:

• sometimes you need more than 1 sdk
• if for any reason the agent doesn't look at docs, it may get the sdk and install it from the wrong registry (e.g. in the past we were using deno.land for the deno sdk and now it's npm so that could fail)
• if we force the agent to always look at docs, there's no need to tell it about the sdk registry because that's in the docs

[BYK]

@betegon I'm not suggesting that we propose an SDK, merely providing the list of all available SDKs from our registry to the agent so it can make the decision to add multiple if needed which we should also mention.