docs: trim sentry subagent to auth/token focus

[marcusquinn]

Remove verbose SDK docs - wizard handles that. Focus on MCP setup and token troubleshooting.

[coderabbitai]

Warning

Rate limit exceeded

@marcusquinn has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 28 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/sentry-docs-trim

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @marcusquinn, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the Sentry monitoring documentation by removing redundant and overly detailed SDK integration instructions, which are now primarily managed by the Sentry wizard. The focus has shifted to providing a more concise guide for Managed Control Plane (MCP) setup and essential token troubleshooting, ensuring the documentation is more targeted and easier to navigate for users setting up Sentry with MCP.

Highlights

• Documentation Trimming: Removed verbose SDK integration documentation, including detailed OpenCode config examples and extensive Next.js setup guides, as these are better handled by the Sentry wizard.
• Token Management Clarification: Updated the 'Generate Personal Auth Token' section to emphasize that tokens must be created after organization setup to inherit access, and added a new 'Test Connection' step for token verification.
• Troubleshooting Refinement: Streamlined the troubleshooting section by removing less common issues (e.g., ad-blockers, source map uploads) and adding a clear distinction between Org tokens and Personal tokens for MCP use.

Changelog

• .agent/services/monitoring/sentry.md
  • Removed the 'OpenCode Config' example for Sentry integration.
  • Clarified that personal auth tokens must be created after organization creation to inherit access.
  • Added a new 'Test Connection' step to verify Sentry token functionality.
  • Replaced extensive 'Next.js SDK Integration' details with a recommendation to use the Sentry wizard and a link to the official Sentry documentation.
  • Simplified the 'Troubleshooting' section, removing specific issues like 'Ad-blockers blocking Sentry' and 'Source maps not uploading'.
  • Added a new troubleshooting point distinguishing between 'Org token vs Personal token'.
  • Updated the 'Related' links to be more general and concise.

Activity

• No specific activity (comments, reviews, etc.) was provided in the context for this pull request.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request significantly slims down the Sentry subagent documentation by removing the detailed SDK integration steps in favor of pointing to the Sentry wizard. This is a great change that improves focus and maintainability. The updates to the troubleshooting section and the addition of a connection test step are also valuable improvements. I've added a couple of suggestions to retain some important context that was removed, which I believe will prevent potential user confusion during setup.

I am having trouble creating individual review comments. Click here to see my feedback.

.agent/services/monitoring/sentry.md (35-43)

While the goal is to trim the document, removing this OpenCode Config example makes it difficult to understand the jq command in 'Step 3. Configure MCP'. Without this context, users may not know what structure is expected in ~/.config/opencode/opencode.json, which could lead to errors. Please consider re-adding this example configuration block.

.agent/services/monitoring/sentry.md (117)

The explanation 'Tokens created before the org don't inherit access' was removed from this troubleshooting tip. While this information is present earlier in the document, it's very helpful to have it here as well for users who jump directly to the troubleshooting section. It clarifies why they are seeing empty organizations and reinforces the solution.

Create a new Personal Auth Token **after** the organization exists. Tokens created before the org don't inherit access.

[augmentcode]

🤖 Augment PR Summary

Summary: This PR trims the Sentry subagent documentation to focus on MCP setup, authentication, and token troubleshooting rather than SDK integration walkthroughs.

Changes:

• Removed the verbose Next.js SDK integration and manual config examples, leaning on @sentry/wizard for setup
• Clarified Personal Auth Token creation timing (after the org exists) and simplified navigation instructions
• Kept/streamlined the OpenCode MCP configuration flow via a jq-based update to opencode.json
• Added a concrete “Test Connection” curl example against /api/0/organizations/ to validate auth quickly
• Updated usage examples to use a generic project placeholder (my-project)
• Simplified troubleshooting steps and added guidance on Org vs Personal tokens for MCP usage
• Reduced related links to core Sentry documentation + Sentry MCP

Technical Notes: Documentation now assumes the wizard owns SDK file generation and focuses on getting a working MCP token + API validation path.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

This step prints the full $SENTRY_YOURNAME token to the terminal; that can easily leak credentials via shell history, CI logs, or screen recordings. Consider a verification approach that confirms the variable is set without outputting the secret.

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}