feat(skills): report agentic onboarding progress

[evanpurkhiser]

Keep Sentry’s getting-started UI synchronized with agent-led setup through silent, privacy-focused progress updates.

The guidance detects onboarding tokens in the initial prompt, defines stage and run-state transitions, handles update failures without interrupting setup, and reports multi-project and verification metadata at the relevant stages.

[sentry]

Bug: The create_project stage instructions omit the initial 'Report active' step, which is present in all other stages, breaking the expected agent state machine.
_{Severity: HIGH}

Suggested Fix

Add an instruction at the beginning of the create_project stage documentation, similar to other stages, that directs the agent to 'Report active' before starting the project creation or selection process. This will ensure the state machine is entered correctly.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: src/references/first-error-setup.md#L36-L45

Potential issue: The documentation for the `create_project` stage omits the instruction
for an agent to report an `active` status at the beginning of the process. All other
stages explicitly start with this instruction. An LLM agent following these instructions
will not report the initial `active` status, causing it to skip a step in its state
machine. This will lead to incorrect state transitions (e.g., starting with `waiting`
instead of `active`) when a user creates a new project, breaking the expected state
machine logic.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a708bb8. Configure here.}

[cursor]

Auth failure permanently stops progress updates

High Severity

Discovery of onboarding_status_update is written as an immediate imperative, and any failed discovery permanently disables progress updates for the rest of the session. First-time getting-started users often have MCP disconnected, so search_sentry_tools fails before auth. The unauthenticated path never re-enables updates after the user connects, so the onboarding UI stays frozen even though setup continues.

Additional Locations (2)

• src/skills/sentry-get-started/SKILL.md#L37-L42
• src/skills/sentry-get-started/SKILL.md#L138-L150

 

^{Reviewed by Cursor Bugbot for commit a708bb8. Configure here.}