Inputs remain active during async init steps (clack)

[sentry-junior]

Summary

During the sentry init flow, user inputs (e.g. team/org selection prompts) remain interactive while an async step like create-sentry-project is still running. This can lead to unintended navigation or input during background operations.

Reproduction

1. Run sentry init --team <team>
2. Observe the spinner: ◓ Setting up Sentry project (create-sentry-project)
3. While the spinner is active, attempt to navigate interactive prompts — they remain responsive

Expected behavior

Interactive inputs should be disabled or locked while async operations are in progress to prevent conflicting state.

Notes

This may be a limitation of the clack prompts library — it may not expose an API to disable inputs mid-flow. Worth investigating if there's a supported pattern.

Action taken on behalf of Miguel Betegón.

[sentry-junior]

Screenshot from the thread showing the issue in context:

Terminal session running sentry init --team sentry-developer-experience in repo test-linear-and-sentry-cli-init on branch main. The EXPERIMENTAL warning was acknowledged, and the spinner Detecting platform and framework (read-files) is visible while inputs remain navigable.

(Image shared by Sergiy Dybskiy in internal Slack thread — attached here for reference.)