Breadcrumbs in Issues

[dcramer]

Consider adding breadcrumbs to the issue details response.

I'm a little hesistant to do this by defaulta s that could be quite a chunk of data.

[iftheshoefritz]

This is literally the only reason I tried to install sentry-mcp. I want to find data in the breadcrumbs that doesn't exist elsewhere, and don't want to make a thousand clicks per event to get all the different permutations that have resulted in an error.

[hallh]

The lack of breadcrumbs makes it difficult for agents to solve frontend issues as they focus too much on the specific line of code that's crashing, rather than the actions being taken by the user. We're seeing that they typically opt to just prevent unhandled errors, but still leave the functionality in a broken state. Would definitely wish for the option to get breadcrumbs in some shape or form.

[dcramer]

Any chance you could share a sample issue? I don’t want to include breadcrumbs by default due to the size but we might be able to hint to the agent when it needs them and give a path to fetch them. That said it’s likely our focus will be on optimizing Seer around this as breadcrumbs are just one of the many concerns Sent from my phone. Pardon the typos.

…

On Sun, Dec 7, 2025 at 12:51 PM hallh ***@***.***> wrote: *hallh* left a comment (getsentry/toolkit#534) <#534 (comment)> The lack of breadcrumbs makes it difficult for agents to solve frontend issues as they focus too much on the specific line of code that's crashing, rather than the actions being taken by the user. We're seeing that they typically opt to just prevent unhandled errors, but still leave the functionality in a broken state. Would definitely wish for the option to get breadcrumbs in some shape or form. — Reply to this email directly, view it on GitHub <#534 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFYOURFXCHY6EM2B7KKG34ASHNBAVCNFSM6AAAAACFNT6KKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRTGI2DKOBQGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[hallh]

@dcramer I can share this one: https://deloguecom.sentry.io/issues/80597161

[dcramer]

I'm going to test before fully committing to this plan, but we'll either add a flag ("get lots of breadcrumbs" kind of thing) or an ultra light very descriptively named tool that tries to consume very few tokens.

Default issue response will include a few (say last 5, with a hint to the tool call).

Anything beyond this will end up deferred to Seer, which is going to be the long term solution for this. We're not really ready to say its the replacement though.

[dcramer]

Ok on further inspection this is worse than I expected. Recent breadcrumbs are absolutely useless. I can add a "get_breadcrumbs_for_issue" but I'm not totally sure its going to be a good experience. Exploring if we can just expose our seer toolchain as a remote agent to inquire from it as it can much more effectively do what we need (give you responses from the collective of data, vs just breadcrumbs, and do it without context bloat).

[oddgames-david]

get_breadcrumbs_for_issue would be perfect, I don't want AI to be filtering my breadcrumbs, i have my own prompt that knows how my logs should look.

[eugene1g]

+1 to get_breadcrumbs_for_issue - it's a perfect option for this when doing a deep dive into a single issue

For us, the highest value of this MCP is to allow agents to consume large amounts of diagnostic text so the developer doesn't have to, and reviewing breadcrumbs is often essential to correctly diagnosing issues in a complex UI.

[evelant]

Not having breadcrumbs essentially makes some use cases of this mcp impossible -- for example having an agent use breadcrumbs to trace what was happening leading up to a crash in which the trace does not have much detail or correlating crash causes out of multiple sets of breadcrumbs.

As a workaround I had codex fetch breadcrumbs for particular issues using the sentry api instead of MCP.

[Trunksome]

Yes, please give the ability to have the MCP investigate breadcrumbs. Using Claude Code + Sentry has been a magical experience these last few hours; but now i realized it cannot access breadcrumbs, which makes it a lot less powerful than i thought it would be...

[dcramer]

Add ?experimental=1 to the conn string and let me know how this goes for yall. This was my best idea to improve things without consequence, and hoping to expand it but I need to feel good that we didnt wreck any normal flows first.

If you have any prompts that have it run in circles (or even fail on the first try) please let me know!

[hotngui]

I look forward to having access to this feature as its one of the main reasons I looked at the MCP.
Any eta on availability?