Collaboration is a major 🗝️ for success. You can now mention other members in issues, making teamwork even easier. Use @ to tag team members - they’ll receive an email and be subscribed to that issue.
Any mentioned user will be able to see why they are getting notifications in the body of the emails they receive:
In your issue dashboard you can do a quick search for subscribed:me to see which issues you are subscribed to, any with a little green comment icon
will be issues you are mentioned in.
You can manually unsubscribe from any issue by selecting Unsubscribe Me. (a.k.a Don’t @ me)
So, if you want to debug React, do Django error tracking, or handle an obscure Rails exception, you can now collaborate with your entire team using Sentry.
Should you use Seer or just connect the MCP to your agent? A breakdown of what Seer, the Sentry agent plugin, the CLI, and coding agent handoffs each do — and when to reach for one over the other.
Five months after launch, Seer Agent can now take action on your behalf in Sentry, and pull in infrastructure data from outside Sentry to diagnose issues faster.
The all-or-nothing sendDefaultPii boolean is going away. dataCollection replaces it with a dial for each category of data, so you can keep the headers you debug with and drop the values you would rather not store.
