Looking for public Claude Code MCP plugin failure logs to test safe failure-window extraction #3050
Unanswered
rileyross722
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone, I’m looking for a few public Claude Code MCP plugin, reconnect, startup, install, or terminal failure logs to test whether a “safe failure-window” workflow is useful for coding agents.
I saw issue #2251, where
plugin:claude-mem:mcp-searchfailed to reconnect in Claude Code with a module-resolution error around:That issue is already closed, so I’m not trying to reopen it or add noise there. I’m using it only as an example of the kind of failure pattern I’m interested in:
Cannot find moduleWhat I’m testing
I’m testing FailLens Crash Gate, which does one narrow thing:
No install is needed for the first test.
If someone has a public failed Claude Code MCP plugin log, reconnect failure, GitHub Actions failure, install failure, or terminal crash related to claude-mem / MCP tooling, feel free to reply with a public link or paste a redacted excerpt.
What I can return
I can run it through FailLens and reply with a safe summary like:
I will not publish raw logs, secrets, private repo names, or stack trace bodies in any public proof without permission.
Good example
A good example is:
If this kind of validation post is not appropriate for this discussion area, I’m happy to remove it. I’m mainly looking for real Claude Code / MCP plugin failure examples to see whether this workflow is useful outside my own test cases.
All reactions